Alan_B

I would guess the next version is unlikely. Quite possibly never because. so far as I know, Piriform uses published API's to accomplish tricky complicated high risk actions such as Secure Deletion and Defragging, and many "experts" argue about whether files are in WinSXS with corresponding Reparse points in System32 - or vice versa, and I have found that CMD.EXE can be in both categories Therefore in my view the determination of which patches have become redundant and then their eradication is a "tricky complicated high risk action". If you are in a hurry you can always create a shortcut to a *.BAT file that launches Cleanmgr and then runs CCleaner. http://www.ghacks.ne...e-cleanup-tool/ http://support.micro....com/kb/2852386 http://support.microsoft.com/kb/315246

You can create a *.BAT script which contains something like SET "ANY TEMP FOLDER=c:\someuser\downloads\saved\custom\whoknows\why\]whenwillwe\okaylets\TEMP\*.*" CCLEANER.EXE That will run CCleaner with a new temporary and unique set of "variables in windows environmental settings", which will include whatever you define as being the variable %ANY TEMP FOLDER%, and this variable can be used by Winapp2.ini or CCleaner.ini. You should not remove logs or temps which would annoy those who can now or in the future cause harm to your career I really think it might be safer, and simpler, and release a lot more space on the server system, if you render inaccessible to everyone but yourself any drive\partition\folder for which you can see no legitimate authorised purpose. When this causes a problem the particular region can be re-enabled. After this has stabilised you could ensure you have backups of all that appears to be safe to remove, and then remove from the servers - and should that go wrong you locate the relevant backup and restore.

I disagree. I see a Möbius loop protruding out of hyperspace

You can create your own WinApp2.ini file with variables. This topic will give you a lot of information and guidance if you want more indormation http://forum.pirifor...showtopic=32310 That topic starts a link for downloading the latest semi-official WinApp2.ini file, which includes variables in lines such as FileKey1=%ProgramFiles%\Acoustica CD Label Maker\thumbs|*.*|RECURSE FileKey2=%AppData%\Acoustica\CD Label Maker\cache|*.*|RECURSE Alternatively, if you use the portable version of CCleaner, or else with the installed version and using the Options / Advanced / "Save all Settings to INI file" option, you will have a file CCleaner.ini that you can manually edit with Notepad.exe and insert lines with a variable such as :- Include1=PATH|%APPDATA%\Adobe\Flash Player\AssetCache\|*.*|RECURSE Include2=PATH|%APPDATA%\Macromedia\Flash Player\|*.*|RECURSE Include3=PATH|%APPDATA%\vlc\|*.*|REMOVESELF I suggest that you take extreme care to NOT click "Run Cleaner" until you have first used "Analyze", and then use the "Save to text file" option, and then inspect the output and determine which people will be annoyed, and whether they will have mercy on your soul And finally, before you "Run Cleaner", make sure your resume is fully up to date and ready for your next job search

This portable freeware utility can capture and save to a text file the results presented by Recuva and may meet your need http://www.nirsoft.n...ils/sysexp.html

This could be an exciting experience I mean that in the worst possible way I think I read an article last year that Windows 7 updates prior to SP1 would remain resident in WinSXS even though they were not needed, but there was a manual technique (possibly involving some tool) of removing them. I obtained the impression that removing subsequent updates would be at my own risk. Will using this new option in "Windows Cleanup" similarly be at my own risk ?

I mentioned 8.1 because it ought to be safer than 8.0 and although finnipinni refers to W8 it was not clear to me that he was excluding 8.1. Regardless, both 8.1 and 8.0 and all other versions of Windows are vulnerable. http://pcsupport.abo...tch-tuesday.htm Alan

A screen shot showing all the details that "Windows Disk Management" can give on this drive might possibly lead to a solution.

Now you appear rather obnoxious in your response, and unbelievably foolish in dismissing the possibility of Malware. I do not believe that when you posted on the 6th you had already installed the Patch Tuesday updates that were issued today and which affect Windows 8.1. http://pcsupport.about.com/b/2013/10/08/patch-tuesday.htm https://community.qualys.com/blogs/laws-of-vulnerabilities/2013/10/08/patch-tuesday-october-2013

Another possibility is to post in your own language so that those with experience of "Google Translate" can convert to English.

Thanks for the update which covers the basics. I have no relevant experience with image files so will now retreat and leave it for those who can help to take it from here Regards Alan

Is this the result of AVG etc choosing a simple password like "123456" ?

Welcome to forum. On what physical drive and partition letter were these files before deletion ? To what physical drive and partition letter have you restored these files ? What version of Windows ?

I was using version 3.14 I was running Virtual Windows 7 64 bit on a Real Windows 7 64 bit platform. This was my first post on 1st Sept 2011, and I bumped it on 17th and still got no response. https://communities....m/thread/326929 This was a separate topic which got no response so I gave up and moved onto VirtulaBox https://communities....m/thread/328856 I have just looked at the very recent topics, and again it appears that no one gets any solutions. This has 14 posts, the first 12 all report that version 6 fails to initialise after an upgrade to version 6. and the last tow posts are users that fixed their problems by un-installing 6 and installing 5.2 and the last one even tried a total purge of every trace of VMware followed by a fresh install of 6.0, AND AGAIN even that failed to initialise. https://communities....m/thread/457667 Your Mileage May Vary It is especially annoying that the destruction of free space on my host was NOT due to the Virtual system crashing, but apparently even the latest version is designed to always transfer files via the Host computer %TEMP%, THEREFORE it is designed to transfer malware into the Host system even if the virtual system has not crashed. https://communities....m/thread/457688 If your virtual machine has no Internet Access, and if you have used dependable malware scanners designed to detect Windows malware, I think your Windows system should remain safe if those files broke through the barrier out of VMware and back into Windows. Please note that :- I vaguely remember reading that it is possible to receive an unsolicited malware file that can infect both Windows and also Linux; I cannot remember where I read that - or if in fact it was just a bad dream

