Quick Cache Dynamic Cache Pruning

There are different Dynamic Cache Pruning options in Quick Cache.

So let’s summarize things here and review your configuration thus far. There is an automatic expiration system ( the Garbage Collector ), which runs through WordPress? behind-the-scenes, according to your Expiration setting. Then, there is also a built-in Expiration Time on existing files, which is checked before any cache file is served up; this also uses your Expiration setting. So… what happens if you’re working on your site, and you update a Post or a Page? Do visitors have to wait an hour before they see these changes? Or should they see changes like this automatically?
That is where this configuration option comes in. Whenever you update a Post or a Page, Quick Cache can automatically Prune that particular file from the cache, so it instantly becomes fresh again. Otherwise, your visitors would need to wait for the previous cached version to expire. If you’d like Quick Cache to handle this for you, set this option to Single. If you want Quick Cache to completely reset ( purge all cache files ) when this happens; and be triggered on other actions too — like if you rename a category or add links, set this to All. If you don’t want any of this, and you just want blazing fast speed at all times, set this to None.

After insatlling BWS, it’s impossible to set Dynamic Cache Pruning to “None”.
And still impossible even after disabling and deleting BWS.

I tried it on a new site. Installed Quick Cache, set Dynamic Cache Pruning to “None”. It works.
Installed BWS. Dynamic Cache Pruning turnes to “Single page” and if I try to choose “None” there is no any effect.

Where can be a problem? Whereshould I look to fix it?

https://www.ads-software.com/extend/plugins/better-wp-security/