Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
-
Win64; I've only seen it on AMD64, but presumably it would also happen on ia64.
Description
When creating and accessing the configuration registry keys, the tool uses CreateRegKeyEx with the KEY_WOW64_32KEY flag, telling windows "Use the 32-bit hive instead of the 64-bit one". Maybe this was done so that 64-bit daemons could use the configuration from 32-bit ones?
Anyway when it's time to go and delete the configuration from the registry it uses the ancient SHDeleteKey call, which tries to delete the key from the 64-bit hive, which fails, so the key is left behind.