Willy2

- I also noticed that DF (v2.20) still (tries to) move(s) a number files/folders that start with an "$" sign. E.g. ("C:\$Extend") when I use the procedure as described in the previous post. Is this done intentionally or is this to be considered to be a bug. I personally think these files should be filtered out and excluded from being moved.

I can report some good news and also have some bad news. It seems that the program code has been improved (somewhat). Although it didn't work as well as would have hoped (I didn't have enough time to let the program finish by itself. Otherwise I would have to wait for - at least - 2 (??) or 3 (??) extra hours). I ran Defraggler (v2.20) ("Defrag" >> "Defrag" in the main screen of DF) with a number of settings in Defraggler.ini (See attachment). 2 folders ("C:\MicroSD" and "C:\Regbackup") weren't included in the "Exclude" pane/screen. In the subfolders of "C:\MicroSD" there're only *.MP3 files and A LOT OF those *.MP3 files are - at least - 5 MB or larger. But each of the "C:\MicroSD" subfolders also contains one file that's smaller than 2 MB. Based on what I saw in the main screen of DF, the program moved all *.mp3 (in "C:\MicrosSD") files that were smaller than 2 MB towards the beginning of the drive. But all other *.mp3 files (each > 5 MB) from the same (sub-)folder(s) were moved towards the end of the (logical) drive. In other words: The option "Do not apply minimum file size ................. " doesn't work, is overlooked, - at least - in this particular instance. I want to do more testing but that will take much more time.

- Are these bugs language related ?? I have seen programs that were written in the USA and didn't work (properly) on my dutch system. So, I wouldn't be surprised to see that (supposed) bugs in DF are actually the result of running on a non english system.

Tested DF v2.20 even more and somethings that weren't fixed in this version. (I reported this odd behaviour before in this thread). - The "Exclude" option (Settings, Options, Exclude") doesn't function well. I added a number of folders to that list (say 30) and then removed some 10 folders, restarted DF and opened the "Exclude" screen again but in that screen I still saw 30 folders listed (some of them even 3 times!!!) !!! If I want to reduce the amount of folders in the Exclude screen (and "Defraggler.ini") then I have to manually (!!!!) remove a number "ExcludePath=" lines. - Tried to move a bunch of *.mp3 files to the end of the drive and it worked exactly one time (i.e. the 1st time) in spite of having tried this function/feature some 20 times. - When DF is busy (trying to) move files to the end of the drive then the user still can open the "Settings" menu(s) and see what the settings are but those options can't be changed. But there's confusion because DF tells me that the option "Move large files to end of drive" hasn't been selected. (while I do know it has been selected !!!!).

- In the folder mentioned above Windows places the Original updates files before installing those updates. and these files aren't removed after an Update. - Windows Update archives all old system files in the (infamous) "C:\Windows\Winsxs\" folder. If you want to reduce the size of that folder then you MUST use the Windows "disk clean Up" tool. CCleaner can't do that.

Add the folder "C:\Windows\SoftwareDistribution\Downloads" to the list of custom folders to be cleaned by CCleaner.

- First (small) bug in DF v2.20: The 1st time I ran DF (1st time after I installed this DF version), the option "Exclude System Restore files" was ticked but nontheless it showed the System Restore files. Only the 2nd and every next time this option works well.

And I love to "put the pedal to the medal" when it comes to testing of Defraggler (v2.20).

New version of Windows Repair (v3.81) available. It turns out that Windows Vista is very "delicate". Register a number of files in the wrong order/sequence and VSS breaks. Although "Repair VSS" does register the files in the right order. New code used for the controls of WR. I was told that the new controls are more reliable and (much) less likely to cause crashes, hiccups , etc. But only time will tell. As said many times before: Feedback (bug reports & suggestions) are very welcome and should be posted on the forum of http://www.tweaking.com/ Or send the author of WR a PM.

As a result of the "bug" mentioned above, here's a suggestion for the next SPECCY version: Instead of using the word "RunSpeccy", use the word "SpeccySkipUAC" to be added to Task Scheduler. That would be less confusing. It could be one of those mysterious "Minor bugfixes".

- But then the description in TS should be different. Just like the description for CCleaner. There the description is "CCleanerSkipUAC". - Why does such an entry in TS matter ?

I ran SPECCY v2.19 and I saw something I don't like. When I look at what's in Task Scheduler (TS) (with e.g. CCleaner) then it turns out that SPECCY has added an extra task to TS without my consent/approval !!!!! Are the developers of SPECCY planning to add or already have added a feature where the program is run upon start up ? Did I overlook one thing in the installation program ? What's also weird is that there's very little info in TS on what SPECCY is supposed to do. Only in the "Action" tab of TS (next to the "Trigger" tab) there's some info: "C:\Program Files\Speccy v1.29\Speccy64.exe" I also attached the *.xml file that was exported from TS.

- Did you let Windows manage the size of the pagefile(s) ? I know that some programs have an EXTREMELY lousy memory management, use LOTS of memory and need a VERY large pagefile. I have come across ~ 5 of such cases where changing this setting helped to solve the problem. - Run Piriform's SPECCY. Then make a snapshot of your system( File > Publish Snapshot) and post the weblink that pops up in your next reply. Perhaps there's something special in your system setup that makes Defraggler crash. - Does Windows produce any logs when your system crashes as a result of this memory problem ? In "Eventviewer" ? Are there any crashdumps ? If so then post them as well. - Run MINITOOL-Box. http://www.bleepingcomputer.com/download/minitoolbox/ Tick the all boxes that you think are appropriate , hit "GO" and attach the file that's produced by this program to your next reply. - Run "Defraggler" in debug mode and post the logs/info it generates. http://www.piriform.com/docs/defraggler/troubleshooting/running-defraggler-in-debug-mode I am convinced the developers of Defraggler will appreciate all the extra info they can get from you. - "RADAR - Windows Automatic Memory Leak Detection" is some sort of program that's used by MS to spot memory leaks. Seems MS has an active (& hidden) program running that tries to spot those memory leaks (in real time ???). Can't find too much info on this software on the internet. It remains - more or less - a mystery.

