Willy2

- When run in Safe Mode a number of repairs simply won't work. If you have version v2.10.1 then you must prepare your system for running in Safe Mode. The program has an additional button for that. - It's HIGHLY recommended to ALWAYS run the first 5/6 repairs - DO NOT run Windows Repair in Safe Mode with Networking !!!!! That's why you need to "switch off" the internet.

- If you turn off the Anti virus then you should "turn off" the internet first. - "Windows Repair" tries to put/puts a whole range of things in Windows back to their default state, including WMI.

Hazelnut closed this thread http://forum.piriform.com/index.php?showtopic=42174 before I could add another reply to that thread. So, I opened a new thread. I did some research on my computer system (see my signature for system details) with some 170.000 files. I put the latest version of Defraggler to work and memory usage increased from ~ 4 MB to ~ 110 MB when it analyzed the drive. After finishing the analysis memory usage went down to ~ 80 MB. So, Defraggler does make brave attempt to reduce memory usage. (minus ~ 30 MB). Only PcWinTech's Cleanmem reduces the memory usage down to a mere ~ 2 MB again. But I don't whether or not that would "break" anything Defraggler stores in the memory. When I, after running Cleanmem, put DF to work again then it seems this memory usage reduction (Cleanmem) didn't have a noticable negative impact on the speed with wich DF analyses & defragments a (logical) drive. But that's with a memory usage of ~ 22%. I don't know whether or not it would a difference when a system has a memory usage as high as "Maki" had. I also looked at the size of the file cache (with Cleanmem's Mini Monitor) but after opening the program itself the size of the filecache actually never/barely increased or decreased. In that regard, Defraggler seems to be trying to keep the filecache as small as possible as well.

- Ouch, my mistake. The option "Wipe Free Space" doesn't exist in Defraggler but it does in CCleaner. But over there's it's a "pain in the a**" as well. As I have described above. - Agree. The users should be warned about the VSS and I am convinced this option should be enabled by default. More over, I think, DF should ALWAYS disable the VSS Service whenever Defraggler is busy doing anything, and re-enabled afterwards (if/when appropriate). Then the program can get rid of that option as well. No need to bother the innocent non-geek with this confusing behaviour. - In that regard, it was good to bring this to the attention of the "Piriform crowd". @Developers of Defraggler: Are you reading this ? To be implemented IMO !!! - I have seen that in certain circumstances Windows itself wipes all the System Restore Points as well on my Win 7 system. - The feature System Restore Point itself can be a "Pain in the a**" as well. If it works it's a wonderful feature but when/if it doesn't work then it's a nightmare. I therefore recommend to install (Warning: Shameless Plug) Tweaking's Registry Backup. It makes a copy of the registry upon every start up. Some 90 to 95% of the errors are registry related.

See also this thread for more info: http://forum.piriform.com/index.php?showtopic=35459

- Did you select "Wipe Free Space" as well ? Because that triggers something in Windows that makes Windows delete one or more System Restore Points. Windows sees that the amount of free disk space becomes too low and then it starts wiping those System Restore Points. - Defraggler has an option called "Disable VSS". Tick that box and I would assume those System Restore Points won't disappear anymore.

Another GUI bug in Defraggler (v2.18.945) !!!! I took the following steps and I noticed DF's behaviour changed: 1. - Open Defraggler and let the program analyze one disk. 2. - Reduce the size of DF the GUI window from "Maximized" (full screen) to say 60% of the screen. (it happens also when the DF GUI window is maximized. One then has to enlarge the column's width.) As a result the columns "Last Modified" & "Path" are no longer shown in the filelist in the DF GUI window. 3. - Click on each column header (e.g. "Path" or "File name") once to sort the info in that column. DF behaves as it should. E.g. when I click on "Path" (as many times as I want) then the column "Path" and the info in that column remains visible in the DF GUI window. 4. - Now set DF to work. Select a number of files and let the program defrag those files and after that the behaviour of DF changes. 5. - Whenever I click on any column header to sort the info in that column the GUI "freaks out". E.g. when I click on "Path" (situation as in the 1st screenshot) to sort that column, the column "Path" disappears out of the visible part of the DF GUI window and the entire column "Filename" shows up in the DF GUI window, in the left hand side of the DF GUI window. (See 2nd screenshot). And that happens everytime I click on a columnheader to sort the info in that column. It even happens when I click on the "Filename" header when that header/column is only partially visible in the DF GUI window. This behaviour is VERY confusing/annoying for a user and I consider it to be a bug. Because it doesn't happen when I haven't defragmented any files. In other words: when I click on the "Path" column header (to sort the info) the GUI changes from screenshot #1 to screenshot #2.

- I am not a computer expert but I have enough experience with Defraggler to have a hunch of what could be going on (e.g. WorkingSet, Filecache, CPU, .......... etc.) - No, I won't give you my HD details. It's not important. - Giving more details (working set growing) is good. You still need to provide more details, though. What Defraggler option did you use ? Defragment (+ optimize) the entire disk ? Defragment the fragmented files only ? Does it occur with every defragment option ? What happens to the size of the filecache during defragmentation ? That kind of details certainly will help the developers to see where they need to improve Defraggler.

