Willy2

- Why limit the backing up of registry keys to the "Fix all issues" option ? I think it should be extended to cover both options.

- I wouldn't be too worried. When Windows detects that disk space is becoming scarce then Windows will automatically delete one or more of those System Restore Points (SRPs). - I also know that when e.g. the C: drive can't contain any SRPs any more then Windows will store the next SRP on the next drive (e.g. D:, E:) provided System Restore is enabled for those drives as well. - Some programs simply apply a "quick & dirty" approach when it comes to storing files on a disk (i.e. leave the files defragmented) instead of finding a free space large enough to store a file in one piece. - Choose a "lowel level" of System Restore ("Only restore previous file versions" or something along those lines) and install Tweaking's Registry Backup. About 95% of system settings are stored in the registry. - Time calculating: It gives an estimate of the time. I think it should be removed but the Piriform developers seem to have different thoughts.

I recently installed Speccy v1.28. And the program still can't make up its mind. On the one hand the program tells me that "Windows Defender" (WD) is "Enabled" but on the other hand it accurately reports that WD Service (called "WinDefend") has been "Stopped". See my signature for more info (made with SPECCY).

@MrV: I do highly doubt it whether that's the case. Because when one has a ton of registry entries to be removed then why select each entry individually ? I personally never choose the "fix Issue" option and Always choose the "Fix all selected Issues" option. I could imagine that on a Win 8 system CC first removes the registry entry BEFORE writing that (non existing) info to disk. Yes, in that case the backup file remains (almost) empty.

CC v5.05 can be and should be improved !!!! The developers of CC have gotten A LOT OF flak for the new color schemes of CC versions v5.xx but since they didn't go back to the old scheme I presume they are determined to stick with the current GUI colors. But that doesn't mean the coloring scheme of the GUI can be & should be improved. - Select "Options", "Include", "Add". Then a window pops up. And there CC's "color behaviour" can be improved. - Click on the downwards pointing arrow and a dropbox opens offering the user three more options. But for the user it's not too obvious what those extra options are. The reason is that the background color in the dropbox is the same as the background color of the "Include" window/menu (i.e. white). That's (at least for me) very confusing and I assume for any other user as well. Solution: Change the background color of the "Include" window/menu from white to e.g. grey. Then the dropbox will stand out from the rest of the window/menu. The CC developers have recognized this problem in the "Settings" screen/pane (Options >> Settings). The background color there is grey but the background color of the "Language" dropbox is white. So, I would assume this color behaviour can be fixed as well.

@mta: When CC exports those obsolete registry entries then there Always should be the text "Windows Registry Editor Version 5.00" on the first line in the *.reg file. I ran CC's registry cleaner on my Win 7 system. The first few lines in the backup *.reg file were (in italics): Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs] "C:\\Windows\\Microsoft.NET\\Framework\\v1.0.3705\\vsavb7rt.dll"=dword:00001000 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDLLs] "C:\\Windows\\Microsoft.NET\\Framework\\v1.0.3705\\system.enterpriseservices.dll"=dword:00001000 It seems that on a Win 8 system CC only exports the first line and nothing else. Yes, this could be a SERIOUS bug in CC. Thumbs up for Sweat-Cleaner.

@mta: right, but the problem is that besides that text, there's no other content. And that could be a bug in CC.

@mta: but then DF won't defragment the enitre file, then it will only partially defragment the file. Solution: Use DF's option "Free Space Defragment". It will move files towards the beginning of the drive and that could create a contiguous 8+ free disk space.

Is there a 8+ GB contiguous free space available at all ?

- Yes, I have seen the same thing happening on my system but (for the time being) I don't blame CC (yet). Don't know what to make of it. - Yes, running CCleaner can indeed "mess up" Windows Update (WU). If one cleans out some folders (e.g. "C:\Windows\SoftwareDistribution") and the registry between the installing those updates and a system restart, then the user (& WU) runs into trouble. WU simply needs those (temporary) files/that info to be able to update one's system. - Which folders were cleaned by CCleaner ? Select "Option", "Advanced", "Save all settings to INI file". Then a file called "Ccleaner.ini" shows up in the CCleaner folder. Please attach that file to your next reply.

- Came across another bug in DF v2.19 !!!! After a fresh re-install DF shows the "Modern" style of displaying the drive map (and file list ?????). Then I switched to the "Original" look (I DO NOT like the "Modern" view. Too fuzzy IMO). But the checkboxes in the file list somehow got overlooked by DF and continued to be displayed in the "Modern" look/style. See picture in the attachment. It suggests that DF has 2 separate subroutines for changing the view/style. One for the drive map and a separate second one for the file list. And that somehow sometimes one of these 2 subroutines isn't executed when the user changes the style of the GUI. Suggestion: Perhaps DF is able to display both the filelist & drivemap in the same style/look/view, directly after a fresh re-install. This means that when the user selects/switches back to the "Modern" style the checkboxes of the filelist should displayed in/changed to the "Modern" view/style as well. Another option could be that the user can choose "Modern" for drive map and "Original" for the file list (and/or the other way around). (Putting all bug reports/thoughts regarding DF in one thread allows me to keep track of the bugs I came across and were reported by me. I thought (and more or less hoped) I would come across more than one bug and I was right.)

Deleted.

@Andavari: I don't mind someone else posts in this thread as well. The more users posting their bugs the more pressure for the Piriform developers to improve the software. Seems not too many users are using these features.

A japanese woman was furious when she learned that her friend cheated on her and then dumped his Apple collection in the bathtub. http://www.dailymail.co.uk/femail/article-3050168/Revenge-dish-best-served-WET-Scorned-woman-dumps-lying-lover-s-entire-Apple-collection-bath-sent-pictures-prove-it.html

