File Cleaner Unneeded files can't find some old hives

tullik

File Cleaner Unneeded files can't find some old hives (Vista, PT v.1.8.0.460)

The files listed are unneeded files. However with *.*_previous; *_previous; as the search parameters in the File Cleaner "Unneeded files" tab, it failed to find the red ones. It seems the protections recently added to File Cleaner include some files inappropriately.

The files can be found and removed with File Finder. The two ntuser.dat_previous files in the C:\Windows\ServiceProfiles\... structure caused a PT pop-up like the screenshot.

The protections in the two File tools should be changed. The "_previous" files do not need to be protected.

A File Finder result:

jv16 PowerTools 2008

Data fields are: Directory, File, Size, Last modified

C:\Windows\ServiceProfiles\LocalService\, ntuser.dat_previous, 152 KB, 04.11.2008, 09

C:\Windows\ServiceProfiles\NetworkService\, ntuser.dat_previous, 144 KB, 04.11.2008, 09

C:\Windows\System32\config\, components_previous, 12.5 MB, 04.11.2008, 09

C:\Windows\System32\config\, default_previous, 172 KB, 04.11.2008, 09

C:\Windows\System32\config\, sam_previous, 132 KB, 04.11.2008, 09

C:\Windows\System32\config\, security_previous, 52 KB, 04.11.2008, 09

C:\Windows\System32\config\, software_previous, 33.3 MB, 04.11.2008, 09

C:\Windows\System32\config\, system_previous, 21 MB, 04.11.2008, 09

C:\Windows\System32\SMI\Store\Machine\, schema.dat_previous, 5.8 MB, 04.11.2008, 08

05-28-2008_21-29-39.jpg

Another File Finder result with More dates:

jv16 PowerTools 2008

Data fields are: Directory, File, Size, Created, Last modified, Last accessed

C:\Windows\ServiceProfiles\LocalService\, ntuser.dat_previous, 152 KB, 11.02.2006, 07, 04.11.2008, 09, 04.11.2008, 09

C:\Windows\ServiceProfiles\NetworkService\, ntuser.dat_previous, 144 KB, 11.02.2006, 07, 04.11.2008, 09, 04.11.2008, 09

C:\Windows\System32\SMI\Store\Machine\, schema.dat_previous, 5.8 MB, 11.02.2006, 05, 04.11.2008, 08, 04.11.2008, 08

jv16

This bug is now fixed, thank you for reporting! The next released version will contain the fix, the next version will be released later in this month, hopefully in this week.