My last post was on CheckSUR and I wanted to follow it up with how you can use the CheckSUR utility to fix corruption errors that CheckSUR might detect, but that cant be fixed with the utility.
Typically, the way that CheckSUR works is that it takes the information included with its payload, loads it locally to your machine into the \Windows\CheckSUR directory and then runs the actual executable on the system. As this executable runs, it detects discrepencies in the package store and corrects the errors that it carries a payload for. But, what do you do when you have a package manifest that shows up in the CheckSUR log but doesnt have the payload with it? If you were to call my team we'll typically try to walk you through getting the files from another server, taking ownership of the servicing directories and moving the files. But what if this is an isolated server? Worse, what if you only have one PC at home and you're having issues? Well, there is an easier way.
What you should do is identify the package(s) that CheckSUR was not able to fix, they're usually listed at the end of the log. From there, you can take that information and go the Microsoft Download site and pull down the KBXXXXXX.MSU that corresponds to the package that you're seeing failures on. Since you've already run CheckSUR to get to this point, you can copy that .MSU to the \Windows\CheckSUR\packages directory (NOTE: This directory does not exist by default and must be created) and then re-run CheckSUR which will take care of the rest. If you're still having issues afterwards, that just means that something else is going on with the system that is going to require more than CheckSUR can accomplish. Typically, this is true corruption and it may be unrecoverable.
As a side note, CheckSUR doesnt have a command line interface component, so you cant rerun it once its been downloaded and installed, you just need to re-run the downloaded MSU package.
Hope that helps.
Where do I find the keys and how do I export and where to.
You'd have to search within the Components branch to find them. Export them to a directory that you know of, it can be anything.
In Regedit I dont see the components branch could it be hidden, the only ones I can see are BCD00000000,Hardware,SAM,Security,Software and System.
I would like to cure myself your help so far has been well appreciated by a 70yr oldtecky GR8 Gdad still learning!!
LOL, no problem.
Try starting the Windows Modules Installer service. Open services.msc, find that service and right click on it. Choose Start and you should see the hive load.
Windows Modules Installer I presume is the trusted installer I dont have the right permissions to open and haven't time to spend altering, I am enjoying learning and finding my way around.
Off to Budapest to catch a cruise down the Danube to the Black Sea and her indoors won't let me take the
PC with me.
Thanks again catch up when I get back.
Captain, correct, Windows Modules Installer is a portion of the trusted installer.
Have fun on the trip. When you get back, I'd like to know what you mean by you dont have the right permissions? You should be able to modify that value unless you arent an administrator on your machine.
I have admin rights but the permissions are read execute and read. When I double click to run it doesn't run.
You should only need to right click on the service name and choose Start. You dont need to change any of the permissions.
Back from hols PC been at local shop to no avail,additional info in Register edit failed installation was 6.1.7600.16385(Win 7_rtm.090713_1255) REG-DWORD 0x00000003 (3). Traced to KB974431 update but update tells me its installed.
Can you walk me thru to Components branch in HKLM or Windows Module installer.
It's a little difficult to tell you how to walkthrought the component branch via a blog and without really knowing whats going on (aside from the comments here). You'll need to have control of the components branch in the registry, which is usually owned by Trusted Installer. You can manually give yourself full permissions to those keys using regedit and the permissions tab for that branch. From there you can export the keys you need to export to a safe location and then delete them and reattempt the operation.
I tried everything, was about to reformat, this worked!! thanks!!
Glad to hear that worked for you Jose. This functionality is now built into Windows 8, just so everyone knows :)
I had servicing issues last month and ran chksur it fixed the problem to resurface again this month on 2k8r2 machine. On both occasions there were different MUM files that were corrupt...
Is there a way I can know what is corrupting the MUM files?
Not really. Corruption is one of those things that just happens on PCs. I can tell you the most common cause from what I have personally seen is dirty shutdowns. Other causes I have seen, bad memory, bad segment on disk and malware.
Since it happened twice I was concerned... Can I setup Auditing on the winsxs folder? Would it be too heavy to log?
Only one MUM file got corrupted on each of the instances.. Is it co-incidence or something wrong ?