I have seen several computers now where index.dat is not being deleted? The program is set to mark it and the relevant entry is in the "PendingFileRenameOperations" registry entry as in:
\??\C:\DOCUME~1\user\LOCALS~1\TEMPOR~1\Content.IE5\index.dat
\??\C:\DOCUME~1\user\Cookies\index.dat
\??\C:\DOCUME~1\user\LOCALS~1\History\History.IE5\index.dat
HOWEVER, after many reboots, the entry still stays there. OS is WinXP Home SP2 and Pro SP2.
Index.dat files don't go away permanently. When they are emptied or deleted, they start over and accumulate data again.
Don't worry that a file size is reported for the index.dat. There is a minimum file size even when empty (usually a multiple of 16 KB, but IE5 may differ).
Index.dat files don't go away permanently. When they are emptied or deleted, they start over and accumulate data again.
You are correct - They do start again BUT ... If you read my concern you will see that I said that the entry remains in the registry which means that it has not run. After the files are deleted, the entry should be removed from the regisrty.
Doesn't appear to be a general bug. I tested on WinXP Home SP2 and get the same reg entries when I run "Delete index.dat files" but they clear after reboot.
I have seen several computers now where index.dat is not being deleted? The program is set to mark it and the relevant entry is in the "PendingFileRenameOperations" registry entry as in:\??\C:\DOCUME~1\user\LOCALS~1\TEMPOR~1\Content.IE5\index.dat
\??\C:\DOCUME~1\user\Cookies\index.dat
\??\C:\DOCUME~1\user\LOCALS~1\History\History.IE5\index.dat
HOWEVER, after many reboots, the entry still stays there. OS is WinXP Home SP2 and Pro SP2.
There is a very good reason for this to be so.
If this index.dat file:
C:\WINDOWS\PCHealth\HelpCtr\OfflineCache
... were to be deleted, you would lose functionality of the SYSINFO command, and portions of Help & Support. I have spent 3 months arguing with the group, at CleanUp!, who refuse to issue warnings, for users of XP, of this glitch.
I have XP, and Cleaner V1.25.201, and the box for 'Delete Index.dat files' is disabled (it came that way).
Thanks, to CCleaner ! A GREAT product, with built-in safeguards !
I now have it disabled as well. With that entry in the registry, other product installs can and do fail. Not only that... I have two clients who have had their computers rendered useless because an automatic update somehow did go through and XP was corrupted due to the entry in the registry. That part - A serious bug indeed.
I'm not sure what you mean about the index.dat file in C:\WINDOWS\PCHealth\HelpCtr\OfflineCache. Is there a setting that causes CCleaner to select this? Obviously, I want to avoid accidentally using it.
When I run CCleaner with "Delete index.dat files" it's never selected that index.dat ... only those in Temporary Internet Files, Cookies and History.
I'm not sure what you mean about the index.dat file in C:\WINDOWS\PCHealth\HelpCtr\OfflineCache. Is there a setting that causes CCleaner to select this? Obviously, I want to avoid accidentally using it.
When I run CCleaner with "Delete index.dat files" it's never selected that index.dat ... only those in Temporary Internet Files, Cookies and History.
Apparently, this ONE file is excluded from deletion, whether you ARE able (I am NOT) to click the box, or not.
My point was to warn of the danger of this file being deleted, and the consequences of this. I did not, know, at the time of posting, whether CCleaner had any protection installed, for XP, and this necessary file. It does !
My concerns had been fueled by the behavior of another product(CleanUP!), which will remove that file, and cause loss of functionality, in XP. Yes, 'Index.dat' files MAY be excluded, easily, from CleanUP!... but, if run, as-is, and without version-specific warnings, for XP, that file is TOAST ! Granted, these are not often-used utility functions, and, to their credit, the design team did not, at the time of writing the code, know of the potential for this problem. They do NOW (LOL), yet they still refuse to issue version-specific warnings, for this product !
I see new victims... er.. users, with this problem, almost daily...
I have, since posting THAT, found another issue, involving a setting, in CCleaner, which causes problems with MacroMedia FlashPlayer (version 8). This is due to a change made in FlashPlayer, and is NOT the fault of CCleaner.
I shall look about, and see if there is a post for this, and if not, I'll start one.