Server 2019 std: Windows Update error 0x8007000d

Question

Good day to all,

I have a Windows server 2019 standard (Hyper-v guest) which does not install the monthly updates (CU's) anymore.
Install goes without error, but at the reboot the updates is reverted.

To fix this I tried:

1)
net stop wuauserv & net stop cryptSvc & net stop bits & net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
Ren C:\Windows\System32\catroot2 Catroot2.old
net start wuauserv & net start cryptSvc & net start bits & net start msiserver
Reboot server, installed the windows updates and rebooted again

2)
Ran without error:

• DISM /online /cleanup-image /RestoreHealth
• SFC /scannow
  installed the windows updates and rebooted again

Downloaded the latest CU (KB5031361), installed it manually and rebooted.

In the event log there is no clear error
In the CBS log I found:
2023-12-08 02:02:22, Info CBS INSTALL index: 164, phase: 2, result 13, inf: mshdc.inf
2023-12-08 02:02:22, Info CBS Doqe: Recording result: 0x8007000d, for Inf: mshdc.inf
2023-12-08 02:02:22, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2023-12-08 02:02:22, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2023-12-08 02:02:22, Info CBS Perf: Doqe: Install ended.
2023-12-08 02:02:22, Info CBS Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2023-12-08 02:02:22, Error CBS Shtd: Failed while processing non-critical driver operations queue. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2023-12-08 02:02:22, Info CBS Shtd: Rolling back KTM, because drivers failed.

As far as I know, the mshdc.inf driver is an AHCI driver, but this is a Hyper-V guest with only Hyper-V SCSI storage used.
This is a production SQL server, therefor any updates/fixes has to be done outside office hours.

Thanks in advance for the advice/support,

Answer 1

According to the log, error 0x0000000D indicates that there is a problem with the configuration of the atapi service, which is responsible for the IDE channel. You can try the following steps to resolve this issue:

1. Make sure you have admin privileges.
2. Open the Service Manager and check whether the "ATAPI" service has been started. If it doesn't, try starting the service manually.
3. If the service has already started, try reinstalling the driver. You can try using the "Update Driver" feature in Device Manager or download the latest driver from the manufacturer's website.
4. If the problem persists, try booting your computer in safe mode and retry installing the driver.

Answer 2

I have (if possible, I use the options "run as administrator')

2.

The service is not present in service.msc.
I found the service through cmd (sc query atapi), service is running, although there is no atapai device connected in this VM.

3.

No hardware device present in devmgmt.msc with this driver.

Driver used is the default driver provided in server 2019.

As far as I know, there is no update package available for this driver.

4.

Does not apply

Answer 3

I just want to say thanks for coming back and posting the fix for this. I had the same issue and applying the registry keys from a working machine solved it. Thank you!