- I got 3 updates for my Win 7 system. - Why doesn't MS issue more "Cumulative Updates" ? It would reduce the amount of updates a user has to install with a fresh re-install.

More details for these 34 updates: https://support.microsoft.com/en-us/kb/894199

In reply #22 I wrote: "- Get rid of the option "Have smaller fragments than". Because DF doesn't show how large the fragments of a defragmented file is. That remains a mystery for the user." Another possibility is to not remove that option but apply the "Have smaller fragments than" rule BEFORE showing the file list.

I am sure there's a separate webpage for Win 8 as well. Try to GOOGLE it.

- On the latest "Windows Update" day I was already wondering why there weren't any "optional updates". I thought MS has simplified a number of things in their WU procedure. - I hope to see a new option for WU called "Download Updates & install when the computer shuts down" (or something along those lines) somewhere in the future. I submitted such a suggestion to MS recently. - It's Always a mystery what all these "optional updates" do. I Always try to find to more info about them but the descriptions/explanations are so murky. (If one wants to provide feedback to MS regarding Windows 7 then one can that here: http://support2.microsoft.com/common/survey.aspx?scid=sw;en-us;2310&altStyle=MFE&renderOption=OverrideDefault&showpage=1&fr=1&nofrbrand=1)

- These files won't be moved by Defraggler at all.

- Perhaps some system files are skipped by Defraggler ? Are these files in "C:\System Volume Information" ?

In other words, in this case, DF failed/overlooked to remove the last line "MoveToDriveEndFiles3=......." from Defraggler.ini.

- More proof that DF needs improved "Collect Info" & "Write Info To Disk" subroutines. I had these lines in Defraggler.ini: MoveToDriveEndFiles1=PATH|R|C:\Een Rotterdamse Aziaat|* MoveToDriveEndFiles2=PATH|R|C:\Videos1|* MoveToDriveEndFiles3=PATH|R|C:\Videos2|* I removed the first line with the "Defrag" GUI. Closed DF & restarted DF again. Then I saw these 3 lines: MoveToDriveEndFiles1=PATH|R|C:\Videos1|* MoveToDriveEndFiles2=PATH|R|C:\Videos2|* MoveToDriveEndFiles3=PATH|R|C:\Videos2|*

- Somehow I ended up with these lines in Defraggler.ini Excluded32=PATH|R|C:\Win 7 Pro 64bit - Nieuw|* Excluded33=PATH|R|C:\Win 7 Pro 64bit - Nieuw|* MoveToDriveEndFiles1=PATH|R|C:\Een Rotterdamse Aziaat|* MoveToDriveEndFiles2=PATH|R|C:\Videos1|* MoveToDriveEndFiles3=PATH|R|C:\Videos2|* Excluded34=PATH|R|C:\Windows|* Excluded35=PATH|R|C:\Windows|* I removed the duplicates (with the "Exclude" GUI), closed and restarted DF again and those lines changed to this (See "Excluded33=....."): Excluded32=PATH|R|C:\Win 7 Pro 64bit - Nieuw|* Excluded33=PATH|R|C:\Windows|* MoveToDriveEndFiles1=PATH|R|C:\Een Rotterdamse Aziaat|* MoveToDriveEndFiles2=PATH|R|C:\Videos1|* MoveToDriveEndFiles3=PATH|R|C:\Videos2|* Excluded34=PATH|R|C:\Windows|* Excluded35=PATH|R|C:\Windows|* Do those 3 lines "MoveToDriveEndFiles" throw DF off the rails, because they're between 2 "Excluded...." lines ?? - DF's "MoveToDriveEnd" doesn't work "too well". With these lines in Defraggler.ini MoveLargeFilesToEndOfDrive=1 MinLargeFileSize=0 MoveOnlySelectedLargeFileCategories=1 LargeFilesCategories=Videos;1|Movie files;0|Disk images;0|Archives;0 LargeFilesExtensions=*.mp4<*.avi|*.mkv|*.mpg|*.mov|*.mp4|*.mpeg|*.wmv<*.bin|*.iso|*.mdf|*.vhd<*.arj|*.tar|*.rar|*.zip|*.cab|*.7z DefragFreeSpaceMoveLargeFiles=1 DontApplyMinimumFileSizeToFilesFolders=1 MoveToDriveEndFiles1=PATH|R|C:\Een Rotterdamse Aziaat|* MoveToDriveEndFiles2=PATH|R|C:\Videos1|* MoveToDriveEndFiles3=PATH|R|C:\Videos2|* I expected DF would move ALL *.mp4 files (in "C:\Videos2") to the end of the drive. But instead, DF moved a number of *.mp4 files only, DF didn't move ALL *.mp4 files. But DF also moved a number of "*.flv" video (in "C:\Videos2") files to the end of the drive. Combined with the fact that DF shows the names of a number metadata files (e.g. "C:\$Extend\.... ", suggesting that DF moves those files as well) strongly suggests that something messes up/interferes with the file list DF uses to move those files. (Does this also happen when moving to the beginning of the drive ?)

- About becoming a BETA tester: If the Piriform developers think I can be of help then they know where to find me. - In a previous post I mentioned that something "throws DF off the rails" when it comes to moving files to the end of the drive. But DF also keeps track, in real time, of the amount of free & used disk space. I could imagine that that also could "interfere" with the file moving subroutine(s). - If the developers want to speed up the program then introduce an option that can turn off all "real time tracking" stuff. Then the user can decide whether or not he/she wants this kind of information. I personally don't care (too much) about this information (I thinks it's a nice gimmick, nothing more) and would like to see that DF uses all the computing power available for the main tasks (i.e. moving files).