You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
15
+
- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
# Error 0x8007000d at startup after installing updates
18
+
# Error 0x8007000d at startup after you install a Windows update
17
19
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.
19
-
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?context=/troubleshoot/azure/virtual-machines/windows/context/context).
20
+
This article helps you resolve an issue that occurs when the computer restarts after you install a Windows update.
22
21
23
22
## Symptoms
24
23
25
-
When this issue occurs, you might experience any of the following symptoms.
24
+
You install a Windows update. The update appears to install successfully. However, when the computer restarts, the installation rolls back, and you receive a "0x8007000d (ERROR_INVALID_DATA)" error message.
25
+
26
+
## Cause
27
+
28
+
Typically, this issue has one of the following causes:
29
+
30
+
-**File corruption or registry corruption** - An old update is reported, and the related file or registry key locations are corrupted. This corruption can prevent the system from verifying the validity of catalog files.
31
+
32
+
-**Incorrect driver version** - Driver updates fail because of incorrect versioning. This issue causes the Windows update to fail during a restart.
33
+
34
+
## Resolution
35
+
36
+
> [!IMPORTANT]
37
+
>
38
+
> - If the affected computer is a Windows virtual machine (VM) that can't restart correctly or that you can't access by using SSH, make sure that you can use the Azure Serial Console to access the VM.
39
+
> - Before you troubleshoot this issue, back up the operating system disk. For information about this process for VMs, see [About Azure Virtual Machine restore](/azure/backup/about-azure-vm-restore).
40
+
41
+
The most reliable way to fix this issue is to perform an in-place upgrade on the affected computer.
42
+
43
+
> [!NOTE]
44
+
> For more information about how to upgrade VMs, see one of the following articles:
45
+
>
46
+
> -[In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade)
47
+
> -[In-place upgrade for supported VMs running Windows in Azure (Windows client)](../../azure/virtual-machines/windows/in-place-system-upgrade.md)
48
+
49
+
If the issue persists, contact Microsoft Support. In the support request, include data from the CBS log that helps describe the issue. For information about how to identify this information, see the next section.
50
+
51
+
## More information
52
+
53
+
Entries in the Component-Based Servicing (CBS) log file might provide more details about how the error actually occurred. This log is typically located at C:\Windows\Logs\CBS. To track down the issue, open the log file in a text editor, and search for `ERROR_INVALID_DATA`. To identify the context in which the error occurred, review the log entries that precede and follow the error.
54
+
55
+
The following sections show examples of log entries that document this error.
26
56
27
-
### Symptom 1: Catalog file errors
57
+
### Case 1: Catalog file errors
28
58
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:
59
+
In this example, `ERROR_INVALID_DATA` occurs when the system tries to validate C:/WINDOWS/Servicing/Packages/Package_1_for_KB4584642~31bf3856ad364e35~amd64~~10.0.1.0.cat.
30
60
31
61
```output
32
62
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
@@ -42,15 +72,11 @@ Entries in the Component-Based Servicing (CBS) log file indicate issues that aff
42
72
20xx-xx-06 xx:51:15, Info CBS Failed to begin deployment installation for Update: 4584642-1_neutral [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
43
73
```
44
74
45
-
In this situation, the error occurs because the system can't determine whether the following catalog fileis valid:
75
+
The system can't validate the .cat (catalog) file. This indicates that the package is probably corrupted.
This symptom indicates that the package is likely corrupted.
50
-
51
-
### Symptom 2: Registry errors
52
-
53
-
In the CBS log file, you see the following entry or something similar that indicates registry issues:
79
+
In this example, `ERROR_INVALID_DATA` occurs when the system determines that a registry value uses the wrong data type.
54
80
55
81
```output
56
82
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]
@@ -62,9 +88,9 @@ In the CBS log file, you see the following entry or something similar that indic
62
88
20xx-xx-24 05:13:10, Info CBS Failed to find or add the component family [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
63
89
```
64
90
65
-
### Symptom 3: Driver update failure
91
+
### Case 3: Driver installation failure
66
92
67
-
In the CBS log file, you see the following entry or something similar that indicates driver update failures during restart:
93
+
In this example, `ERROR_INVALID_DATA` occurs when the system tries to install drivers during the restart process.
68
94
69
95
```output
70
96
20xx-xx-18 15:21:14, Info CBS Perf: Doqe: Critical install started.
@@ -84,11 +110,9 @@ In the CBS log file, you see the following entry or something similar that indic
84
110
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
111
```
86
112
87
-
This entry shows that the driver updates failed. This issue caused the Windows update to also fail.
113
+
The mshdc.inf driver doesn't install correctly. This issue triggers the rollback process.
88
114
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**
115
+
The SetupAPI log (typically in C:\Windows\INF\setupapapi.dev) also records driver installations. In this example, the following excerpt from Setupapapi.dev.log provides additional information about Mshdc.inf, including the names and versions of the driver packages.
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?context=/troubleshoot/azure/virtual-machines/windows/context/context).
0 commit comments