Vasek wroteYes, this is unfortunately normal... I reported this behaviour several times to developer and no reply...
This type of failure to "fix" or remove is usually due to permissions issues, or possibly intentional application protection by the applicable product vendor, of a key and sub-keys.
This manual RegEdit procedure can often allow you to set permissions and ownership so you (and jv16PT) can change or remove the pertinent registry items:
If you don't want to mess with manually changing the registry, simply use one of jv16PT's ignore methods so you won't have to see the anomalies on the list.
The above referenced procedure could probably be performed programmatically. There are at least three reasons why the developer probably won't do that:
- 1. To change permissions automatically, he would have to assume too much about why the issues or protection exist in the first place. That's a safety risk.
2. It could slow down the scans on some systems.
3. Coding the routine would not be easy, and the ignore options are already present for the user.
