Another windows 7 800F0900 update error

Chertwell

Member
Joined
Aug 11, 2013
Posts
12
I have a windows 7 update problem. I get a message that there are updates ready to install. When I open the update box I get the red warning and error 800F0900. Have run sfc /scannow etc. I'd greatly appreciate any help.
 
Hi there Chertwell, and welcome to Sysnative!

I need you to do the following for me please. :)

Run the System Update Readiness Tool (SURT)


  1. Download the System Update Readiness Tool from Microsoft --> here <-- Please save the tool to a convenient location as it may be necessary to run it again.
  2. After the download has completed, double-click the file and wait while it initializes.
  3. Click Yes to begin installation. Please note it may take some time to complete and may appear to stall whilst installing. Don't worry, this is perfectly normal behaviour. Also note, whilst I say "installing", it's actually running the tool and can therefore be "installed" (run) repeatedly.


Export CBS folder


  1. Click the Start button :startorb: then click Computer.
  2. Double-click on the C: drive, under the Hard Disk Drives category, and then scroll down to, and double click on the Windows folder.
  3. Find and double click on the Logs folder.
  4. Right-click on the CBS folder, and select Copy.
  5. Go back to your Desktop, right-click on it, and select Paste. You should now see a copy of the CBS folder appear on your Desktop called CBS.
  6. Right-click on this new folder, and navigate through Send to, and select Compressed (zipped) folder.
  7. A new file, also called CBS (CBS.zip), but this time with a different icon, will be created.
  8. Attach this new file to your next post.


Stephen
 
Last edited:
Hello, and welcome to Sysnative :)

Actually, before following Stephen's advice, can you please follow these additional steps:

Download SFCFixVersion2.exe to your Desktop from here: https://www.sysnative.com/niemiro/apps/SFCFixVersion2.exe
Run it, then upload a copy of SFCFix.txt from your Desktop when it has finished (up to ~20 minutes)

Then please follow Stephen's advice and post the requested logfiles.

Thank you!

Richard
 
Hello, and welcome to Sysnative :)

Actually, before following Stephen's advice, can you please follow these additional steps:

Download SFCFixVersion2.exe to your Desktop from here: https://www.sysnative.com/niemiro/apps/SFCFixVersion2.exe
Run it, then upload a copy of SFCFix.txt from your Desktop when it has finished (up to ~20 minutes)

Then please follow Stephen's advice and post the requested logfiles.

Thank you!

Richard
 
Hello, and welcome to Sysnative :)

Actually, before following Stephen's advice, can you please follow these additional steps:

Download SFCFixVersion2.exe to your Desktop from here: https://www.sysnative.com/niemiro/apps/SFCFixVersion2.exe
Run it, then upload a copy of SFCFix.txt from your Desktop when it has finished (up to ~20 minutes)

Then please follow Stephen's advice and post the requested logfiles.

Thank you!

Richard

Richard,

I did not see the second message until I had run SURT. I ran SFCFixVersion2. I am including both versions of CBS marked CBS1 and CBS2 as well as the text file.
 

Attachments

Last edited:
Hello again :)

Thanks a lot for those logs. Can you please rerun SFCFixVersion2.exe, exactly as you did last time, and post a new SFCFix.txt (no need for SURT or CBS logs this time). I have made some server side changes which should result in some more files being fixed this time around. Tomorrow I or somebody else will post you a manual fix for the remainder.

Thank you for your patience :)

Richard
 
Hi Chertwell,

I have a few of the files that you need, so let's get these out of the way:

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

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

  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log

https://dl.dropboxusercontent.com/u/16537616/Fixes/SURT/Chertwell/Packages.zip

Tom
 
Hi Chertwell,

Here's the next bunch :)

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

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

  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log

https://dl.dropboxusercontent.com/u/16537616/Fixes/SURT/Chertwell/Packs.zip

Tom
 
Hi Chertwell,

Next batch :)

Windows Update Package Replacement

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Please download the attached file, Packs.zip and save this to your Desktop.
  2. Right-click on the file and select Extract All...
  3. Tick the box labelled Show extracted files when complete then click Extract
  4. A window will open showing two folders, Manifests and Packages
  5. Open the Manifests folder and copy the files into the following folder (if there are any files)

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

  6. Open the Packages folder and copy the files into the following folder (if there are any files)

    C:\Windows\Temp\CheckSur\Servicing\Packages

  7. Run the System Update Readiness Tool (SURT) again
  8. When the SURT finishes installing, copy (Ctrl + C) and paste (Ctrl + V) the contents of the SURT log into your next post please:

    C:\Windows\Logs\CBS\CheckSUR.persist.log


https://dl.dropboxusercontent.com/u/16537616/Fixes/SURT/Chertwell/Packs.zip

