Skip to content

Commit 5d514b0

Browse files
ryanberg-aquentryanberg-aquent
authored
Merge pull request #9981 from ryanberg-aquent/CI-7536
AB#7536: [Windows Server/Azure: New] Troubleshoot Windows Update Error 0x8007000d - Invalid Data - updates
2 parents f2e9c72 + baa126e commit 5d514b0

File tree

2 files changed

+101
-26
lines changed

2 files changed

+101
-26
lines changed

‎support/azure/virtual-machines/windows/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -237,6 +237,8 @@ items:
237237
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-code-0x8024002e.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
238238
- name: Error code 0x80070490
239239
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070490.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
240+
- name: Error 0x8007000d after installing Windows updates
241+
href: ../../../windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
240242
- name: Error Code 0x800f0831
241243
href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-installation-error-corruption.md
242244
- name: Error Code 0x8007045b

‎support/windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md‎

Lines changed: 99 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,51 +1,124 @@
11
---
2-
title: ERROR_INVALID_DATA error after installing Windows updates
3-
description: Helps resolve the 0x8007000d (ERROR_INVALID_DATA) error at system startup after installing Windows updates.
2+
title: ERROR_INVALID_DATA Error After Installing Windows Updates
3+
description: Helps resolve the 0x8007000d (ERROR_INVALID_DATA) error at system startup after you install Windows updates.
44
ms.date: 05/23/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
8-
ms.reviewer: kaushika, hamansoor, jdickson, v-lianna
8+
ms.reviewer: kaushika, hamansoor, jdickson, v-lianna, dougking
99
ms.custom:
10-
- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error
10+
- sap:Windows Servicing, Updates and Features on Demand\Windows Update - Install errors starting with 0x8007 (ERROR)
1111
- pcy:WinComm Devices Deploy
1212
appliesto:
1313
- <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
14+
- <a href=https://learn.microsoft.com/lifecycle/products/azure-virtual-machine target=_blank>Azure Virtual Machines</a>
1415
---
1516
# Error 0x8007000d at startup after installing updates
1617

17-
This article helps resolve an issue in which you receive the 0x8007000d (ERROR_INVALID_DATA) error at the system startup after installing Windows updates.
18+
This article helps you resolve an issue that occurs at system startup after you install Windows updates. After you install the updates and restart the system, the system performs a rollback, and you receive a "0x8007000d (ERROR_INVALID_DATA)" error message.
1819

19-
After you install an update and restart the system, the system performs a rollback at the system startup, and you receive the 0x8007000d (ERROR_INVALID_DATA) error.
20+
> [!IMPORTANT]
21+
> This article covers the Windows Server upgrade process for non-Azure servers and virtual machines (VMs) only. To do an upgrade of Windows Server running in an Azure VM, see [In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade).
2022
21-
This issue occurs because the database of performance counters is corrupted.
23+
## Symptoms
2224

23-
## Rebuild the performance counter setting
25+
When this issue occurs, you might experience any of the following symptoms.
2426

25-
To resolve this issue, follow these steps:
27+
### Symptom 1: Catalog file errors
2628

27-
1. Open an elevated Windows PowerShell prompt, and then navigate to the *C:\\windows\\system32\\wbem* folder by running the following cmdlet:
29+
Entries in the Component-Based Servicing (CBS) log file indicate issues that affect a catalog file. This log is typically located at *C:\Windows\Logs\CBS*. You see a log entry that resembles the following output:
2830

