SFC Can't Fix Files

T

thenk

Member
Joined
Nov 23, 2016
Posts
6
Hey,

Boss's computer had a power outage, now half of windows doesn't work. SFC can't repair, and the SFXFix tells me something in the SxS is broken. I've attached the log output and the CBS file, can anyone help?

SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-11-23 14:02:55.127
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~nl-NL~0.0.0.0.
FIXED: Orphaned package PcmH (Microsoft-Windows-MediaPlayer-Package~31bf3856ad364e35~amd64~nl-NL~0.0.0.0) on package watchlist.


CORRUPT: C:\Windows\winsxs\x86_microsoft-windows-sxs_31bf3856ad364e35_6.1.7601.17514_none_b0540607b5e5d445\sxs.dll




SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 1
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 234
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 1
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2016-11-23 14:03:42.428
----------------------EOF-----------------------



View attachment CBS.zip
 
Just to update, I managed to manually fix the SFC corruption error - I got the WinSXS.dll from the Windows CD by extracting from the source folder and copied into the system with powershell. It's resolve the SFC errors, but most of the symptoms have not changed; the windows UI is still 90% broken, when you try to go to the resolution/personalization screen, it says: "Server execution failed". One thing did change though, I can now access the network/sharing center.

The SURT errors are still there. I can't run any installers to install anything as the Windows Installer service is broken - so the SURT tool won't work! Is there any way to manually install the SURT packages? As far as I can see, they contain most of what I'm missing which is causing the SURT errors.. just that I can't install them due to the broken installer service. Catch 22!

Just thought it was worth updating. The machine is still unusable, I tried to grok the SFCFix script file format which I think I understand, but I don't have any place to find most of the manifests that are required to be replaced (I did find a few in the windows DVD, but grepping the files was a pain), so I need some assistance here. Thanks in advance for any help
 
thenk said:
The SURT errors are still there. I can't run any installers to install anything as the Windows Installer service is broken - so the SURT tool won't work! Is there any way to manually install the SURT packages?
Click to expand...

basically the only thing stopping me is the inability of the Windows Installer service to install the manifests which it needs to run the Windows Installer service.

I don't have a copy of those manifests as I am not usually a Microsoft Windows guy. But I do understand how this all works, all I need is the files and I can probably make the SFCFix script myself, or at the very least automate the copying process via PowerShell.

Following the Microsoft advice about manual CheckSUR fixing, I came up with the a regex in order to list the files that have not been fixed (i.e. lines that start with (f) but are not succeeded by a (fix) line). I realized while doing the regex that, handily the file is provided in a tab seperated list, which makes the regexing a bit obsolete. You could also probably import it into Excel, create a table and filter the table, then export the CSV manually - I guess there's a lot of ways to manipulate the data. Anyway, I digress..

