[SOLVED] Win10 22H2 Update Failure

J

jackiegibson

Member
Joined
Feb 23, 2023
Posts
19
This is a fresh install (albeit from an old image) of Win10 and am unable to get 22H2 to update.

sfc /scannow errors that the Windows Resource Protection could not perform the requested operation.

DISM /online /cleanup-image /restorehealth fails at 3.8% and says the component store has been corrupted.
 

Attachments

Hi and welcome to Sysnative,

Step 1. Replace Components Hive Manually

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 COMPONENTS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the COMPONENTS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config


Step 2. Reboot the system and run
61f7aba7309a1-ComponentsScanner_Icon.png
ComponentsScanner again.
  • Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
  • Follow the on-screen instructions.
  • Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
  • Post the logfile ComponentsScanner.txt as attachment into your next reply.
 

Attachments

Great, please run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 
Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Rich (BB code): 
2023-02-25 09:02:27, Info                  CSI    00000007 Hashes for file member [l:17]'M1033Zira.TBT.NUS' do not match.
 Expected: {l:32 ml:33 b:c553acd12df4776bfc8443838d2f144257a3fe3d967af51f9ff4ebc173c098a5}.
 Actual: {l:32 b:6ba348ecea332e780ad63b2cbd42c3aa2c5321c137e0677924fe8b5ee93298b7}.
2023-02-25 09:02:27, Info                  CSI    00000008 Warning: Unable to repair payload file ([l:17]'M1033Zira.TBT.NUS') for component ([l:98 ml:140]'amd64_microsoft-windows-t..peech-en-us-onecore_31bf3856ad364e35_10.0.19041.1_none_b1edff6d283a640a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Rich (BB code): 
2023-02-25 09:35:36, Info                  CSI    00000007 Hashes for file member [l:21]'System.Deployment.dll' do not match.
 Expected: {l:32 ml:33 b:6394ad2ac77880208204a6848284b57015996128cdd201b9bebcbf6a1625bdea}.
 Actual: {l:32 b:0fb94496ef94006f4deacbdb59d6fb9be861724d188f8d784ad1a98a2c169228}.
2023-02-25 09:35:36, Info                  CSI    00000008 Warning: Unable to repair payload file ([l:21]'System.Deployment.dll') for component ([l:76 ml:140]'amd64_system.deployment_b03f5f7f11d50a3a_4.0.15805.245_none_b2d16576d71c478c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

There is no need to attach the dism.log, in cases like this it is not necessary to provide.

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

Done and DISM completed successfully, but still experiencing errors with Windows Update. It tried to update KB5022834 2023-02 Cumulative Update for 21H2 and errors 80073712. So I tried to use the Media Creation Tool to upgrade to 22H2 and it downloaded successfully but did not verify. I received error 0x80070570 0xb0003.

I ran DISM /checkhealth and no corruption was detected.

I ram DISM /scanhealth and no corruption was detected.
 

Attachments

Hi,

Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards, reboot the system and attempt to update. If it fails attach a new copy of the CBS log(s).
 

Attachments

Thanks. Files attached. Update failed. I truly appreciate your help! We are traveling for the day so will be unresponsive until late and will follow up tomorrow with any additional steps.
 

Attachments

Rich (BB code): 
2023-02-26 09:33:35, Info                  CSI    0000026f Warning: Unable to repair manifest for component ([l:100 ml:140]'amd64_microsoft-windows-c..ed-deployment041120_31bf3856ad364e35_10.0.19041.844_none_3846dd2f0a5001a0') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-02-26 09:33:49, Error                 CSI    00000270@2023/2/26:15:33:49.795 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]

Hi,

Step 1.
Warning: This fix was written specifically for this system. Do not run this fix on another system.
  • Save any work you have open, and close all programs.
  • Download the attachment SFCFix.zip and save it to your desktop.
  • Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt.
  • Post the logfile (SFCFix.txt) as attachment in your next reply.


Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.
Code: 
DISM /online /cleanup-image /RestoreHealth
 

Attachments

You must log in or register to reply here.

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

Back
Top