<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Serious Disk Cleanup Problem in Windows Caused by Broken Registration</title>
	<atom:link href="http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/</link>
	<description>Troubleshooting Windows 7/XP/Vista, Fixes &#38; Tweaks &#124; General Productivity Tips</description>
	<lastBuildDate>Fri, 20 Nov 2009 16:00:45 -0800</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lyzek</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-8776</link>
		<dc:creator>Lyzek</dc:creator>
		<pubDate>Sat, 29 Aug 2009 16:36:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-8776</guid>
		<description>August 29 2009.
Thanx tons, I just want to add that reading this left me very confused (as I lack knowledge of the technical wording here ) , but I eventually clicked the link (... cleanmgrfix.reg ...) under the heading (... Fixing the Disk Cleanup WER Handlers in the Registry ... ) and found a warning about adding to my registry. I proceeded to run the download, based on Felipe from Chile&#039;s post above and it showed the file location. I double-clicked on the file and Voila, my problem is fixed. Many thanx again ... Lyzek</description>
		<content:encoded><![CDATA[<p>August 29 2009.<br />
Thanx tons, I just want to add that reading this left me very confused (as I lack knowledge of the technical wording here ) , but I eventually clicked the link (&#8230; cleanmgrfix.reg &#8230;) under the heading (&#8230; Fixing the Disk Cleanup WER Handlers in the Registry &#8230; ) and found a warning about adding to my registry. I proceeded to run the download, based on Felipe from Chile&#8217;s post above and it showed the file location. I double-clicked on the file and Voila, my problem is fixed. Many thanx again &#8230; Lyzek</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Felipe Peña</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-8765</link>
		<dc:creator>Felipe Peña</dc:creator>
		<pubDate>Fri, 28 Aug 2009 02:38:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-8765</guid>
		<description>Hey 
I&#039;m Felipe from Chile, I have to say, this post is very helpful!
I was about to clean up 32GB but I found it very strange !
So I search the web for problems related to Disk Cleanup and I found some pages like this one.
Thanks for post this.  I think, it could definetily help a lot of people.
I have to say that my &quot;Per user .. &quot; and &quot;System queued&quot; are just 55 MB aproximadtly, but the item called &quot;Temporary files&quot; is 32.0 GB.

I have to say I&#039;ve read a lot of problems to other users to have deleted all of that data.  Big lost for them, and I&#039;m very sorry. 

Be carefull, and I suggest you to delete temp files with another tool.
I suggest Microsoft to fix this...I have Service Pack 2 and this problem as I can see has been detected a lot time ago.

Be happy :)</description>
		<content:encoded><![CDATA[<p>Hey<br />
I&#8217;m Felipe from Chile, I have to say, this post is very helpful!<br />
I was about to clean up 32GB but I found it very strange !<br />
So I search the web for problems related to Disk Cleanup and I found some pages like this one.<br />
Thanks for post this.  I think, it could definetily help a lot of people.<br />
I have to say that my &#8220;Per user .. &#8221; and &#8220;System queued&#8221; are just 55 MB aproximadtly, but the item called &#8220;Temporary files&#8221; is 32.0 GB.</p>
<p>I have to say I&#8217;ve read a lot of problems to other users to have deleted all of that data.  Big lost for them, and I&#8217;m very sorry. </p>
<p>Be carefull, and I suggest you to delete temp files with another tool.<br />
I suggest Microsoft to fix this&#8230;I have Service Pack 2 and this problem as I can see has been detected a lot time ago.</p>
<p>Be happy :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim_O</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-5763</link>
		<dc:creator>Jim_O</dc:creator>
		<pubDate>Sun, 11 Jan 2009 16:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-5763</guid>
		<description>This is NOT unique to Vista. I have seen this occur on three separate XP (all Home) systems. The error has only been observed in the Temporary Files selection where the folder entry location has been lost in the registry. The suttle indication something is amiss is that there is no kb or Mb extension as to the size of the files found in the Disk Cleanup selection screen. WinOptimizer and Registry Mechanic were the tools of choice for these three systems. I don&#039;t believe it&#039;s a MS problem. If these tools are being used pay close attention or lose a weekend!</description>
		<content:encoded><![CDATA[<p>This is NOT unique to Vista. I have seen this occur on three separate XP (all Home) systems. The error has only been observed in the Temporary Files selection where the folder entry location has been lost in the registry. The suttle indication something is amiss is that there is no kb or Mb extension as to the size of the files found in the Disk Cleanup selection screen. WinOptimizer and Registry Mechanic were the tools of choice for these three systems. I don&#8217;t believe it&#8217;s a MS problem. If these tools are being used pay close attention or lose a weekend!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-4886</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Thu, 04 Dec 2008 02:04:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-4886</guid>
		<description>This cant be true ...this must be what everyone who experienced the same must have thought...i still cant believe it!!!

Quick Info - YES!! this problem can be caused by vista RegCleaner only!!!! (No viruses, no crappy regoptimizer toolz involved...just a plain and clean mashine)

&quot;Lets clean up a little bit&quot; were his(my) last words ...and the system never booted ever since!!!Fucking Hell!!!

...anyone has found out anything?..any hope?...

cheers N</description>
		<content:encoded><![CDATA[<p>This cant be true &#8230;this must be what everyone who experienced the same must have thought&#8230;i still cant believe it!!!</p>
<p>Quick Info &#8211; YES!! this problem can be caused by vista RegCleaner only!!!! (No viruses, no crappy regoptimizer toolz involved&#8230;just a plain and clean mashine)</p>
<p>&#8220;Lets clean up a little bit&#8221; were his(my) last words &#8230;and the system never booted ever since!!!Fucking Hell!!!</p>
<p>&#8230;anyone has found out anything?..any hope?&#8230;</p>
<p>cheers N</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tctucom</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-4575</link>
		<dc:creator>tctucom</dc:creator>
		<pubDate>Fri, 21 Nov 2008 08:49:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-4575</guid>
		<description>A very long and focused day!

It is (our Registry Cleaners) that are the culprints. It is not the fault of SP1. I accused SP1 of this problem early on, but I was dead-wrong.

I spent the day reinstalling Vista Business and downloading Windows updates (including customs). I then began to tweak the system. When I was finished with processes and services I made a back-up of the C:drive then installed and ran (RegistryFix Version 7).

As each group of errors was found, I would abort the scan and open each error to see where it was pointing to in Windows Registry. Low and behold when I got to the errors for &quot;Complete Registry Scan&quot; there were the 4 Keys for Windows Error Reporting!  RegistryFix was going to delete those keys if I did not choose &quot;ignore&quot; each one.

DANGER Will Robinson!

I restarted the scan and allowed it to find and what it interpreted as errors, made a backup of those errors so I could reverse the cleaning, then allowed it to delete the keys.

I then ran Disk Cleanup and sure enough, there were all the huge files in GB&#039;s and 100&#039;s of MB&#039;s all related to Windows Error Reporting and Archives. The four infamous keys had been deleted.

No Reboot yet.

I then restored the keys through RegistryFixe&#039;s Backup and ran the Disk Cleanup again without a reboot. When it finished the four Keys were (not missing)! I allowed Disk Cleanup to finish and restarted the computer. Bingo! Right back to the desktop without a hitch.

So..bottom line is the Developers of our Registry Optimizers/Cleaners need to figure this out on their end. Believe me! I love to dump on M$ for allowing us to be the guinea pigs, but this time I know 100% that it has nothing to do with SP1. It has everything to do with our third party Registry cleaners/optimizers.

Took a long time but it&#039;s worth it knowing that you all can do the same thing and adjust your Cleaners to &quot;ignore&quot; the Reg Keys for Windows Error Reporting before you finish the cleanup process. It&#039;s tedious but it&#039;s worth it.  Phew!</description>
		<content:encoded><![CDATA[<p>A very long and focused day!</p>
<p>It is (our Registry Cleaners) that are the culprints. It is not the fault of SP1. I accused SP1 of this problem early on, but I was dead-wrong.</p>
<p>I spent the day reinstalling Vista Business and downloading Windows updates (including customs). I then began to tweak the system. When I was finished with processes and services I made a back-up of the C:drive then installed and ran (RegistryFix Version 7).</p>
<p>As each group of errors was found, I would abort the scan and open each error to see where it was pointing to in Windows Registry. Low and behold when I got to the errors for &#8220;Complete Registry Scan&#8221; there were the 4 Keys for Windows Error Reporting!  RegistryFix was going to delete those keys if I did not choose &#8220;ignore&#8221; each one.</p>
<p>DANGER Will Robinson!</p>
<p>I restarted the scan and allowed it to find and what it interpreted as errors, made a backup of those errors so I could reverse the cleaning, then allowed it to delete the keys.</p>
<p>I then ran Disk Cleanup and sure enough, there were all the huge files in GB&#8217;s and 100&#8217;s of MB&#8217;s all related to Windows Error Reporting and Archives. The four infamous keys had been deleted.</p>
<p>No Reboot yet.</p>
<p>I then restored the keys through RegistryFixe&#8217;s Backup and ran the Disk Cleanup again without a reboot. When it finished the four Keys were (not missing)! I allowed Disk Cleanup to finish and restarted the computer. Bingo! Right back to the desktop without a hitch.</p>
<p>So..bottom line is the Developers of our Registry Optimizers/Cleaners need to figure this out on their end. Believe me! I love to dump on M$ for allowing us to be the guinea pigs, but this time I know 100% that it has nothing to do with SP1. It has everything to do with our third party Registry cleaners/optimizers.</p>
<p>Took a long time but it&#8217;s worth it knowing that you all can do the same thing and adjust your Cleaners to &#8220;ignore&#8221; the Reg Keys for Windows Error Reporting before you finish the cleanup process. It&#8217;s tedious but it&#8217;s worth it.  Phew!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The PC Doctor&#8217;s blog &#187; Blog Archive &#187; &#187; Vista/Disk Cleanup bug</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-2804</link>
		<dc:creator>The PC Doctor&#8217;s blog &#187; Blog Archive &#187; &#187; Vista/Disk Cleanup bug</dc:creator>
		<pubDate>Wed, 20 Aug 2008 16:20:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-2804</guid>
		<description>[...] I&#039;ve not come across the bug personally but it is well documented over on the Winhelponline blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;ve not come across the bug personally but it is well documented over on the Winhelponline blog. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Suzanne</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-3/#comment-2803</link>
		<dc:creator>Suzanne</dc:creator>
		<pubDate>Wed, 20 Aug 2008 15:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-2803</guid>
		<description>Well this happened to me the weekend of August 9th. I didn&#039;t know about this website or had even heard of this issue.  Like Kelly commented above, I thought the GB a mistake (I have seen Windows programs misreport file sizes before) and let Disk Cleaner do its evil thing.  I am still in the process of trying to recover my data because then Windows XP (my backups had been done in XP b/c my Vista machine was new), deciding that my backup was corrupted about a 1/4 way through restoring my files, went and then deleted my backup file without my permission (didn&#039;t even ask me). Right now I am not too impressed with Microsoft&#039;s programming ability.  I did have a second incremental backup but so far, a number of things (not all the things) are lost.  After reading over the posts, I don&#039;t think this is just a Registry Cleaner issue but also an SP1 issue.  Ultimately, regardless of fingerpointing, even Microsoft should have safeguards to protect data - in ANY case - from being deleted.  This isn&#039;t just a registry issue - but a programming issue. In my view anyway it is.</description>
		<content:encoded><![CDATA[<p>Well this happened to me the weekend of August 9th. I didn&#8217;t know about this website or had even heard of this issue.  Like Kelly commented above, I thought the GB a mistake (I have seen Windows programs misreport file sizes before) and let Disk Cleaner do its evil thing.  I am still in the process of trying to recover my data because then Windows XP (my backups had been done in XP b/c my Vista machine was new), deciding that my backup was corrupted about a 1/4 way through restoring my files, went and then deleted my backup file without my permission (didn&#8217;t even ask me). Right now I am not too impressed with Microsoft&#8217;s programming ability.  I did have a second incremental backup but so far, a number of things (not all the things) are lost.  After reading over the posts, I don&#8217;t think this is just a Registry Cleaner issue but also an SP1 issue.  Ultimately, regardless of fingerpointing, even Microsoft should have safeguards to protect data &#8211; in ANY case &#8211; from being deleted.  This isn&#8217;t just a registry issue &#8211; but a programming issue. In my view anyway it is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fsr</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-2/#comment-2779</link>
		<dc:creator>fsr</dc:creator>
		<pubDate>Mon, 18 Aug 2008 16:08:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-2779</guid>
		<description>Two months ago, I had the same problem, I wiped my C:\ drive. DC reported 110 GB to be cleaned in a 150 GB drive with 15 GB in use; I suspected an error, but you never know. It was Eusing that deleted the values &quot;for me&quot;. I never used DC ever since, and right now it reports 160 GB to be cleaned. Your original post dates from 6 months ago, Microsoft should REALLY do something about this, why on earth do we have WINDOWS REGISTRY PROTECTION if Vista fails like this ?

Thanks for the fix !</description>
		<content:encoded><![CDATA[<p>Two months ago, I had the same problem, I wiped my C:\ drive. DC reported 110 GB to be cleaned in a 150 GB drive with 15 GB in use; I suspected an error, but you never know. It was Eusing that deleted the values &#8220;for me&#8221;. I never used DC ever since, and right now it reports 160 GB to be cleaned. Your original post dates from 6 months ago, Microsoft should REALLY do something about this, why on earth do we have WINDOWS REGISTRY PROTECTION if Vista fails like this ?</p>
<p>Thanks for the fix !</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dave</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-2/#comment-2751</link>
		<dc:creator>dave</dc:creator>
		<pubDate>Fri, 15 Aug 2008 03:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-2751</guid>
		<description>I had the same problem and it was caused by the &quot;EUSING FREE REGISTRY CLEANER&quot;.</description>
		<content:encoded><![CDATA[<p>I had the same problem and it was caused by the &#8220;EUSING FREE REGISTRY CLEANER&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lee Ray</title>
		<link>http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/comment-page-2/#comment-2748</link>
		<dc:creator>Lee Ray</dc:creator>
		<pubDate>Thu, 14 Aug 2008 20:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.winhelponline.com/blog/serious-disk-cleanup-problem-caused-by-broken-registration/#comment-2748</guid>
		<description>Well, I did my own experiment twice using RegistryFix before Windows Updates for Vista Business and then after Windows Updates.

Here&#039;s the trial after I lost the entire system after using Disk Cleanup.

1. Disconnected Internet Connection.

2. Reintalled the system with the Recovery Media.
3. After first boot to desktop, deactivated Windows Updates.
4. Installed RegistryFix v7 then ran and rebooted system.
5. Ran Disk Cleanup then rebooted system.

At this point, no problems.

6. Reconnected to Internet.
7. Downloaded all updates including SP1
8. Ran RegistryFix v7 rebooted computer.
9. Ran Disk Cleanup and crashed the system. No way to get back to the HD to repair it.

Conclusion: Windows Updates effect how all of our Registry Cleaners are working (so it appears) and when they clean the registry they are changin/removing values that allow Disk Cleanup to destroy the hard drive.  Holy Moly!!

Resolution. I am on my XP computer and will reinstall Vista Business on my other desktop. However, this time will no longer run Registry Fix and will be very careful to look at how much disk space will be cleaned up after ticking each item.

Vista is such a dissapointment.  MS should give a credit to everyone who still has a receipt of Vista from wherever they purchased it and issue credits so they can all buy Windows XP Pro. We should all just wait until a new Windows OS is released. In my opinion, Vista is &quot;belly-up in the water&quot; just like Windows ME was destined to become soon after it&#039;s release.

I love XP Pro. You can access everything you need to adjust the system. There are millions upon millions of excellent tips on the Internet that do not cause the average user (my client base) to jump through hoops to edit registries manually. It&#039;s almost a crime!

My two cents:  Lee</description>
		<content:encoded><![CDATA[<p>Well, I did my own experiment twice using RegistryFix before Windows Updates for Vista Business and then after Windows Updates.</p>
<p>Here&#8217;s the trial after I lost the entire system after using Disk Cleanup.</p>
<p>1. Disconnected Internet Connection.</p>
<p>2. Reintalled the system with the Recovery Media.<br />
3. After first boot to desktop, deactivated Windows Updates.<br />
4. Installed RegistryFix v7 then ran and rebooted system.<br />
5. Ran Disk Cleanup then rebooted system.</p>
<p>At this point, no problems.</p>
<p>6. Reconnected to Internet.<br />
7. Downloaded all updates including SP1<br />
8. Ran RegistryFix v7 rebooted computer.<br />
9. Ran Disk Cleanup and crashed the system. No way to get back to the HD to repair it.</p>
<p>Conclusion: Windows Updates effect how all of our Registry Cleaners are working (so it appears) and when they clean the registry they are changin/removing values that allow Disk Cleanup to destroy the hard drive.  Holy Moly!!</p>
<p>Resolution. I am on my XP computer and will reinstall Vista Business on my other desktop. However, this time will no longer run Registry Fix and will be very careful to look at how much disk space will be cleaned up after ticking each item.</p>
<p>Vista is such a dissapointment.  MS should give a credit to everyone who still has a receipt of Vista from wherever they purchased it and issue credits so they can all buy Windows XP Pro. We should all just wait until a new Windows OS is released. In my opinion, Vista is &#8220;belly-up in the water&#8221; just like Windows ME was destined to become soon after it&#8217;s release.</p>
<p>I love XP Pro. You can access everything you need to adjust the system. There are millions upon millions of excellent tips on the Internet that do not cause the average user (my client base) to jump through hoops to edit registries manually. It&#8217;s almost a crime!</p>
<p>My two cents:  Lee</p>
]]></content:encoded>
	</item>
</channel>
</rss>