Tom
 
I managed to find almost all (all but 1 or 3 - the last 2 had some complexity to them and I can't remember whether I resolved it or not) of the payload files the other day. I've lost it in my filing system at moment, but I should be able to dig it out soon :p
 
I managed to find almost all (all but 1 or 3 - the last 2 had some complexity to them and I can't remember whether I resolved it or not) of the payload files the other day. I've lost it in my filing system at moment, but I should be able to dig it out soon :p

At least you have a filing system! My files are in complete disarray :p I deleted 47 CBS logs from my downloads folder yesterday, lol.
 
I managed to find almost all (all but 1 or 3 - the last 2 had some complexity to them and I can't remember whether I resolved it or not) of the payload files the other day. I've lost it in my filing system at moment, but I should be able to dig it out soon :p

At least you have a filing system! My files are in complete disarray :p I deleted 47 CBS logs from my downloads folder yesterday, lol.

If it was any good then files wouldn't have gone missing :p

TBH, I used to have quite a good filing system, with everything ordered by username then fix number. But that computer's been out of action for quite a bit, so now everything's scattered everywhere across two computers. I honestly don't even know whether it's on this computer or my laptop!
 
Richard,

I did as you instructed.

I made the mistake of looking in the wrong place to find the persist log. I ran SURT a second time so there may be some extra lines in the log file.

I wish I understood windows better.
I have a separate problem on a windows 8 machhine. It will not re-start - only shut-down then start. For that I tried:
DSM.exe /Online /Cleanup-image /Restorehealth
Is that command similar to what you are doing here?

regards

Chertwell
 

Attachments

@Richard

Here is the latest CheckSUR log summary, to save you from downloading it:

Code:
Summary:
Seconds executed: 1705
 Found 59 errors
  CSI Manifest All Zeros Total count: 1
  CSI Manifest and S256H Do Not Match Total count: 1
  CSI Manifest Failed Catalog Check Total count: 36
  CSI Located Replacement: Invalid (Catalog) Total count: 14
  CSI Payload File Missing Total count: 16
  CBS MUM Corrupt Total count: 1
  CBS Catalog Corrupt Total count: 4

Unavailable repair files:
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_fi-fi_a5e12d4f585626ef.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_ko-kr_d934f0aa12cc0996.manifest
	winsxs\manifests\amd64_vpcuxd.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_fi-fi_0207d273c1d568f7.manifest
	winsxs\manifests\amd64_vpcusb.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_ro-ro_63dad7573c96b3ac.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_pt-br_08970242cfc940bf.manifest
	winsxs\manifests\amd64_vpcuxd.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_pt-br_64bda767394882c7.manifest
	winsxs\manifests\amd64_vpcuxd.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_fr-fr_05a443c5bf8d8d2f.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_fr-fr_a97d9ea1560e4b27.manifest
	winsxs\manifests\x86_microsoft.msxml2_6bd6b9abf345378f_4.1.0.0_none_6c030d6fdc86522c.manifest
	winsxs\manifests\amd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7601.21693_none_89d95665bc9fff7c.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_pl-pl_0643179ed13facdb.manifest
	winsxs\manifests\amd64_microsoft-windows-winhstb.resources_31bf3856ad364e35_50.1.7600.16386_en-us_dfb0b646d64b001f.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_pt-pt_0978d1aecf38b09b.manifest
	winsxs\manifests\amd64_policy.9.0.microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.21022.8_none_1179c2b5d66019bc.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_he-il_ed9d46433c7d4c15.manifest
	winsxs\manifests\x86_microsoft.msxml2r_6bd6b9abf345378f_4.1.1.0_none_365945b9da656e4d.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_nb-no_c1c771deeaf13552.manifest
	winsxs\manifests\x86_microsoft-windows-capi2-certs_31bf3856ad364e35_6.1.7600.16784_none_c26418a8f57a0a47.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_ro-ro_4db397e6b59f7bf7.manifest
	winsxs\manifests\amd64_vpcuxd.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_tr-tr_f14abd53037e8d1b.manifest
	winsxs\manifests\amd64_wvpchbus.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_fr-fr_9fb7e526e3508029.manifest
	winsxs\manifests\x86_microsoft-windows-capi2-certs_31bf3856ad364e35_6.1.7600.20928_none_c332980a0e6364ee.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_nl-nl_c006bd1cec1d3f27.manifest
	winsxs\manifests\amd64_vpcuxd.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_pl-pl_6269bcc33abeeee3.manifest
	winsxs\manifests\amd64_vpcuxd.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_nb-no_1dee17035470775a.manifest
	winsxs\manifests\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.91_none_d6c3f1519bae0514.manifest
	winsxs\manifests\amd64_netfx-system.windows.forms_b03f5f7f11d50a3a_6.1.7601.17587_none_837857547b5afc4a.manifest
	winsxs\manifests\amd64_microsoft-windows-n..loyment-netfx30-wpf_31bf3856ad364e35_6.2.7600.16513_none_a6e9a94e56fc74eb.manifest
	winsxs\manifests\x86_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7600.16513_none_5ce27e967b21016b.manifest
	winsxs\manifests\amd64_netfx-dfshim_dll_31bf3856ad364e35_6.2.7600.16513_none_9ced6808153f4ebe.manifest
	winsxs\manifests\amd64_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7600.16513_none_b9011a1a337e72a1.manifest
	winsxs\manifests\amd64_netfx-mscorees_dll_31bf3856ad364e35_6.2.7600.16513_none_3dc6fbd94372d382.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_es-es_06c628a2633c34c5.manifest
	winsxs\manifests\amd64_wvpchbus.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_nl-nl_b64103a2795f7429.manifest
	winsxs\manifests\wow64_microsoft-windows-i..optional-deployment_31bf3856ad364e35_9.4.8112.16421_none_2c74e0c21785bccf.manifest
	winsxs\manifests\amd64_vpcusb.inf-languagepack_31bf3856ad364e35_7.1.7601.17514_pl-pl_1c6a570f5836e490.manifest
	winsxs\manifests\amd64_microsoft-windows-v..tyhandler.resources_31bf3856ad364e35_7.1.7601.17514_da-dk_60de60897260e2c1.manifest
	winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.20551_none_1ad1c342d54f56f8.manifest
	servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~da-DK~6.1.7601.17514.mum
	servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~sv-SE~6.1.7601.17514.mum
	servicing\packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~de-DE~7.1.7601.17514.mum
	servicing\packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~es-ES~7.1.7601.17514.mum
	servicing\packages\Package_for_KB2656373_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
	servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~da-DK~6.1.7601.17514.cat
	servicing\packages\Microsoft-Windows-VirtualPC-Package-wrapper~31bf3856ad364e35~amd64~sv-SE~6.1.7601.17514.cat
	servicing\packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~de-DE~7.1.7601.17514.cat
	servicing\packages\Microsoft-Windows-VirtualPC-Package~31bf3856ad364e35~amd64~es-ES~7.1.7601.17514.cat
	servicing\packages\Package_for_KB2656373_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat

Missing payload files:
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.17514_none_04709031736ac277\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.17514_none_0ec53a83a7cb8472\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.17725_none_0466c45b7371f20d\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.17725_none_0ebb6eada7d2b408\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.16915_none_0cdfe193aaa42c2b\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.21861_none_04c1204e8cb39c3f\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.20594_none_0d11f536c403a063\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.16484_none_0c932857aadde4a8\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.16385_none_023f7c69767c3edd\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.21861_none_0f15caa0c1145e3a\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.20594_none_02bd4ae48fa2de68\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.17035_none_02756f8b7653d554\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.21092_none_0d0fd45cc4059593\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.16484_none_023e7e05767d22ad\lsasrv.mof
	C:\Windows\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.16385_none_0c9426bbaadd00d8\lsasrv.mof
	C:\Windows\WinSxS\amd64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7600.16915_none_028b374176436a30\lsasrv.mof

I don't have any of these but I can get the payload files easily enough - I've been meaning to download a Windows 7 x64 RTM ISO for a while now.





Hi Chertwell,

Thanks for the log. Richard and I will get you up and running in no time!

It's no problem that you ran it twice, but thank you for letting me know :)

I wish I understood windows better.

If you ever have a question about Windows, computers or anything related then feel free to send me a PM and I'll do my best to explain!

I have a separate problem on a windows 8 machhine. It will not re-start - only shut-down then start. For that I tried:
DSM.exe /Online /Cleanup-image /Restorehealth
Is that command similar to what you are doing here?

I don't think DISM will be able to help you with that, but you're right in thinking that DISM command is similar to what the System Update Readiness Tool does. We'll stick to your problem here, but if you start a new thread in the Windows 8 forum then someone will help you with that:

Windows 8 | Windows RT - Sysnative Forums

Tom
 
Hi Chertwell,

I was going to hold off on a fix until I had all of the files, but we might as well break this down as I expect the others will be harder to source:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl + C) and Paste (Ctrl + V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

https://dl.dropboxusercontent.com/u/16537616/Fixes/SFCFix/Scripts/Chertwell/SFCFix.zip

Tom
 
I don't have any of these but I can get the payload files easily enough - I've been meaning to download a Windows 7 x64 RTM ISO for a while now.

@Tom - Do you want any files - I've got a Windows 7 Pro SP1 x64 ISO lying around somewhere if that's any use to you?
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top