Windows update repeatedly fails; occasional BSOD Stop error 0x0093

[svldtech]

I'm new to posting on these boards but I'm going to do my best to follow all the guidelines. I ask your forgiveness in advance, just in case. I wasn't able to use the system specs tool because it says .NET won't install. I found that interesting since I believe .NET to be the root of my problems. I've been trying to run Windows Update for far longer that I like to recount. This computer had been on a shelf and my bosses want to bring it out for a new employee. It seems to work fine, except for it absolutely will not update and sometimes when I run Windows Update I get BSOD with Invalid Kernel and stop error 0x0093. I have tried everything I've found in the Seven Forums that applies to my version of Windows and errors. I have tried countless FixIts, but nothing has worked. I finally gave in and registered with y'all and I hope someone can help.

Thanks for your time.

 

[NoelDP]

Please follow the Windows Update Posting Instructions and post the requested data

 

[svldtech]

Hi, I tried to but the system specs utility won't work because of a .NET error. I read through everything and did my best to follow as closely as possible, minus the specs (obviously). However, I'll get whatever information you need and do it happily. I can go through and get the specs individually, if necessary. Other than that, I felt like I posted according to guidelines. I'm very sorry if I missed something. I'll read them again.

 

[svldtech]

I reran everything and this is what I have:

View attachment 280345

View attachment 280346

 

[mrdivi0910]

the problem same goes to me too, i wanted to update it but it kept failed to update

 

[NoelDP]

CheckSUR found the following errors...

Unavailable repair files:
 winsxs\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4137_none_508fc1d4bcbb3eca.manifest
 winsxs\manifests\x86_policy.9.0.microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_5d1777c2e857a23b.manifest
 winsxs\manifests\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_b81d038aaf540e86.manifest
 winsxs\manifests\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.21022.8_none_bdf22a22ab9e15d5.manifest
 winsxs\manifests\x86_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4137_none_f47d3254f657e518.manifest
 winsxs\manifests\x86_policy.9.0.microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_5926f98ceadc42c2.manifest

SFC found the following errors...

 Line 32665: 2013-08-07 14:32:06, Info                  CSI    0000035b [SR] Repairing 2 components
 Line 32666: 2013-08-07 14:32:06, Info                  CSI    0000035c [SR] Beginning Verify and Repair transaction
 Line 32667: 2013-08-07 14:32:06, Info                  CSI    0000035d [SR] Cannot verify component files for Microsoft.VC90.ATL, Version = 9.0.21022.8, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 32668: 2013-08-07 14:32:06, Info                  CSI    0000035e [SR] Cannot verify component files for Microsoft.VC90.MFC, Version = 9.0.21022.8, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32", TypeName neutral, PublicKey neutral, manifest is damaged (FALSE)
 Line 32673: 2013-08-07 14:32:06, Info                  CSI    00000360 [SR] Repair complete

These ones are effectively the same as the ones from CheckSUR, so can be ignored.

I'll post a fix protocol later (if I can!)

 

[svldtech]

You are a Godsend, Noel!! Thanks!

 

[svldtech]

Can anyone help me out? I know y'all are busy but I'm really ready to tackle this problem.
Thanks

 

[NoN]

Can anyone help me out? I know y'all are busy but I'm really ready to tackle this problem.
Thanks

Here a little help...

you can try searching for the meaning of the Windows Updates errors code through this page

 

[svldtech]

I went through the error codes and found two of the three, but I really don't know what either of them mean and how to proceed forward. Thanks for taking the time to post that though.

 

[NoN]

I went through the error codes and found two of the three, but I really don't know what either of them mean and how to proceed forward. Thanks for taking the time to post that though.

You can try to type the error code you found in the search bar of the Microsoft Community

 

[tom982]

I went through the error codes and found two of the three, but I really don't know what either of them mean and how to proceed forward. Thanks for taking the time to post that though.

You can try to type the error code you found in the search bar of the Microsoft Community

This isn't something that can be fixed from reading someone else's thread It requires a custom made fix.

 

[NoN]

you're welcome!

 

[NoN]

How do I reset Windows Update components?

Are you running Windows 7 SP1 as i see that manies updates (54)

See also:
How to get support for Windows Update problems

 

[NoelDP]

Can anyone help me out? I know y'all are busy but I'm really ready to tackle this problem.
Thanks

Sorry about the delay - my 3G dongle has gone AWOL and I can't post attachment until I can get to a decent network tomorrow. I'll get back to you then.

 

[tom982]

Can anyone help me out? I know y'all are busy but I'm really ready to tackle this problem.
Thanks

Sorry about the delay - my 3G dongle has gone AWOL and I can't post attachment until I can get to a decent network tomorrow. I'll get back to you then.

If it would help, I could sort out a fix for this?

 

[NoelDP]

I've got most of them - but the ones for 4137 are AWOL


I've uploaded a file - svtaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder svtaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[svldtech]

I zipped the entire folder again and attached it. I hope that is ok. I wanted to make sure you got everything. If you need me to attach the individual files I can do that too.

 

[svldtech]

