krit86lr

You repaired permissions with dial-a-fix, and it didn't work? You don't need to move your software. First, try this: Reboot in Safe Mode, logon as administrator, and run CCleaner. If that doesn't work. Try this: Have your installation CD ready, but don't insert it until you're prompted to do so. start > run > (type) sfc /scannow (there is a space after sfc)

The following instructions are 3 possible solutions in one. It will take about 10 minutes. You do need administrator access to perform these tasks. If your user account isn't the administrator then logon as administrator. Print these instructions for easy navigation. If you have any questions please ask before continuing. 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following key in the registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\3ware Storage Controller\Cache Control (If this key is not in your registry skip to step 5) 3. On the Edit menu, click Modify. 4. Type 0, and then press ENTER. 5. Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management 6. In the right pane, right-click the value SystemPages, and then click Modify. 7. In the Value data box, type the following value: 0xFFFFFFFF and then click OK 8. Locate the following registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters 9. In the right pane, right-click enablesecuritysignature, and then click Modify. 10. In the Value data: box, type 0, and then click OK. 11. Quit Registry Editor. 12. Restart the computer.

Some people intentionally remove that folder. (From another forum) "For example, consider the following scenario: 1. You apply a security update that installs a GDR version of File.dll with a version number of 5.2.3790.1000 and copies a hotfix version of File.dll with a version number of 5.2.3790.1000 to the %windir%\$hf_mig$ folder. 2. You apply a hotfix that includes a hotfix version of File.dll with a version number of 5.2.3790.0000. In this scenario the hotfix installation in step 2 installs the hotfix version of File.dll (version number 5.2.3790.1000) from the %windir%\$hf_mig$ folder instead of the hotfix version of File.dll (version number 5.2.3790.0000) from the hotfix package." (Franklin) "If I remember correctly $hf_mig$ folder is recreated when any new hotfixes are installed." (Franklin) "As I understand it, if you install an update, then later install another update that contains an earlier version of a file that's in the previous update, then you need it to migrate the later version of the file instead of installing the earlier version. Why this would ever come up I don't know, but it's Windows, it doesn't have to make sense." (Greenknight) I don't know how to confirm whether or not that folder gets re-installed with a hotfix. If someone knows how to confirm this, please hit us up. I'm also interested in whether or not the cache can be rebuilt if the folder does get re-created. I would like to add one more thing. Even though this folder may not be as serious as we think, it's still not a hotfix uninstaller folder. Therefore, it shouldn't be cleaned by the hotfix uninstaller option.

No clue. I saw it too, and was wondering the same thing. MrG hasn't posted any announcements.

hahaha I'm just giving you a hard time. But yes...I'm a "she".

You're probably right. If v1.1 functions were included in 2.0 then you wouldn't be prompted to install v1.1.

???his??? Who is "his"? It's "her"...

Never mind. It's useless. I used it, and didn't find it to be informative.

Do you have a 3ware Raid Controller?

Can you go into your event viewer, and get the Event ID and Error Source and the Message? Start > Control Panel > Administrative Tools > Event Viewer click on Applications - you will see errors and warnings (double click on them for information) click on System - you will see errors and warnings (double click on them for information) This will narrow down the source of your problem as well as the solution. Let me know if you have any questions.

I understand. If you want to fix the problem (problem being "delayed write failures") follow these instructions. If you don't want to fix the problem then please disregard this post. To work around this problem, turn off SMB signing on the server: 1. Start Registry Editor. 2. Locate, and then click the enablesecuritysignature value under the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters 3. On the Edit menu, click Modify. 4. In the Value data: box, type 0, and then click OK. 5. Quit Registry Editor. 6. Restart the computer. If these instructions are not clear, ask for clarification before continuing.

I'm running WinXP Pro SP2. That folder isn't anywhere on my computer. I'm going to fix that later on today.