Today I used "Defragment Free Space" on a MicroSD card but DF refused to move file. (Yes, I know. I shouldn't use this feature on a SD card, it reduces the life of such a card). See attachment. I marked 4 files in red. I thought those 4 files would be moved by this DF feature but they stayed where they were placed. The developers do have some work on their plate.

- Did you tell Windows to limit the size of the pagefile to a certain amount of MBs ? Changing that to "let Windows manage the size" could eliminate those crashes. - No, not all "RAM opitmize" programs are "pseudo-tools" or "snake oil". There's an Windows API called "EmptyWorkingSet()" and that makes Windows to release "unused" memory. Programs like PcWinTech's "Cleanmem" use that API to kick the Windows memory management into action (like releasing "unused" memory). "Cleanmem" also can collapse the file cache (can be VERY big (GBs)) and reduce Defraggler's (DF) and overall memory usage. - I think the solution could be very simple. Defraggler Always analyzes a drive before taking any action. So, Defraggler could reduce its own memory usage (e.g. using that one API) before even analyzing a drive. - But it seems the developers of Defraggler aren't too interested in issueing an updated & improved version of DF. That's a pity because DF still has a number of other bugs.

After the Windows Update of january 2016, Microsoft will reduce support for a number of Internet Explorer versions. - Support for IE 7 & IE 8 will be dropped all together. - Vista users will only receive support for IE 9. - Win 7 & Win 8 users will only receive support for IE 11. Makes perfect sense. It reduces the workload for MS. And when I want to download the latest update packages it makes searching for those updates A LOT easier. Is MS going to combine the 32 bit & 64 bit update packages into one download ? I certainly would hope so. http://www.computerworld.com/article/2490996/microsoft-windows/microsoft-slashes-ie-support--sets--huge--edict-for-jan--2016.html (Was this already reported on this forum in the past ??? For - at least - me, it was news for me. Luckily, I use IE 11)

- The program code of DF definitely needs another improvement. I used "Defragment Free space" in DF v2.19 to defragment a MicroSD card but it looked like it failed to do its job. Looking at the file map of DF I assumed DF would move some 6 to 9 files but DF moved only 1 (one) file. Then I tried the same function again and again. But to no avail. DF refused to move any file anymore. Odd, very odd. - Can we expect a new version of Defraggler in the (near) future ? The code still needs to be improved. (See previous posts in this thread).

- Disable Defender on your Win 8 system and run Speccy. And see what Speccy reports. - Run Speccy on your Win 7 system. What does Speccy report ? Does it report the proper status of Defender ? - Defender is run as a Service. I think Speccy looks for one or more specific files to see whether or not Defender exists. But to see whether or not Defender is "Enabled" checking the status ("Running" or "Stopped") of the appropriate Service should suffice. Or perhaps Speccy simply assumes that on a Win 7 (& Vista) system Defender Always is enabled. Well, on my system Defender is "Disabled". Anyhow, Speccy's program code needs to be improved.

- @Trium: Do you have Win 8 or newer ? I still use Win 7. - I ask because Windows Security Essentials (in Vista & Win 7) is renamed to "Windows Defender" in Win 8 and higher. - Are there more users with Vista or Win 7 that have the same problem ?

Installed v2.19 yesterday but it still doesn't know what to make of what's going on with "Windows Defender" on my laptop. Under the header "Windows Defender" (in the "Operating System" screen) Speccy displays the text "Windows Defender: Enabled". But in the list of Services Speccy displays the text "Stopped Windows Defender". That's an inconsistency that needs to be resolved in the next Speccy version. No, it's NOT a translation error because this inconsistency also shows up when I change the language from dutch to english, spanish, german & french. I think the most likely explanation is that when the program code has noticed that the Defender Service has been switched off, Speccy's pointer points to the text string "Enabled", instead of "Disabled". If this is the case then it shouldn't be too difficult to change the program code. Or perhaps there isn't a text string called "Disabled" available for "Windows Defender" at all. See my (updated) Speccy snapshot.

- What's the size of the memory ?

There's a tool that supposedly enables the user to kill (all ?) GWX related stuff. I don't know if I want to try it at all. Seems Microsoft changed its mind A LOT OF times. http://www.infoworld.com/article/2995915/microsoft-windows/unwanted-win7win81-upgrades-to-win10-can-now-be-stopped.html

"How To Geek.com" confirms the news. http://www.howtogeek.com/232176/whats-new-in-windows-10s-first-big-update-the-windows-10-fall-update/

"Petition asks Microsoft to fix two glaring shortfalls in Windows 10". Brilliant idea. http://www.infoworld.com/article/2994120/microsoft-windows/petition-asks-microsoft-to-fix-two-glaring-shortfalls-in-windows-10.html @Nergal: Accidentally "pushing out Win 10" ??? I don't think so. I am NOT convinced. I think Microsoft simply tries to "Push the envelope" as far as possible. Only when they run into resistance then they will undo (one or more of) those step. MS simply tries to see with much they can get away with. Time for MORE pushback !!!!

Odd. Now the "Update to Win 10 Pro" on my Win 7 system is gone from the "Optional Updates" screen. But the "Update to Win 10" system tray icon is still "alive & kicking" every time I start my system. Odd.