Can anyone help me out? I know y'all are busy but I'm really ready to tackle this problem.
Thanks

Sorry about the delay - my 3G dongle has gone AWOL and I can't post attachment until I can get to a decent network tomorrow. I'll get back to you then.

If it would help, I could sort out a fix for this?

Hey Tom, I'm not sure if y'all have policies on more than one person providing a solution or not, but I'm willing to take all the help I can get. But I can understand how two people providing help on one problem could get a little hairy. I appreciate the offer, either way.

 

[NoelDP]

My, that's a fun list!

Unavailable repair files:
 winsxs\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4137_none_508fc1d4bcbb3eca.manifest
 winsxs\manifests\x86_policy.9.0.microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4137_none_f47d3254f657e518.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_8.0.7601.22389_none_cba0b2af1eb90ded.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_8.0.7601.22389_none_c14c085cea584bf2.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_8.0.7601.18210_none_33487de25b4a7c5d.manifest
 winsxs\manifests\x86_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_8.0.7601.18210_none_d729e25ea2ed0b27.manifest
 winsxs\manifests\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_8.0.7601.18210_none_09f4a4ebbe02c5da.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_8.0.7601.22389_none_b4c82bc5e6c9e525.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_8.0.7601.22389_none_6491b36788cf189b.manifest
 winsxs\manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7601.22389_none_ddc58b9555129047.manifest
 winsxs\manifests\wow64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7601.22389_none_e81a35e789735242.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.18210_none_c07fd95e1a296fd1.manifest
 winsxs\manifests\x86_microsoft-windows-ie-devtools_31bf3856ad364e35_8.0.7601.18210_none_5862a051151e2c7f.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_8.0.7601.18210_none_b4813bd4cd7b9db5.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_8.0.7601.22389_none_c0b04eeb412c89d1.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7601.22389_none_e35e539415caad97.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7601.22389_none_d909a941e169eb9c.manifest
 winsxs\manifests\amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.18210_none_2dbf46e0646f2ae1.manifest
 winsxs\manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.18210_none_d1a0ab5cac11b9ab.manifest
 winsxs\manifests\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.22389_none_64a82dcb7b1a460b.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_8.0.7601.22389_none_665a30608fae7e80.manifest
 winsxs\manifests\x86_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.18210_none_64613dda61cbfe9b.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18210_none_8c1f41a0afcebaaa.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.18210_none_9673ebf2e42f7ca5.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7601.18210_none_e31763a2fc7c6627.manifest
 winsxs\manifests\x86_microsoft-windows-ie-devtools_31bf3856ad364e35_8.0.7601.22389_none_58a990422e6c73ef.manifest
 winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.22389_none_1eed76ef906927ae.manifest
 winsxs\manifests\wow64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7601.18210_none_e7d345f670250ad2.manifest
 winsxs\manifests\amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.22389_none_2e0636d17dbd7251.manifest
 winsxs\manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_8.0.7601.22389_none_d1e79b4dc560011b.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_8.0.7601.22389_none_c0c6c94f3377b741.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_8.0.7601.18210_none_cb59c2be056ac67d.manifest
 winsxs\manifests\x86_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_8.0.7601.22389_none_0d2f54b84c607658.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22389_none_8c663191c91d021a.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_8.0.7601.22389_none_96badbe3fd7dc415.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-vgx_31bf3856ad364e35_8.0.7601.18210_none_6613406f76603710.manifest
 winsxs\manifests\amd64_microsoft-windows-ieframe_31bf3856ad364e35_8.0.7601.18210_none_dd7e9ba43bc448d7.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_8.0.7601.18210_none_6907004aeb6fa01e.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_8.0.7601.22389_none_694df03c04bde78e.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_8.0.7601.22389_none_338f6dd37498c3cd.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_8.0.7601.18210_none_acec77e01fd86abd.manifest
 winsxs\manifests\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.22389_none_7b0c127348c698e4.manifest
 winsxs\manifests\x86_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_8.0.7601.18210_none_0ce864c733122ee8.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-feeds-platform_31bf3856ad364e35_8.0.7601.18210_none_d8c2b950c81ba42c.manifest
 winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.18210_none_1ea686fe771ae03e.manifest
 winsxs\manifests\x86_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_8.0.7601.22389_none_d770d24fbc3b5297.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_8.0.7601.18210_none_090b1363d835dbf3.manifest
 winsxs\manifests\x86_microsoft-windows-ie-vgx_31bf3856ad364e35_8.0.7601.22389_none_0a3b94dcd7510d4a.manifest
 winsxs\manifests\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.18210_none_7ac522822f785174.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ieshims_31bf3856ad364e35_8.0.7601.18210_none_644ac3766f80d12b.manifest
 winsxs\manifests\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_8.0.7601.22389_none_ad3367d13926b22d.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_8.0.7601.22389_none_09520354f1842363.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_8.0.7601.18210_none_c105186bd10a0482.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_8.0.7601.18210_none_c0695efa27de4261.manifest

I'll try and sort them out tomorrow - but it's more likely to be Friday (Tom, you're welcome to join in if you can do it earlier!)