29-
```PowerShell
30-
cd C:\Windows\system32\wbem
31-
```
31+
```output
32+
20xx-xx-06 xx:51:15, Info CBS Exec: Installing Package: Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0, Update: 4584642-1_neutral, InstallDeployment: amd64_771d1f434ef835536dafe93d6811f766_31bf3856ad364e35_10.0.17763.1549_none_e4d395cdb7886270
33+
20xx-xx-06 xx:51:15, Error CSI 00000034@20xx/xx/5:23:51:15.422 (F) onecore\base\wcp\rtllib\win32lib\catalog.cpp(633): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function CCatalog::Create expression: CertCreateCTLContext
34+
[gle=0x80004005]
35+
20xx-xx-06 xx:51:15, Error CSI 00000035 (F) NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) #6317935# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 0[gle=0xd007000d]
36+
20xx-xx-06 xx:51:15, Error CSI 00000036 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #6317715# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8007000d]
37+
20xx-xx-06 xx:51:15, Error CSI 00000037 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #6317714# from Windows::ServicingAPI::CCSITransaction::AddCatalog(Flags = 1, CatalogPath = '[file://%3f/C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat')%5bgle=0x8007000d]\\?\C:\WINDOWS\Servicing\Packages\Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat')[gle=0x8007000d]
38+
20xx-xx-06 xx:51:15, Error CSI 00000038 (F) HRESULT_FROM_WIN32(ERROR_INVALID_DATA) #6317713# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_InstallDeployment(Flags = 0, a = 771d1f434ef835536dafe93d6811f766, version 10.0.17763.1549, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.4584642-1_neutral', rah = (null), manpath = (null), catpath = '[file://%3f/C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat%5bgle=0x8007000d]\\?\C:\WINDOWS\Servicing\Packages\Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat[gle=0x8007000d]
39+
20xx-xx-06 xx:51:15, Error CSI ', disp = 0)[gle=0x8007000d]
40+
20xx-xx-06 xx:51:15, Error CBS Failed to verify if catalog file [C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat]\\?\C:\WINDOWS\Servicing\Packages\Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat is valid. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
41+
20xx-xx-06 xx:51:15, Info CBS Failed to verify manifest against catalog, mark store as corrupt. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
42+
20xx-xx-06 xx:51:15, Info CBS Failed to begin deployment installation for Update: 4584642-1_neutral [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
43+
```
3244

33-
2. Run the following [wmiadap](/windows/win32/wmisdk/wmiadap) cmdlet to parse all the performance libraries:
45+
In this situation, the error occurs because the system can't determine whether the following catalog file is valid:
3446

35-
```powershell
36-
C:\Windows\system32\wbem>wmiadap.exe /f
37-
```
47+
*C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat*
3848

39-
3. Run the following [lodctr](/windows-server/administration/windows-commands/lodctr) cmdlet to rebuild the performance counter setting:
49+
This symptom indicates that the package is likely corrupted.
4050

41-
```powershell
42-
C:\Windows\system32\wbem>lodctr /r
43-
```
51+
### Symptom 2: Registry errors
4452

45-
Then, you receive the following message if the cmdlet runs successfully:
53+
In the CBS log file, you see the following entry or something similar that indicates registry issues:
4654

47-
```output
48-
Successfully rebuilt performance counter setting from system backup store
49-
```
55+
```output
56+
20xx-xx-24 05:13:10, Info CBS Registry value for Package_7762_for_KB5001347~31bf3856ad364e35~amd64~~10.0.1.4 is not a dword type. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
57+
20xx-xx-24 05:13:10, Info CBS Failed to enumerate values in store object. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
58+
20xx-xx-24 05:13:10, Info CBS Failed to enumerate all component versions for component detect: amd64_windows-application..egistrationverifier_31bf3856ad364e35_0.0.0.0_none_06e8f842c597e59b [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
59+
20xx-xx-24 05:13:10, Info CBS Failed to enumerate store versions on component: amd64_windows-application..egistrationverifier_31bf3856ad364e35_10.0.14393.4169_none_fcb27d831f9fb942 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
60+
20xx-xx-24 05:13:10, Info CBS Failed to enumerate related component versions on component: amd64_windows-application..egistrationverifier_31bf3856ad364e35_10.0.14393.4169_none_fcb27d831f9fb942 [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
61+
20xx-xx-24 05:13:10, Info CBS Failed to load current component state [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
62+
20xx-xx-24 05:13:10, Info CBS Failed to find or add the component family [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
63+
```
5064