I'm posting this in response to the $hf_mig$ thread going on in CCleaner Discussion. This tool may, or may not be useful in checking your system. I haven't tested it yet, but it can't hurt. "Microsoft has released a command-line tool named Qfecheck.exe that gives network administrators increased ability to track and verify installed Windows 2000 and Windows XP hotfixes. This tool provides the following benefits: ? This tool helps customers who thought they had properly installed an update, but had not, and are now experiencing a problem. Previously, it was somewhat difficult to identify which fixes were installed on a computer. This simple tool easily enumerates all of the installed fixes by Microsoft Knowledge Base article number. Customers can then confirm that they have installed the appropriate set of fixes before using a valuable support incident and potentially experiencing unplanned down time. ? Many companies identify a common set of fixes that are required for all servers in a given data center. To help ensure that Windows 2000 and Windows XP hotfixes are applied in a consistent manner across many servers, this tool allows you to create logs for each computer in your organization that show which fixes are installed. Once those logs are created, you can easily scan them for consistency. ? There are rare situations in which, because of a network problem, a problem with the update itself, or a subsequent update that improperly overwrites a previous fix, updates could be damaged or removed in error. This tool ensures that not only have the fixes been installed, but that they are current on the computer. ? Microsoft has noted a significant correlation between maintaining a consistent platform across organizations and the overall stability and uptime of those systems. Microsoft believes that using this tool to regularly audit computers is a best practice that will help customers achieve higher reliability on their computers." (MS Corp) FOR MORE INFORMATION Read Me Downloads for the tool are also available on this page.

Yes, most definitely. Especially since the $hf_mig$ folder isn't an uninstaller, but the cache folder. "...the package installer installs these software updates from the cache."

Nice catch! I just ran a search on my computer, and I don't have the $hf_mig$ folder - hmmmm. @MrG: Get back to us soon please.

I was just getting ready to PM you. Can you please post the Uninstaller folders that CCleaner cleans? CCleaner should not touch the $hf_mig$ folder. Read Me Read Me Read Me Thank you, K Does the CCleaner option "Hotfix Uninstallers" clean the $hf_mig$ folder?

"If the version installed is from the branch with fewer cumulative changes (in this example, it would be the GDR branch), the package installer caches the more cumulative versions (in this example, the QFE version) in %WINDIR%\$hf_mig$\KB######\. If a hotfix for one of those files is installed later, the package installer will ?migrate? the previously updated files to the QFE versions in order to maintain consistency. In addition, versions for a higher service pack level (if such versions exist) are also cached so that the software updates can be reapplied when the computer is updated to the next service pack. After the service pack installation, the package installer checks the cache directory at %WINDIR%\$hf_mig$\KB######\ to determine whether there are any software updates to be migrated to the new service pack level. If there are, the package installer installs these software updates from the cache. This method does not use the Xpsp1hfm.exe file that is used in dual-mode packages described previously. Instead, this functionality is built into the package installer itself." (MS Corp) My understanding is that "%WINDIR%\$hf_mig$\KB######" is the cache folder, not a hotfix uninstaller. CCleaner should not touch this folder. As for removing the uninstallers...sometimes hotfixes will mess up your computer, and you do need to uninstall them. It is a good idea to test your hotfixes before removing the uninstaller. I'm not clear why removing the uninstaller would break future updates. Microsoft tells you how to remove uninstallers safely. This is very interesting. Any feedback is appreciated.

Yeah, I know. I'll time it, and let you know. Thank you.

CCleaner cleans the hotfix "uninstallers". If you don't want to uninstall your hotfixes then you don't need the uninstallers.

Everthing came out clean. 0 errors, and what not. Did the Process Idle Tasks thing. Defragged, and I think that the startup was a little faster but I haven't timed it yet to see by how much (or if at all for that matter). Rriddgley.....are you going to split this thread? It's completely hijacked! Thanks.

I'm K! (You should know who I am with all of the PM's I have been sending you lately). And I don't know how to be a moderator, and I'm not qualified. I'm still a n00b.

My solution was for the "Delayed Write Failures". Are those fixed too?

What was the solution? Are you keeping the standard build?

I have found that trusted sources is very important. But that doesn't mean you're 100% safe from getting hit.

Uninstall CCleaner. Reboot. Then reinstall CCleaner. Choose to download either the Basic Build, or the Slim Build. The Basic Build supports multiple languages, and the Slim only supports english. Reboot after installing. Now run CCleaner, and fix Issues. If the problem continues follow these instructions. To work around this problem, turn off SMB signing on the server: 1. Start Registry Editor. 2. Locate, and then click the enablesecuritysignature value under the following key in the registry: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Lanmanserver\Parameters 3. On the Edit menu, click Modify. 4. In the Value data: box, type 0, and then click OK. 5. Quit Registry Editor. 6. Restart the computer. If these instructions are not clear, ask for clarification before continuing. I hope this works!