Share via

Server 2019 std: Windows Update error 0x8007000d

Anonymous
Dec 8, 2023, 2:51 PM

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,

Windows Server Devices and deployment Install Windows updates, features, or roles

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

8 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    Mar 13, 2024, 3:55 PM

    I finally fixed it!

    For those who also encounter this, the solution for my situation was to export the following four registry keys from a working virtual Microsoft server 2019 and import them into the failing server:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\intelide

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pciide
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\storahci

    After the registry keys were replaced, I first restarted the server before I installed the updates!

    4 people found this answer helpful.
    0 comments
  2. Anonymous
    Dec 11, 2023, 3:28 AM

    Hi Primator,

    according to your CBS log, it seems to be caused by a failed driver file installation. To confirm this, you can search 0x8007000d in your setupact.dev.log.

    If this is indeed the cause of the error, you will need to reinstall the driver file named mshdc.inf.

    For more information about 0x8007000d, you can refer to Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Learn.

    Hope it helps.

    Kind regards,

    Lei

    0 comments
  3. Anonymous
    Dec 12, 2023, 11:06 AM

    Hi Lei,

    I had the same conclusion, but the issue is how to fix this corruption.

    Renaming the file (mshdc.inf) did not fix it, and copying the file from a wprking 2019 std server does not help either.

    And as far as i know, there is no installer or update package for this driver.

    System update randiness tool is not available for server 2019.

    I can not find the logfile setupact.dev.log on the server, ony setupact.log or setupapi.dev.log.

    Best regards,

    0 comments
  4. Anonymous
    Dec 13, 2023, 3:19 AM

    Sorry I misspelled, it should be setupapi.dev.log. This Log file contains information about Plug and Play devices and driver installation.

    0 comments
  5. Anonymous
    Dec 15, 2023, 11:27 AM

    Hi Lei Tao,

    found this 'error' in the logs:

     sto: Driver update 'tsprint.inf' is already reflected.  
 sto: Driver update 'sdstor.inf' is already reflected.  
 sto: Driver update 'sdbus.inf' is already reflected.  
 sto: No effective section names for 'mshdc.inf'.  
 sto: {Reflect Driver Package: C:\Windows\System32\DriverStore\FileRepository\mshdc.inf\_amd64\_893b22a378783eb8\mshdc.inf}  
 sto:      Flags          = 0x00020F3F  
 inf:      Class GUID     = {4d36e96a-e325-11ce-bfc1-08002be10318}  
 inf:      Class Options  = Configurable BootCritical  
 idb:      Driver packages:  
 idb:           mshdc.inf\_amd64\_893b22a378783eb8 (active)  
 idb:           mshdc.inf\_amd64\_e7706f527988d6c2  
 inf:      {Configure Driver: PCMCIA IDE/ATAPI Controller}  
 inf:           Section Name = pcmcia\_atapi\_Inst\_Server  
 inf:           {Add Service: atapi}  
 inf:                Start Type    = 0  
 inf:                Service Type  = 1  
 inf:                Error Control = 3  
 inf:                Image Path    = System32\drivers\atapi.sys  
 inf:                Display Name  = IDE Channel  
 inf:                Group         = SCSI Miniport

    !!! inf: Failed to query service configuration. Error = 0x0000000D
    inf: {Add Service: exit(0x0000000d)}
    inf: {Configure Driver: exit(0x0000000d)}
    !!! sto: Failed to reflect driver package. Error = 0x0000000D
    sto: {Reflect Driver Package: exit(0x0000000d)}
    !!! sto: Failed to reflect all driver updates. Error = 0x0000000D
    <<< Section end 2023/11/16 02:02:22.181
    <<< [Exit status: FAILURE(0x0000000d)]

    But I'm at a loss how to fix it.

    Best regards,

    0 comments