51-
4. Install the update again.
65+
### Symptom 3: Driver update failure
66+
67+
In the CBS log file, you see the following entry or something similar that indicates driver update failures during restart:
68+
69+
```output
70+
20xx-xx-18 15:21:14, Info CBS Perf: Doqe: Critical install started.
71+
20xx-xx-18 15:21:14, Info CBS Doqe: [Forward] Installing driver updates, Count 2
72+
20xx-xx-18 15:21:14, Info CBS INSTALL index: 53, phase: 1, result 0, inf: machine.inf
73+
20xx-xx-18 15:21:14, Info CBS INSTALL index: 194, phase: 1, result 0, inf: mshdc.inf
74+
20xx-xx-18 15:21:14, Info CBS INSTALL index: 246, phase: 2, result 0, inf: machine.inf
75+
20xx-xx-18 15:21:14, Info CBS INSTALL index: 194, phase: 2, result 13, inf: mshdc.inf
76+
20xx-xx-18 15:21:14, Info CBS Doqe: Recording result: 0x8007000d, for Inf: mshdc.inf
77+
20xx-xx-18 15:21:14, Info CBS DriverUpdateInstallUpdates failed [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
78+
20xx-xx-18 15:21:14, Info CBS Doqe: Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
79+
20xx-xx-18 15:21:14, Info CBS Perf: Doqe: Critical install ended.
80+
20xx-xx-18 15:21:14, Info CBS Failed installing driver updates [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
81+
20xx-xx-18 15:21:14, Error CBS Startup: Failed executing critical driver operations queue [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
82+
20xx-xx-18 15:21:14, Info CBS Startup: Rolling back KTM, because drivers failed.
83+
20xx-xx-18 15:22:46, Info CBS Retrieved original failure status: 0x8007000d, last forward execute state: CbsExecuteStatePrimitives
84+
20xx-xx-18 15:22:52, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.4889.1.2, status: 0x8007000d, failure source: DOQ, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
85+
```
86+
87+
This entry shows that the driver updates failed. This issue caused the Windows update to also fail.
88+
89+
To verify that this condition is true, go to *C:\Windows\INF\setupapapi.dev*, locate the log, and examine the entries for the driver failure. In this case, it's mshdc.inf.
90+
91+
**setupapapi.dev.log**
92+
93+
```output
94+
sto: {Unstage Driver Package: C:\Windows\System32\DriverStore\FileRepository\mshdc.inf_amd64_b0b5572axx95167b\mshdc.inf} 15:21:14.3xx
95+
sto: {DRIVERSTORE DELETE BEGIN} 15:21:14.3xx
96+
sto: {DRIVERSTORE DELETE BEGIN: exit(0x00000000)} 15:21:14.3xx
97+
idb: {Unregister Driver Package: C:\Windows\System32\DriverStore\FileRepository\mshdc.inf_amd64_b0b5572axx95167b\mshdc.inf} 15:21:14.3xx
98+
idb: Unregistered driver package 'mshdc.inf_amd64_b0b5572axx95167b' from 'mshdc.inf'.
99+
idb: Deleted driver package object 'mshdc.inf_amd64_b0b5572axx95167b' from SYSTEM database node.
100+
idb: Driver packages registered to 'mshdc.inf':
101+
idb: mshdc.inf_amd64_79f38c21b894a1c1
102+
idb: {Unregister Driver Package: exit(0x00000000)} 15:21:14.3xx
103+
```
104+
105+
Make sure that you note the driver packages.
106+
107+
## Cause
108+
109+
This issue occurs either because the database of performance counters is corrupted or the driver version is incorrect.
110+
111+
### File corruption or registry corruption
112+
113+
An old update might be reported, and the related file or registry key locations might be corrupted. This corruption can prevent the system from verifying the validity of catalog files.
114+
115+
### Incorrect driver version
116+
117+
Driver updates might fail because of incorrect versioning. This issue causes the Windows update to fail during a restart.
118+
119+
## Resolution
120+
121+
> [!NOTE]
122+
> Before you proceed, [back up the OS disk](/azure/backup/about-azure-vm-restore).
123+
124+
The most reliable solution for this problem is to perform an [in-place upgrade (IPU) on the Windows virtual machine (VM)](/azure/virtual-machines/windows-in-place-upgrade).

0 commit comments

Comments
 (0)