Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Cannot install SP1 on Windows 7 0x800F0900 - bad manifests in SUR log

15 Dec 2014   #1
PS98101

W7 Ultimate x64
 
 
Cannot install SP1 on Windows 7 0x800F0900 - bad manifests in SUR log

This seems to be the place to go with these. This is a Windows 7 Ultimate x64 machine which won't take SP1 -- error 0x800F0900. SFC returns no errors. CheckSUR.log is attached.

Thanks.


My System SpecsSystem Spec
.
16 Dec 2014   #2
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

You have a fair number of errors there - I'll post a fix protocol later for most of them, and we'll have to work on the others after that.
My System SpecsSystem Spec
16 Dec 2014   #3
PS98101

W7 Ultimate x64
 
 

Thanks.
My System SpecsSystem Spec
.

16 Dec 2014   #4
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

For easy-access, these are the errors I'm trying to fix, currently...
Code:
Unavailable repair files:
 winsxs\manifests\amd64_system.web_b03f5f7f11d50a3a_6.1.7600.16677_none_8400955abe54c7be.manifest
 winsxs\manifests\msil_system.web.extensions_31bf3856ad364e35_6.1.7600.20804_none_3bed8de8183e838f.manifest
 winsxs\manifests\amd64_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7600.20804_none_aca3c610f96a2224.manifest
 winsxs\manifests\amd64_netfx35linq-system.web.extensions_31bf3856ad364e35_6.1.7600.20804_none_2b4dbeaa1db905be.manifest
 winsxs\manifests\x86_netfx35linq-system.web.extensions_31bf3856ad364e35_6.1.7600.20804_none_cf2f2326655b9488.manifest
 winsxs\manifests\amd64_system.web_b03f5f7f11d50a3a_6.1.7600.20804_none_6d2c30c8d80229d1.manifest
 winsxs\manifests\amd64_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7600.16677_none_c3782aa2dfbcc011.manifest
 winsxs\manifests\amd64_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7600.20804_none_3aed5b964dc79b9e.manifest
 winsxs\manifests\x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7600.20804_none_f450fce80de64b2a.manifest
 winsxs\manifests\msil_system.web.extensions_31bf3856ad364e35_6.1.7600.16677_none_3b1b40a0ff56f63a.manifest
 winsxs\manifests\msil_system.web.resources_b03f5f7f11d50a3a_6.1.7600.16677_en-us_5405b5c155beaf38.manifest
 winsxs\manifests\x86_system.web_b03f5f7f11d50a3a_6.1.7600.20804_none_b4d9679fec7e52d7.manifest
 winsxs\manifests\x86_system.web_b03f5f7f11d50a3a_6.1.7600.16677_none_cbadcc31d2d0f0c4.manifest
 winsxs\manifests\msil_system.web.resources_b03f5f7f11d50a3a_6.1.7600.20804_en-us_3d31512f6f6c114b.manifest
 winsxs\manifests\x86_netfx35linq-system.web.extensions_31bf3856ad364e35_6.1.7600.16677_none_ce5cd5df4c740733.manifest
 winsxs\manifests\x86_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7600.20804_none_829a926d6243c4a4.manifest
 winsxs\manifests\amd64_netfx35linq-system.web.extensions_31bf3856ad364e35_6.1.7600.16677_none_2a7b716304d17869.manifest
 winsxs\manifests\amd64_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7600.16677_none_51c1c028341a398b.manifest
 winsxs\manifests\x86_netfx-web_engine_dll_b03f5f7f11d50a3a_6.1.7600.16677_none_0b256179f438e917.manifest
 winsxs\manifests\x86_netfx-aspnet_wp_exe_b03f5f7f11d50a3a_6.1.7600.16677_none_996ef6ff48966291.manifest
 servicing\packages\Package_1_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_2_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_3_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_4_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_7_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_7_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2416471_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2416471_RTM~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.mum
 servicing\packages\Package_1_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_1_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_2_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_3_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_4_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_5_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_7_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_7_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2416471_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2416471_RTM~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
 servicing\packages\Package_for_KB2416471~31bf3856ad364e35~amd64~~6.1.1.0.cat
My System SpecsSystem Spec
16 Dec 2014   #5
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

I've uploaded a file - ps9aa.zip - to my OneDrive at Noel's OneDrive
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 ps9aa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the 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.
My System SpecsSystem Spec
16 Dec 2014   #6
PS98101

W7 Ultimate x64
 
 

The logs look better now -- all errors fixed (both log files are identical and attached.) SP1 and all subsequent updates installed without a hitch now. I think this has been resolved. Thanks! I wonder what sequence of events causes this to happen to so many people.
My System SpecsSystem Spec
17 Dec 2014   #7
NoelDP

Microsoft Community Contributor Award Recipient

Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
 
 

In your case, this appears to have been caused by one failed update - windows was protecting itself from further damage by refusing to update further, which would only have caused more problems.
There are any number of reasons for a failed update like this - common ones include...
Registry 'Cleaners'
File cleanup tools running at shutdown
power failure during update reboots
etc., etc.
My System SpecsSystem Spec
17 Dec 2014   #8
PS98101

W7 Ultimate x64
 
 

Thanks for the insight. It's rather sad that Microsoft implements this "safeguard" with no apparent mechanism to resolve it. If it weren't for this forum, would we all have to call some guy in India to remote into the computer and duplicate what you did? Would an in-place upgrade reliably resolve this? Anyway, thanks very much for helping me with this.
My System SpecsSystem Spec
Reply

 Cannot install SP1 on Windows 7 0x800F0900 - bad manifests in SUR log




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Win7 Ult sp1 install error, missing manifests
Hello, I've pasted the checkSUR log info from my Dell XPS420 after recently trying to update my Win 7 Ult x64 install to SP1. All other updates install fine, but SP1 does not. I get error 80073712. The log seems to indicate that there are 4 manifest files that are either or corrupt. I've...
Installation & Setup
Windows Update Manifests - Manually Trace Through Registry
How to Trace what Windows Update a Manifest File Originated From This is an advanced method for solving Windows Update issues (outlined in CheckSUR logs). I would highly advise against doing this unless you're sure about what to do! In CheckSUR logs, you will sometimes see errors about...
Tutorials
Windows 7 Home Premium 32bit SP1 Update is failing, error 0x800f0900
Ever since it came out, my computer has been unable to install SP1. It has never really been an issue before, but I now have a program that won't install because it requires SP1. The error message I am getting is 0x800f0900 I have run the System Update Readiness Tool...
Windows Updates & Activation
Windows 7 Update/Repair error 0x80070246, missing manifests+mum files
Trying to repair a Windows 7 64bit Dell Laptop. Owner had bad RAM running back from February causing multiple BSOD and unstable behavior - but they kept using it. Got new RAM, it now tests rock solid with both ms ram tests and memtest. No more BSOD. Now trying to repair corrupted files. ...
Windows Updates & Activation
Windows update failing due to missing timezone manifests
Windows update errors are Code 80073712, 800B0100 and 8007065E There are a number of manifests missing that the repair disk/original disk isn't fixing I am running Windows 7 x64 Ultimate (upgrade online after originally installing Pro) help fixing this much appreciated....
Windows Updates & Activation
SFC - Broken Manifests, what now?
Win7 Pro x64 Alright, so I ran the SFC tool because things are bit wonky, and I got: 2011-06-01 20:34:07, Info CSI 0000003a Cannot verify component files for Microsoft-Windows-CAPI2-certs, Version = 6.1.7601.17582, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral,...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 11:59.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App