\(f\)\t(.*)\t(.*)\t(.*)\t(.*)\t\n(?!\(fi) was the regex I used, match $3 and $4 are the interesting strings. Can anyone point me to the place to obtain these files? Many don't seem to be in the Windows CD, but they are in the SUR packages. Manual extraction of each is proving a bit painful. Perhaps I could write a 7-zip script to extract the files from there?

Either way.. if I can't get some assistance from these boards within the day, I'm going to reinstall the computer. It's been over a week now since I started the fix, I'd love to complete the fix and restore the computer without having to reinstall... but if I can't get those files sorted, there's not much point. Anyone?



Code: 
SFCFIX Replace File: 806fc081f0b..d9fc8019693_31bf3856ad364e35_11.2.9600.18426_34d2df5c89b5a3b2 from appid (error: CSI Missing Identity (0x00000000))SFCFIX Replace File: 96bf54e9cb5..c7eb1c84a98_31bf3856ad364e35_11.2.9600.18426_e43b0ef1791c06b3 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: 7f74ad608e9..e5e6bca0509_31bf3856ad364e35_11.2.9600.18426_4a83bee29deb7071 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_044aad0bab1eb146 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: fb4753b4f18..deb76e9c51b_31bf3856ad364e35_11.2.9600.18426_2005a9df43e2af06 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: 89ff976e7e5..47051edf465_31bf3856ad364e35_11.2.9600.18426_a9f5c8391886b748 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: ebedac87124..f0c622c9733_31bf3856ad364e35_11.2.9600.18426_38f1a04270c9752a from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: f98dc7886ce..e71c274bfa2_31bf3856ad364e35_11.2.9600.18426_2b19f6a04f3565b8 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: 941dccf9597..b6306fbce4b_31bf3856ad364e35_11.2.9600.18426_3ad77b78950947c6 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: a8b14e56791..15b9d296b50_31bf3856ad364e35_11.2.9600.18426_9853c8ed2f2c4759 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: 601c6557789..3eb1735547a_31bf3856ad364e35_11.2.9600.18426_ae477b3f737634da from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: 485162bebff..448f1275899_31bf3856ad364e35_11.2.9600.18426_d591713f65d07071 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: ecd3500810a..e20e988cc8f_31bf3856ad364e35_11.2.9600.18426_d4f3a5b85e5fe486 from appid (error: CSI Missing Identity (0x00000000))
SFCFIX Replace File: amd64_ebedac8712468a48ef601f0c622c9733_31bf3856ad364e35_11.2.9600.18426_none_38f1a04270c9752a from c!ebedac87124..f0c622c9733_31bf3856ad364e35_11.2.9600.18426_38f1a04270c9752a (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_ecd3500810a49941468f5e20e988cc8f_31bf3856ad364e35_11.2.9600.18426_none_d4f3a5b85e5fe486 from c!ecd3500810a..e20e988cc8f_31bf3856ad364e35_11.2.9600.18426_d4f3a5b85e5fe486 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.2.9600.18426_none_29e4745faf46fb85 from c!806fc081f0b..d9fc8019693_31bf3856ad364e35_11.2.9600.18426_34d2df5c89b5a3b2 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_f98dc7886ce503577e536e71c274bfa2_31bf3856ad364e35_11.2.9600.18426_none_2b19f6a04f3565b8 from c!f98dc7886ce..e71c274bfa2_31bf3856ad364e35_11.2.9600.18426_2b19f6a04f3565b8 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_485162bebffaeda02179d448f1275899_31bf3856ad364e35_11.2.9600.18426_none_d591713f65d07071 from c!485162bebff..448f1275899_31bf3856ad364e35_11.2.9600.18426_d591713f65d07071 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-i..riptcollectionagent_31bf3856ad364e35_11.2.9600.18426_none_3bfff0f3f57af29d from c!601c6557789..3eb1735547a_31bf3856ad364e35_11.2.9600.18426_ae477b3f737634da (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.18426_none_ba94e7060c2bc51a from c!ecd3500810a..e20e988cc8f_31bf3856ad364e35_11.2.9600.18426_d4f3a5b85e5fe486 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_acd388d7e1d8689f from c!policy.9.0...ft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_acd388d7e1d8689f (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-mshtmldac_31bf3856ad364e35_11.2.9600.18426_none_5e764b8253ce53e4 from c!ecd3500810a..e20e988cc8f_31bf3856ad364e35_11.2.9600.18426_d4f3a5b85e5fe486 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_89ff976e7e53ce37665a647051edf465_31bf3856ad364e35_11.2.9600.18426_none_a9f5c8391886b748 from c!89ff976e7e5..47051edf465_31bf3856ad364e35_11.2.9600.18426_a9f5c8391886b748 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.18426_none_2e84dae840916a1f from c!7f74ad608e9..e5e6bca0509_31bf3856ad364e35_11.2.9600.18426_4a83bee29deb7071 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_806fc081f0ba068c02b74d9fc8019693_31bf3856ad364e35_11.2.9600.18426_none_34d2df5c89b5a3b2 from c!806fc081f0b..d9fc8019693_31bf3856ad364e35_11.2.9600.18426_34d2df5c89b5a3b2 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.2.9600.18426_none_728628c95f9e9517 from c!485162bebff..448f1275899_31bf3856ad364e35_11.2.9600.18426_d591713f65d07071 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_a8b14e567919844afa6ad15b9d296b50_31bf3856ad364e35_11.2.9600.18426_none_9853c8ed2f2c4759 from c!a8b14e56791..15b9d296b50_31bf3856ad364e35_11.2.9600.18426_9853c8ed2f2c4759 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: wow64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.18426_none_1c0deec5636d3b76 from c!a8b14e56791..15b9d296b50_31bf3856ad364e35_11.2.9600.18426_9853c8ed2f2c4759 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-jsprofilerui_31bf3856ad364e35_11.2.9600.18426_none_d5563e11e340f03f from c!941dccf9597..b6306fbce4b_31bf3856ad364e35_11.2.9600.18426_3ad77b78950947c6 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_11.2.9600.18426_none_973a5c45ebd7e405 from c!89ff976e7e5..47051edf465_31bf3856ad364e35_11.2.9600.18426_a9f5c8391886b748 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-adminkitbranding_31bf3856ad364e35_11.2.9600.18426_none_fa89155fb42dba29 from c!f98dc7886ce..e71c274bfa2_31bf3856ad364e35_11.2.9600.18426_2b19f6a04f3565b8 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-jsprofilerui_31bf3856ad364e35_11.2.9600.18426_none_7937a28e2ae37f09 from c!941dccf9597..b6306fbce4b_31bf3856ad364e35_11.2.9600.18426_3ad77b78950947c6 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-lowreg_31bf3856ad364e35_11.2.9600.18426_none_8aa3766bf8eedb55 from c!7f74ad608e9..e5e6bca0509_31bf3856ad364e35_11.2.9600.18426_4a83bee29deb7071 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_601c6557789f088e351343eb1735547a_31bf3856ad364e35_11.2.9600.18426_none_ae477b3f737634da from c!601c6557789..3eb1735547a_31bf3856ad364e35_11.2.9600.18426_ae477b3f737634da (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146 from c!microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_044aad0bab1eb146 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-antiphishfilter_31bf3856ad364e35_11.2.9600.18426_none_dde95ac180cc84eb from c!ebedac87124..f0c622c9733_31bf3856ad364e35_11.2.9600.18426_38f1a04270c9752a (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_96bf54e9cb5c954755e22c7eb1c84a98_31bf3856ad364e35_11.2.9600.18426_none_e43b0ef1791c06b3 from c!96bf54e9cb5..c7eb1c84a98_31bf3856ad364e35_11.2.9600.18426_e43b0ef1791c06b3 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_7f74ad608e9a44e36ebfde5e6bca0509_31bf3856ad364e35_11.2.9600.18426_none_4a83bee29deb7071 from c!7f74ad608e9..e5e6bca0509_31bf3856ad364e35_11.2.9600.18426_4a83bee29deb7071 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-i..riptcollectionagent_31bf3856ad364e35_11.2.9600.18426_none_981e8c77add863d3 from c!601c6557789..3eb1735547a_31bf3856ad364e35_11.2.9600.18426_ae477b3f737634da (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_11.2.9600.18426_none_11b944732f0c797b from c!a8b14e56791..15b9d296b50_31bf3856ad364e35_11.2.9600.18426_9853c8ed2f2c4759 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-ratings_31bf3856ad364e35_11.2.9600.18426_none_a9e982be71c93379 from c!96bf54e9cb5..c7eb1c84a98_31bf3856ad364e35_11.2.9600.18426_e43b0ef1791c06b3 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_11.2.9600.18426_none_16678d45a74123e1 from c!485162bebff..448f1275899_31bf3856ad364e35_11.2.9600.18426_d591713f65d07071 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_fb4753b4f18fe43817cd5deb76e9c51b_31bf3856ad364e35_11.2.9600.18426_none_2005a9df43e2af06 from c!fb4753b4f18..deb76e9c51b_31bf3856ad364e35_11.2.9600.18426_2005a9df43e2af06 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-ratings_31bf3856ad364e35_11.2.9600.18426_none_4dcae73ab96bc243 from c!96bf54e9cb5..c7eb1c84a98_31bf3856ad364e35_11.2.9600.18426_e43b0ef1791c06b3 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-antiphishfilter_31bf3856ad364e35_11.2.9600.18426_none_81cabf3dc86f13b5 from c!ebedac87124..f0c622c9733_31bf3856ad364e35_11.2.9600.18426_38f1a04270c9752a (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: wow64_microsoft-windows-ie-objectcontrolviewer_31bf3856ad364e35_11.2.9600.18426_none_23d256e85d91d05e from c!fb4753b4f18..deb76e9c51b_31bf3856ad364e35_11.2.9600.18426_2005a9df43e2af06 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_11.2.9600.18426_none_cdc5d8dbf6e98a4f from c!806fc081f0b..d9fc8019693_31bf3856ad364e35_11.2.9600.18426_34d2df5c89b5a3b2 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_941dccf9597bcf84f5e96b6306fbce4b_31bf3856ad364e35_11.2.9600.18426_none_3ad77b78950947c6 from c!941dccf9597..b6306fbce4b_31bf3856ad364e35_11.2.9600.18426_3ad77b78950947c6 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_11.2.9600.18426_none_3b1bc0c2337a72cf from c!89ff976e7e5..47051edf465_31bf3856ad364e35_11.2.9600.18426_a9f5c8391886b748 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-adminkitbranding_31bf3856ad364e35_11.2.9600.18426_none_56a7b0e36c8b2b5f from c!f98dc7886ce..e71c274bfa2_31bf3856ad364e35_11.2.9600.18426_2b19f6a04f3565b8 (error: CSI C Mark Deployment Not Marked (0x00000000))
SFCFIX Replace File: amd64_microsoft-windows-ie-objectcontrolviewer_31bf3856ad364e35_11.2.9600.18426_none_197dac9629310e63 from c!fb4753b4f18..deb76e9c51b_31bf3856ad364e35_11.2.9600.18426_2005a9df43e2af06 (error: CSI C Mark Deployment Not Marked (0x00000000))
 
Hi there thenk,

Would you mind running SURT again and attaching the log (C:\Windows\Logs\CBS\CheckSUR.log)?
I'd like to see what files and registry entries still need work after your fixes.
 
zcomputerwiz said:
Hi there thenk,

Would you mind running SURT again and attaching the log (C:\Windows\Logs\CBS\CheckSUR.log)?
I'd like to see what files and registry entries still need work after your fixes.
Click to expand...

Hi mate,


Thanks for the reply.


As far as I know, I can't run CheckSURT again. When I attempt to run the MSU, it opens the dialog but then comes up with an error and says it can't start.


I haven't written down the error record, but the CheckSUR in the file there is the latest I have.. unless there's some other way to run CheckSURT?
 
Ok, let's try resetting the Windows Update Components.

Run Windows Repairs
  1. Download Windows Repair (All-in-One) Portable to your desktop.
  2. Once the file is downloaded, right-click on the file on your desktop and choose Extract All...
    Extract.JPG
  3. Keep the defaults and click the Extract button.
  4. A folder named tweaking.com_windows_repair_aio will be extracted to the desktop. Once the extraction is complete the folder will open.
  5. Inside this folder, there is a folder named Tweaking.com - Windows Repair. Open this folder as well.
    Capture.JPG

  6. Double-click on Repair_Windows.exe to open. Note: Please make sure all of your programs are closed and anything you were working on is saved as we will be rebooting.
  7. When the program opens, click the Reboot to Safe Mode button at the bottom of the screen. Answer Yes to allow.
  8. Once rebooted into Safe Mode, open the program again. When the program opens, click the Repairs tab and click the Open Repairs button.
  9. A backup of your registry will be made. After a few moments you will have many options from which you can choose.
  10. Please click the Unselect All button and then click to enable only the following ones:

    17 - Repair Windows Updates

  11. Ensure the Restart check box is selected and click the Start Repairs button in the lower right of the screen. This may take some time to run so be patient.
    StartRepairsWithReboot.JPG
  12. Once the fixes are complete you will be prompted to restart your machine. Answer Yes.

Once the computer has restarted, try to run SURT again and attach C:\Windows\Logs\CBS\CheckSUR.log. If it fails, please note the error message and code (if any) and include it with your reply.
 
Hi computerwiz,

Thanks for the reply. Unfortunately it was a bit late. I managed to figure out how to run CheckSUR when the MSI doesn't work, so I thought I'd post that here, it might help someone. I did run the Tweaking.com Windows Repair tool in the manner you describe here, but it did not change anything, the issue was still there.

Anyway, to answer my question in my last post: in order to run that CheckSUR if the Windows Installer service is broken is that you expand the KBxxxxxx-x86-x64.MSI installer and run the checksur.exe that is expanded with it in a console. It then goes through and does it's thing, writes to the CheckSUR.log. You can then extract your matching mum/manifest/cat files into the CheckSUR directory, run CheckSUR again and it will replace any corrupted files as per the MS documentation and give you another CheckSUR.log

Also, if you want to, and I think an easier way than running CheckSUR and messing with the mum/manifest/cat files, you can actually use the DISM tool to add standalone cab packages to the windows image. In my case, the Windows Installer service was broken, DISM couldn't seem to deal with MSI files.

Method for this: Download the KBxxxx.MSU files that match your CheckSUR list; put them all in one folder.
Open a command prompt, go to the folder and run:

expand -F:*.cab *.MSU cabs

Then run the DISM tool to add the extracted cabs into the windows image:

DISM /Online /Add-Package /PackagePath:"cabs"

The tool will go through one by one and install the CAB files that were in the MSU packages.


After running CheckSUR again, most of the errors were gone, there were a couple of manifests that didn't have KB names in them - I tracked them down from other PCs in the office, but strangely, none of the PCs or windows image files I could find contained one of the missing manifests. I think the update in question was superceded by another update which has a version number which is only 1 higher than the manifest that was missing on this PC - and all of the PCs I could find had that 'other' manifest on it. Anyway, I digress...

Doing that with the DISM tool (and then installing the missing manifests with the CheckSUR tool), I was able to replace all except 6 of the SUR errors. One error that remained was a manifest file for visual studio 2008 VC90, which is a very old KB that was not available anymore. I found a post in this forum where the helper had attached all of those manifest files to the post, but the attachment was over-written with some other attachment so I was not able to get the manifest files for that update, or the KB file from anywhere (I could find the 32 bit one, but not the 64 bit), and I was under pressure to get the PC fixed ASAP.

So, I just put in a Windows 7 usb and hit the "upgrade" button. 30 minutes later, Windows is working perfectly again. Suffice to say, I could have done that weeks ago, but I wanted to attempt to fix the corruption myself. I came very close, and if I had access to the manifest files I needed, then I believe I would have been able to fix it, as I got the error count to just 6, and all of the missing files were part of that visual studio security update. I believe the component was an absolute essential part of windows (i.e. visual c 9.0) and that's why even though there was almost no errors with system file corruption, no missing packages and only 6 issues with the registry, pretty much everything was broken.

This has been a great learning experience, next time I experience some kind of corruption on a PC, I'll be very well placed to fix it, provided I know where to get the files.

Is there an Microsoft site somewhere, maybe on a free MSDN account, where one can track down all these manifest files, or are the files that the sysnative helpers attach just kept in some kind of large store where only the approved people have access? It would be great if I can find an easier way to get the required files :)
 
Good job with what you did, that was some excellent work. The symptoms you describe does sound like a Visual C Runtime or .Net framework problem.

There are ways to trace missing manifests to updates in the registry if the manifest was originally packaged in a Windows Update. Sometimes they are part of something else, like a Visual C Runtime package (which can be a pain to source for some versions, as you discovered).

In the cases where the manifest is from a superseded version of some update that is no longer available from MS, we are stuck if one of our machines didn't already have that version installed at some point.

I usually source my files directly from updates or a virtual machine, so unfortunately I don't have a quicker way to find the missing files - especially in the case of the Visual C Runtime. Sometimes it helps to find out what other software was installed at the same time, as the runtime installer may have been packaged with it.
 
You must log in or register to reply here.
Back
Top