[SOLVED] Windows Server 2019 Standard VM - KB5010351 Won't Install - Found Driver Issue

[TechFA]

Hello,

I've hit a wall trying to figure out why KB5010351 will not install on one of my Windows Server 2019 Standard VMs. As far as I can tell, it's getting stuck registering a driver...

SFC, DISM, SFCFix and ComponentsScanner come back clean.

CBS.log
-----------------------

2022-02-28 14:31:30, Info CBS Perf: Doqe: Staging started.
2022-02-28 14:31:30, Info CBS Doqe: [Forward] Staging driver updates, Count 80
2022-02-28 14:31:30, Info CBS STAGE index: 4, phase: 1, result 1009, inf: oposdrv.inf
2022-02-28 14:31:30, Info CBS Doqe: Recording result: 0x800703f1, for Inf: oposdrv.inf
2022-02-28 14:31:30, Info CBS DriverUpdateStageUpdates failed [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-02-28 14:31:30, Error CBS Doqe: Failed staging driver updates [HRESULT = 0x800703f1 - ERROR_BADDB]
2022-02-28 14:31:30, Info CBS Perf: Doqe: Staging ended.
2022-02-28 14:31:30, Info CBS Setting ExecuteState key to: CbsExecuteStateFailed

setupapi.dev.log
-----------------------

Failed to register driver package 'C:\Windows\System32\DriverStore\FileRepository\oposdrv.inf_amd64_313106b94d0b5742\oposdrv.inf'. Error = 0x000003F1

Short of trying to run an in-place upgrade, what can I do to remedy this? Any help would greatly be appreciated.

 

[TechFA]

Ahhhh, I just ran the following command and found corruption: dism /online /get-drivers /format:table > C:\drivers.txt

Deployment Image Servicing and Management tool
Version: 10.0.17763.1697

Image Version: 10.0.17763.2452

Obtaining list of 3rd party drivers from the driver store...

Error: 1009

The configuration registry database is corrupt.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

How do we go about fixing this?

 

[TechFA]

I finally figured it out myself:

1. Renamed C:\Windows\System32\config\DRIVERS to C:\Windows\System32\config\DRIVERS.bad
2. Copied C:\Windows\System32\config\DRIVERS from a good VM
3. Re-ran dism /online /get-drivers /format:table > C:\drivers.txt and resulted in good output
4. Added administrators full write permission to C:\Windows\System32\DriverStore\FileRepository
5. Used Beyond Compare to compare C:\Windows\System32\DriverStore\FileRepository of the good VM to bad VM, copied missing directories to bad
6. Re-ran KB5010351 downloaded copy

 

[philc43]

Sorry there was no one available to help but well done on fixing it yourself!

Thank you for letting us know.