QUOTE(gunner @ Sep 17 2005, 09:43 AM)
Exactly my point. If the function worked correctly, the problem would not have happened. It would have been deleted. It is not a CCleaner bug, it is a microsoft bug.{ The post was in bug reporting}file management system:
erm you do realize that there is nothing wrong with the function(s)? all it does is send the delete message to the file system. the file system returns a value that indicates whether it worked or not.
you also have to realize that files loaded into memory cannot be deleted unless they are terminated. This is not Microsoft's fault and it is not CCleaner's fault. this is the same principle with all Operating Systems so it is not limited to Microsoft.
also another thing the winapp entry for Ahead Nero Burning ROM is this.
CODE
[Ahead Nero Burning ROM]
LangSecRef=3021
Detect=HKCU\Software\ahead\Nero - Burning Rom
Default=True
RegKey1=HKCU\Software\ahead\Nero - Burning Rom\Settings|BrowserDir
RegKey2=HKCU\Software\ahead\Nero - Burning Rom\Settings|ImageDir
RegKey3=HKCU\Software\ahead\Nero - Burning Rom\Settings|WorkingDir
RegKey4=HKLM\Software\Ahead\Nero - Burning Rom\Settings|ImageDir
RegKey5=HKLM\Software\Ahead\Nero - Burning Rom\Settings|BootImageDir
when the program is uninstalled, the uninstaller doesnt bother to delete the registry entry. why? cause it doesnt want to.
CCleaner currently does not have the ability to erase registry values from old programs. it only can fix errors in the registry as the checkboxes are labeled.