The two EXE files above the "--" are legit entries - I changed their extensions on-disk to disable them.
The two SCR files are living, breathing (an assumption on my part) files that exist unmolested where the registry says they exist. Not that I'll ever use them but it makes me nervous getting this error using a tool widely acclaimed to be the very best. What could cause this?
(Another SCR extension'd file in the Regy and on-disk remained appropriately unindicted, so that one worked properly.)
The two EXE files above the "--" are legit entries - I changed their extensions on-disk to disable them.
The two SCR files are living, breathing (an assumption on my part) files that exist unmolested where the registry says they exist. Not that I'll ever use them but it makes me nervous getting this error using a tool widely acclaimed to be the very best. What could cause this?
(Another SCR extension'd file in the Regy and on-disk remained appropriately unindicted, so that one worked properly.)
Thanks!
Matson
Examining the "SharedDLLs" Registry key a little more closely... it has between 4k and 5k entries and contains as many non-DLL entries as it does DLL entries. Has this Regy key become every App creator's dumping ground for manifests? If so, I can understand why an error here might NOT be as vital to ongoing OS operations as I had originally thought.