[SOLVED] Error Install Update KB5034127 Windows server 2019

Please do the following, but this script will also (force) a reboot.

Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Warning: This script was written specifically for this system. Do not run this script on another system.

  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.

Afterwards attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

Rich (BB code):
2024-02-14 19:19:33, Error                 CSI    00000034@2024/2/14:22:19:33.933 (F) onecore\base\wcp\componentstore\versionedindex.cpp(3604): Store corruption detected in function ComponentStore::CRawStoreLayout::CheckFamilyIndexForDeadWinnerComponent expression: (null)
  MissingWinningComponentKey on resource 'amd64_microsoft-windows-s..cingstack-onecoreds_31bf3856ad364e35_10.0.17763.5084_none_020d9fdcf35c0f43'[gle=0x80004005]

Hi,

Please attach a new copy of the COMPONENTS hive.

Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Step 1. Start the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.
  • Download the attachment fixlist.txt and save it to your desktop.
  • Right-click on FRST.exe and select "Run as administrator".
  • Press the Fix button.
  • If for some reason the tool needs a restart, please make sure you let the system restart normally.
  • When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  • Post the logfile Fixlog.txt as attachment in your next reply.


Step 2. Follow these instructions to install an update with DISM.
  • Open the Start menu of Windows and type CMD.
  • When you see Command Prompt on the list, select the option Run as administrator.
  • Copy and paste the following command into it, and press enter. (Leave the CMD window open!)
Code:
MD C:\WUTemp
  • Now, download the following update (KB5032196) to: C:\WUTemp - Or copy this file from the download directory to C:\WUTemp. (Important!)
    Downloadlink: KB5032196
  • Copy and paste the following commands one at a time into the command prompt and press enter after each.
Code:
CD C:\WUTemp
EXPAND.exe windows10.0-kb5032196-x64_07be38ad94320c193e1e66ee614f2a2c902c1964.msu -f:* C:\WUTemp
DISM.exe /Online /Add-Package /PackagePath:C:\WUtemp\ssu-17763.5084-x64.cab
  • Let me know if it says it was successful or if there are any errors. Or take a screenshot of the command prompt window and paste it into your next reply.
 

Attachments

The commands were successfully completed, and DISM also reached 100% for the update. However, when I tried to run the latest update, I still received error 0x80070003
 

Attachments

Rich (BB code):
2024-02-15 08:25:53, Info                  CBS    DriverUpdateUnstageUpdates failed [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]
2024-02-15 08:25:53, Error                 CBS    Doqe: Failed unstaging driver updates [HRESULT = 0x80070032 - ERROR_NOT_SUPPORTED]

Upload the setupapi.dev.log file
  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
657716925b62b-setup-api-dev-folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 
Download
6530fbb0f4101-56f31e53c97da-SFCFix.PNG
SFCFix and save it to your desktop.
  • Download the attachment SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
650ef5dbdfd06-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.
 

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.
650c22f99662d-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 System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Here's the next fix for another driver.

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.
650c22f99662d-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 System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Here's the next fix.

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.
650c22f99662d-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 System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

Hi,

After installing the driver you recommended, there was a restart, but the error persisted. Then I realized that several repositories were missing, as you indicated. I resolved it as follows: I compared the folder on this server with another server that was updating correctly, and I imported all the missing folders within System32/DriverStore/FileRepository. After that, the update worked correctly, and now the server is 100%. Thank you so much, Maxstar, for all your support!
 

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

Back
Top