- Fixing memory leaks is not that simple. There's only a limited amount of things that can be done. Programs are/can be very complex. - Defraggler does reduce it own memory usage. I have seen it happen. But it seems it happens only on systems with a limited amount of memory (512 MB ?, 1 GB ? 2 GB ?, ....... ). - The filecache growing and growing is not a "memory leak". - What option are you using ? Defrag entire (logical) disks ? Or are you only defragmenting fragmented files ? If you want to defrag entire drives then it makes perfect sense to cache as much files as possible in the file cache. Then it's no wonder the filecache grows and grows.

- When the system uses A LOT OF RAM (e.g. filecache) then the amount of "Standby" memory (See Resource Monitor) is very low. And that "Standby" memory is precisely the cached memory. That's why there're A LOT OF "cached read requests" to the harddisk, as well. - I assume some other program interferes with Defraggler and makes Defraggler use so much memory. - Install PcWinTech's Cleanmem. It reduces memory usage and let it collapse the filecache as well. The program also can tell you how large the filecache is. Some programs simply won't release file cache memory.

Then I would assume that you've spotted a bug in CCleaner. Developers of CCleaner, are you reading this ? Bug to be fixed !!!

Didn't know that.

It means that the WMI subsystem in Windows is corrupted/damaged. There's a program called "Windows Repair All In One" that can fix that problem. (www.tweaking.com). Follow the instructions provided. Disable internet & Anti virus and run the program with the default boxes ticked (Under the tab "Repairs"). Running the program should take about 20 to 30 minutes.

@Login123 : Each next version (IE, FF, ...... ) is Always larger in size and then comes it at no surprise that the new version requires more computing power/a more powerful system/more RAM or one should accept that the new version is slower on an older system. Tried FF (have it installed but I don't use it because of certain features/characteristics).

Defraggler could optimize the system files that are read by the Operating System upon start up. These files/directories are listed in the file "C:\Windows\Prefetch\Layout.ini". So, DF should read all the files/directories mentioned in that file and put all the files/directories together in one place on the harddrive. Or perhaps there's an Windows' API or MSDOS command available that allows DF to put Windows to work to do the task as described above.

Topic: "Clean Recycle Bin" behaviour. Odd. I ran CC v4.18 again but this behaviour (see previous post) didn't show up any more. Did I overlook something ? Don't know. But it doesn't matter anymore. Because I downloaded & installed CC v4.19 and it correctly showed/recognized the files & the size of the files in the Recycle Bin. It also recognized that those files were on the USB harddrive. And the files were deleted by CC.

- The OP didn't disclose whether it was a 32 or 64 bit XP version. XP has been available in a 64 bit version. - The simple fact that the pagefile gets fragmented leads me to believe that Windows enlarges the pagefile. - There could be happening something else. Some files (metadata files ???) could be placed in the middle of the drive and prevent the pagefile from getting/being defragmented. - I assume the OP increased the size of the pagefile later ? Solution: - Switch off the pagefile feature, move all valuable data to another drive, reformat that particular drive, use the build-in Windows defragmentation program to optimize the drive and then enable the pagefile, Make the pagefile slightly smaller than the size of the drive. Perhaps then the pagefile remains defragmented. - Perhaps you need to delete the partition and then re-create the partition ?

- According to my info, every time when both the pagefile & the memory are full then the pagefile WILL be enlarged and potentially fragmented, no matter what. Even when you have set the pagefile to a maximum size. that's why reducing memory usage (with Cleanmem) will reduce the need to write to the pagefile. - Cleanmem has a socalled "Mini Monitor" that displays an icon in the system tray. If that value (as displayed by the icon) remains very high (say ~ 70 or ~ 80%) then I would recommend installing more memory. That's the best way to improve system performance & keep the page file defragmented.

- I would advice against placing the pagefile on a different HD (except when the main HD is a SSD), because it will decrease overall system performance. It then takes the system more time for the drive to read & write data from/to that drive. - Windows itself will place the pagefile on a different drive when the amount of free space on a drive is insufficient. I have seen it happen on a XP & Win 7 system. - Fragmentation of the pagefile occurs because Windows needs to enlarge the pagefile and can't expand the pagefile without fragmentation. That enlargement of the pagefile on its own slows down your system. - Install PcWinTech's Cleanmem. It reduces memory usage every 15 minutes. Reducing memory usage, means reducing or even eliminating Windows' need to write data to the pagefile and disk I/O is - comparatively - slow. Then the chance of having a fragmented pagefile will be reduced significantly.

Ditch the name Nokia and then completely botch it ??

The surge in popularity for IE comes at the expense of Firefox. Seems IE 11 is better than the last version of Firefox ?

- Run the program is Safe Mode. Perhaps then you can remove those entries ? - Perhaps the permissions are modified and then one can't remove them. Try if running "Tweaking's windows Repair" (www.tweaking.com) will help to solve the issue.

Satya Nadella admits that MS "got a number of things wrong": http://www.businessinsider.com/nadella-admits-windows-8-was-wrong-2014-10 And "Business Insider" came with an article on how windows 10 will be different from Win 8 http://www.businessinsider.com/windows-10-features-2014-9 http://www.businessinsider.com/windows-10-features-2014-9?op=1

No, I also didn't have any problems. But I pulled the update anyway. Don't know if I should remove the other updates as well.

New version of "Windows Repair" available (v2.10). Improved repairs for e.g. "Windows Update". One can tweak the program to make sure all repairs run in Safe Mode. www.tweaking.com