Jump to content


What is wrong with the Hotfix Uninstaller?


3 replies to this topic

#1 OFFLINE   slowday444

    Power Member

  • Members
  • PipPipPipPip
  • 807 posts

Posted 22 March 2006 - 05:30 AM

As far as I know, I haven't had any problems.

#2 OFFLINE   krit86lr

    Power Member

  • Members
  • PipPipPipPip
  • 1,958 posts
  • Gender:Female
  • Location:Missouri, USA

Posted 22 March 2006 - 06:30 AM

View Postslowday444, on Mar 21 2006, 11:30 PM, said:

As far as I know, I haven't had any problems.
Hi slowday444. The "hotfix uninstaller" is deleting the $hf_mig$ folder. This folder isn't supposed to be deleted. MrG fixed it for CCleaner v1.28 which will be released in a few days.

If you do a forum search for $hf_mig$ you will find all of the information about it.

There are 2 solutions that have been established thus far, to repair the folder.
1. A system restore point that is dated prior to using the "hotfix uninstaller" in any versions of 1.27 (even the betas).
2. Or, a repair installation.

Example of something that could go wrong, and you won't realize it. Let's say that you have a hotfix from 1 year ago, and MS releases an updated hotfix for the old hotfix. Your auto updates will not install the updated hotfix on your computer because the old hotfix isn't cached in your $hf_mig$ folder. Therefore, they don't think that you need the updated hotfix, but you really do.


Hope that this helps. :)

#3 OFFLINE   hazelnut

    try to stay calm

  • Moderators
  • 9,458 posts
  • Gender:Female
  • Location:Huddersfield uk

Posted 22 March 2006 - 07:11 AM

If I could just add that the $hf_mig$ folder (should you have deleted it ) will be restored with the next MS update but will only contain the new info.
That is why my $hf_mig$ folder is unfortunately now only 4.1mb's instead of the hundreds of mb's it should be.
CCLEANER, RECUVA, DEFRAGGLER AND SPECCY DOCUMENTATION CAN BE FOUND HERE

http://www.piriform.com/docs

#4 OFFLINE   Andavari

    Captain Spectacular

  • Moderators
  • 13,327 posts
  • Gender:Male
  • Location:Shadow Moses

Posted 22 March 2006 - 03:41 PM

Plain and simple it's broken. In reality it should have been thoroughly tested before the release of 1.27, but oh well.
Complexity of incoherent design.