[SOLVED] Windows Server 2019 (VM) Failure to Update KB5034768, KB5034683, KB5034127 (Part 2)

richmolasses

richmolasses

Member
Joined
Feb 29, 2024
Posts
24
Previous Post [SOLVED] - Windows Server 2019 (VM) Failure to Update KB5034768, KB5034683, KB5034127 (Resolved)

When attempting to install KB5034768, KB5034683, KB5034127 on a second Windows Server 2019 VM I am receiving an update error 0x800703f1. The other server was able to be updated thanks to Gary R.

Noted same error message [HRESULT = 0x800703f1 - ERROR_BADDB] is shown a number of times within the CBS log file.

I have tried the following:

SFC
SFC /Scannow

Result: Windows Resource Protection did not find any integrity violations.

DISM

DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.3406

Image Version: 10.0.17763.5206

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Components Scanner

==== Repair Log ====
No possible repairs

==== Warnings ====
None

I have uploaded the CBS zip and ComponentsScanner log.
 

Attachments

  • Navigate to C:\Windows\System32\Config and locate the DRIVERS 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 DRIVERS.ZIP on your desktop.
  • Please attach it to your next post.
  • The file may sometimes be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
Gary R said:
  • Navigate to C:\Windows\System32\Config and locate the DRIVERS 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 DRIVERS.ZIP on your desktop.
  • Please attach it to your next post.
  • The file may sometimes be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
Click to expand...
Driver's file attached.
 

Attachments

Warning: this fix is specific to the user in this thread, and no one else should follow these instructions.

  • Download DRIVERS.ZIP and save to your Desktop.
  • Right-click on it and select Extract all....
    • Make sure the Show extracted files when complete is checked and click Extract.
    • You should now have the DRIVERS file that we will be using to replace your current one.

Next ...

  • Navigate to C:\Windows\System32\config
  • Right-click on the current DRIVERS file and select Rename.
    • Rename it to DRIVERS.old
    • Note .... If you get an error that the file is in use, reboot your computer and then try again.
  • Take the file from the DRIVERS folder on your desktop and paste it into C:\Windows\System32\config

Next ....

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

Provided drivers file swapped out after renaming existing file to DRIVERS.old

DISM ran successfully.

CBS.log attached.
 

Attachments

Latest CBS.log looks good, so please try updating your machine.

If successful please let me know.

If not, please post the CBS.log created after the update attempt. Also post a copy of your setupapi.dev.log
  • Please go to C:\Windows\INF
  • Copy the file setupAPI.dev.log
  • Please attach it to your reply post
 
Gary R said:
Latest CBS.log looks good, so please try updating your machine.

If successful please let me know.

If not, please post the CBS.log created after the update attempt. Also post a copy of your setupapi.dev.log
  • Please go to C:\Windows\INF
  • Copy the file setupAPI.dev.log
  • Please attach it to your reply post
Click to expand...
Hi Gary, I will complete this tonight when I can schedule an outage window and report back the results.
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.
 

Attachments

Gary R said:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.
Click to expand...
SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-03-26 22:59:59.327
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\User\Desktop\Update Troubleshooting\SFCFixScript.txt [0]




FileScan::
[0: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5458.1.12\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf
File is untraceable.
Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE=
Version number not available.
Trace not available.



[1: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5458.1.12\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf
File is untraceable.
Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg=
Version number not available.
Trace not available.



[2: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5329.1.4\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf
File is untraceable.
Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE=
Version number not available.
Trace not available.



[3: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5329.1.4\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf
File is untraceable.
Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg=
Version number not available.
Trace not available.



[4: 2] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf
Expected: UNKNOWN Found: uEAix0km7JhbhxXXwfCZkfV2jPLLLU1OkCSB2X0bYSI=
Expected: 10.0.17763.348 Found: Version number not available.
Failed to trace component amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d with return code -3.

[C:\Windows\INF\oposdrv.inf]


[5: 1] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf
File is untraceable.
Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg=
Version number not available.
Trace not available.



[6: 1] C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf
File is untraceable.
Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE=
Version number not available.
Trace not available.



[7: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5576.1.19\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf
File is untraceable.
Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE=
Version number not available.
Trace not available.



[8: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5576.1.19\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf
File is untraceable.
Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg=
Version number not available.
Trace not available.



[9: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5206.1.3\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\r\oposdrv.inf
File is untraceable.
Found: uvq5FrDzmEUUaWNDvJPFJBtegj6IatNpUUqQHqqHPWE=
Version number not available.
Trace not available.



[10: 1] C:\Windows\servicing\LCU\Package_for_RollupFix~31bf3856ad364e35~amd64~~17763.5206.1.3\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\f\oposdrv.inf
File is untraceable.
Found: QbS1T6eZ+lCyU9AJYy5ittjBx4yzEMiXksmmHbk08yg=
Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2024-03-26 23:07:03.909
Script hash: K0AZppfO219+jC0X9fjAFteQoTapGYDzw1myK/7VtLQ=
----------------------EOF-----------------------
 
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

  • Download the attachment SFCFixScript.txt and save it on your desktop.
  • Save any work you have open, and close all programs.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
1p8eDnI.gif

  • SFCFix will launch, let it complete.
  • Once done, a file will appear on your desktop, called SFCFix.txt
  • Open the file, then copy and paste its content in your next reply.

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

SFCFix Output:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-03-27 01:55:08.269
Microsoft Windows Server 10 Build 17763 - amd64
Using .txt script file at C:\Users\User\Desktop\SFCFixScript.txt




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\System32\DriverStore\FileRepository

Successfully created directory tree \\?\C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742.

Successfully copied file C:\Windows\WinSxS\amd64_dual_oposdrv.inf_31bf3856ad364e35_10.0.17763.348_none_361ac2b69ffff30d\oposdrv.inf to C:\WINDOWS\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf.

Successfully restored ownership for C:\WINDOWS\System32\DriverStore\FileRepository
Successfully restored permissions on C:\WINDOWS\System32\DriverStore\FileRepository
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2024-03-27 01:55:09.485
Script hash: ard4uUALUq0VohOhISc2SiwPSx/zt4RscQoTJkTXTKI=
----------------------EOF-----------------------

DISM Output:

Version: 10.0.17763.5206

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

CBS.log attached.
 

Attachments

Latest logs look good, please try updating your machine.

If successful please let me know.

If not, please post the CBS.log created after your update attempt.
 
Hey Gary, I can happily confirm that the updates have been installed successfully. Thank you again for all your great work, it is really appreciated! 👏
 
Good news. (y)

Glad we were able to resolve things for you.
 
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