I fully agree that restoring a partition table is dangerous. My Laptop had 4 off NTFS partitions and 2 off FAT32 partitions plus a hidden FAT? "Secure Zone" partition created and used by Acronis. One day the partition table broke and the computer could not boot. The Linux based Minitool Partition Wizard Boot Rescue CD was able to create a new partition table. After many attempts it failed to include the Acronis Secure Zone so I gave up and attempted the other 6 partitions. When that looked plausible I committed to the writing of a new partition table for only those 6. I think that when I committed there was no way of then adding the Acronis special without endangering the other 6. The NTFS partitions were well recovered. When I booted up Windows promptly demanded that I should run chkdsk and reboot to fix fatal errors in one of the FAT32 partitions. That was fixed by chkdsk but innumerable errors were fixed and I never trusted that data again. Once all was working I ran chkdsk on all the other partitions and the other FAT32 partition had a large number of errors detected, but the 4 off NTFS partitions only needed a few fixes to some sort of Security logs. That was the day that I finally believed that data was safer on an NTFS partition than a FAT32 partition. I fully agree with the safety of creating an image backup before attempting to write a new partition table.

More than two years ago VMware had a massive security hole and gave absolutely no support response to two separate issues which I raised. My primary issue was that when I drag-drop-copied something between two partitions on my SECONDARY HDD, one of which was for access by the virtual machine, something went wrong and the virtual machine crashed. Then Windows Explorer had a great big red bar showing that I had zero free space available In system partition C:\. on my PRIMARY HDD there was too much copied to the virtual machine I discovered that because VMware was NOT available as a portable application, and could only be installed, even though most of it was installed on the secondary HDD, it still used system resources including %TEMP% in my system partition C:\ and the virtual machine had stuffed a gazillion Gigabytes into %TEMP% on my system partition C:\ So far as I am concerned if a virtual machine can disgorge its "sandboxed" contents into my operating system when I innocently drag-drop-copy, it will do the same when "sandboxed" malware deliberately forces a buffer overflow. I uninstalled VMware and replaced it with VBox from Sun/Oracle. Initially I had problems with VBox, but each time a had a quick helpful response and it very quickly worked well for me, Regardless of whether or not VMware has by now fixed their issue, there was no response to the two topics which I posted on their forum, and I gave up looking after two years. Both VBox and VMware have their own user forums - which I have not visited for a few years. I suggest it might be worth visiting those forums to get an idea of the percentage of problems that are never resolved, and the average time taken before a problem is resolved.

The windows on the house serve as microphone diaphragms, and lasers in space can detect the vibrations.

Yes, that is what I meant. I would expect most of the original 150 GB free space to be at the "far end" of the disk The E:\ partition is at the start of your disk so that represents 31.9 GB of the original files that has been over-written. There remain 320 GB that could be recovered, ASSUMING that "after formatting over" refers to a Quick format and not a slow overwrite format. Was your external drive originally formatted as FAT32 or NTFS ? What version of Windows do you have ? I have limited experience with Recuva so I now "tag out" and defer to others with experience. All the best Alan

Welcome to forum A screenshot of Disk Management will give far more valuable information on your situation.

Disk Management shows that G:\ is assigned to a 100 MB "System Reserved" volume. Recuva is showing that System32 and SysWOW64 both exist in G:\. Those two things CANNOT be true at the same time. Either drive letters got reassigned in the time between those screen shots, or there is stupendous confusion caused either by Reparse points within System Volume or by the laptop damage that needs $1000 to rebuild.

Desktop Videos instead of Desktop Screenshots would be a wonderful enhancement to Dennis's Desktop topic http://forum.piriform.com/index.php?showtopic=39586 Who is going to try first

UTTER RUBBISH - YOU NEVER MENTIONED DISK OR TEMPERATURE IN THE TITLE. The title falsely indicated that Speccy would cause damage to a computer, and nowhere in your initial diatribe did you mention temperature. Only in post #3 did you refer to the disk temperature. So far as I am concerned your initial tile was Libel. You were not being kind when you agreed to your false title being changed to an accurate statement.

WARNING TO EVERYONE It may be hazardous to the safety of your registry if you download a genuine registry backup from another computer in good condition. A computer that has been damaged by a version of CCleaner that is packed with nothing but Winapp2.ini plus CCenhancer is no safer and ... If this version was NOT downloaded from Piriform or FileHippo, then other more dangerous things could also have been packed in with it by a dishonest site. I for one am not going to download what might be a *.REG file but could equally well include a Zero Day exploit.

Only people that use Windows 8 or Apple iPhones get to believe it and feel it

Your operating system(s) and whether your external drive is FAT32 or NTFS could be reasons. It has no relevance to me so I have forgotten precise details, but I think that if an external drive receives files from one user on an XP system then another user on a Windows 7 System may be prohibited from access, or it might have been the other way round, or something else of this nature.