Server 2019 updates failing, but only after domain joining. For the life of me I can't see why! (I can't see any obvious GPO settings!)

[peteypie]

Hi team, I've been trying to trouleshoot and look at this for over a week, and it's driving me nuts.

Something seems to be stopping the majority (15 or so) of our 2019 VMs from updating since June time last year. I can't understand what it is.

These are Windows Server 2019, all domain joined, running on Hyper-V.
If I create a new VM, the system patches fine. To me, this seems to rule out something environmental/web filter/some other oddity.
As soon as I domain join, I can't patch it - it throws the same error (0x80070002) when trying to apply updates (cumulative and .Net updates seem to be mostly affected)
If I remove from the domain, it still doesn't patch - same error code.
The updates download and install, the server goes to reboot but fails around 9% updating and rolls back.

I've tried all the regular fixes, and even did a reinstall of Windows (keeping apps and docs, so not a complete wipe).
I can't see anything obvious in the default domain GPO that woudl be causing this. Its really light on what it sets.

I'm hoping someone that knows what they're looking for, can spot something in the CBS logs. I can see something about the usbstor.inf in the CBS log, but not sure if that's relevant. The VMs are on Hyper-V and don't have any USB pass-through or USB devices obviously listed in device manager.

Anyway, any help or pointers that you can see will be very gratefully appreciated.

CBS logs from one of the affected VMs I've been working on is attached.

Thanks again in advance!

 

[Windows Update Bot]

Hi @peteypie,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[peteypie]

I meant to also attach the componentscanner log too, sorry!

 

[peteypie]

I'm wondering if this is related to something around USBSTOR.

I see this in the CBS logs:
2025-01-21 13:51:39, Info CBS INSTALL index: 135, phase: 2, result 2, inf: usbstor.inf
2025-01-21 13:51:39, Info CBS Doqe: Recording result: 0x80070002, for Inf: usbstor.inf
2025-01-21 13:51:39, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-01-21 13:51:39, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-01-21 13:51:39, Info CBS Perf: Doqe: Install ended.
2025-01-21 13:51:39, Info CBS Failed installing driver updates [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-01-21 13:51:39, Error CBS Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2025-01-21 13:51:39, Info CBS Startup: Rolling back KTM, because drivers failed.


And this in the setupapi.dev.log

sto: No effective section names for 'usbstor.inf'.
sto: {Reflect Driver Package: C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_eed801326ad7a90b\usbstor.inf}
sto: Flags = 0x00020F3F
inf: Class GUID = {36fc9e60-c465-11cf-8056-444553540000}
inf: Class Options = Configurable BootCritical
idb: Driver packages:
idb: usbstor.inf_amd64_eed801326ad7a90b (active)
idb: usbstor.inf_amd64_ecde77a0735d75b1
inf: {Configure Driver: USB Mass Storage Device}
inf: Section Name = USBSTOR_BULK.NT
inf: {Add Service: USBSTOR}
inf: Start Type = 3
inf: Service Type = 1
inf: Error Control = 1
inf: Image Path = \SystemRoot\System32\drivers\USBSTOR.SYS
inf: Display Name = USB Mass Storage Driver
!!! inf: Failed to query service configuration. Error = 0x00000002
inf: {Add Service: exit(0x00000002)}
inf: {Configure Driver: exit(0x00000002)}
!!! sto: Failed to reflect driver package. Error = 0x00000002
sto: {Reflect Driver Package: exit(0x00000002)}
!!! sto: Failed to reflect all driver updates. Error = 0x00000002
<<< Section end 2025/01/21 13:51:39.458
<<< [Exit status: FAILURE(0x00000002)]


I don't know if that's terminal, or unrelated.

I've checked and reset permissions on the C:\windows\inf\usbstor.inf file
And checked that the file exists and the permissions "look OK" (they are inherited from the parent) at "C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_ecde77a0735d75b1" which is where the USBSTOR section in the registry points to.

However, I note above that its refering to a different path "C:\Windows\System32\DriverStore\FileRepository\usbstor.inf_amd64_eed801326ad7a90b\usbstor.inf" - is that what the setup is trying to apply/install and failing? Or should that actually exist?

Any help is really apprecaited!

Pete