Merge remote-tracking branch 'upstream/main' into AB#7613-Troubleshoot-Windows-Update-Error-0x8007000d

Author: v-tappelgate

support/azure/.openpublishing.redirection.azure.json

@@ -5513,7 +5513,7 @@
       {
         "source_path": "entra/entra-id/welcome-entra-id.yml",
         "redirect_url": "/troubleshoot/entra/entra-id/welcome-entra-id",
-        "redirect_document_id": true
+        "redirect_document_id": false
       },
       {
         "source_path": "entra/entra-id/user-prov-sync/use-upn-matching-identity-sync.md",

support/azure/azure-storage/files/security/files-troubleshoot-smb-authentication.md

@@ -571,9 +571,7 @@ This mitigation applies only to clients that are:
 - Hybrid Microsoft Entra joined
 - Cloud-native (Microsoft Entra–only) clients cannot use this workaround.
 
-To apply this mitigation, configure a cloud trust between on-premises AD DS and Microsoft Entra ID for accessing Azure Files. For step-by-step guidance, see: [Configure a cloud trust for Azure Files authentication](files/storage-files-identity-auth-hybrid-cloud-trust?tabs=azure-portal)
-
-
+To apply this mitigation, configure a cloud trust between on-premises AD DS and Microsoft Entra ID for accessing Azure Files. For step-by-step guidance, see [Configure a cloud trust for Azure Files authentication](/azure/storage/files/storage-files-identity-auth-hybrid-cloud-trust).
 
 ## Error AADSTS50105
 

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

@@ -108,6 +108,8 @@ items:
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x8000ffff.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error code 0x80070002
       href: ../../../windows-server/installing-updates-features-roles/troubleshoot-windows-update-error-0x80070002.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
+    - name: Error 0x80070003 when Windows Update fails
+      href: ../../../windows-server/installing-updates-features-roles/error-0x80070003-windows-update-fails.md?context=/troubleshoot/azure/context/context
     - name: Error code 0x8007000d
       href: ../../../windows-server/installing-updates-features-roles/error-invalid-data-startup-installing-updates.md?context=/troubleshoot/azure/virtual-machines/windows/context/context
     - name: Error code 0x8007000e or 0x800705aa

support/windows-client/toc.yml

@@ -1421,6 +1421,8 @@ items:
     items:
     - name: Analyze log file entries that SFC.exe generates
       href: ./installing-updates-features-roles/analyze-sfc-program-log-file-entries.md
+    - name: Error 0x80070003 at startup after you install a Windows update
+      href: ../windows-server/installing-updates-features-roles/error-0x80070003-windows-update-fails.md?context=/troubleshoot/windows-client/context/context
     - name: Error code 0x8024402C when you try to install a Windows update or a Feature on Demand
       href: ./installing-updates-features-roles/error-0x8024402c-installing-update-feature-on-demand.md
     - name: Fix errors found in CheckSUR.log

support/windows-server/installing-updates-features-roles/error-0x80070003-windows-update-fails.md

@@ -0,0 +1,76 @@
+---
+title: Error 0x80070003 at Startup after You Install a Windows Update
+description: Discusses how to fix Windows Update error 0x80070003. When this issue occurs, the update can't install correctly. After the computer restarts, the installation rolls back.
+manager: dcscontentpm
+audience: itpro
+ms.date: 12/30/2025
+ai.usage: ai-assisted
+ms.topic: troubleshooting
+ms.reviewer: kaushika, dougking, v-appelgatet
+ms.custom:
+- sap:windows servicing,updates and features on demand\windows update fails - installation stops with error
+- pcy:WinComm Devices Deploy
+appliesto:
+- ✅ <a href=https://learn.microsoft.com/windows/release-health/supported-versions-windows-client target=_blank>Supported versions of Windows Client</a>
+- ✅ <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
+- ✅ <a href=https://learn.microsoft.com/lifecycle/products/windows-365target=_blank>Supported versions of Windows 365</a>
+- <a href=https://learn.microsoft.com/lifecycle/products/azure-virtual-machine target=_blank>Supported versions of Azure Virtual Machine</a>
+---
+# Error 0x80070003 at startup after you install a Windows update
+
+This article discusses how to fix Windows Update error 0x80070003. When this issue occurs, the update can't install correctly. After the computer restarts, the installation rolls back.  
+
+## Symptoms
+
+When you try to install a Windows update, the installation fails, and you receive the following error message:
+
+> Some update files are missing or have problems. We'll try to download the update again later. Error code: (0x80070003).
+
+## Cause
+
+This error typically means that driver files are missing or inaccessible.
+
+## Resolution
+
+> [!IMPORTANT]  
+>
+> - 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.
+> - 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).
+
+The most reliable way to fix this issue is to perform an in-place upgrade on the affected computer.
+
+> [!NOTE]  
+> For more information about how to upgrade VMs, see one of the following articles:
+>
+> - [In-place upgrade for VMs running Windows Server in Azure](/azure/virtual-machines/windows-in-place-upgrade)
+> - [In-place upgrade for supported VMs running Windows in Azure (Windows client)](../../azure/virtual-machines/windows/in-place-system-upgrade.md)
+
+If you experience error 0x80070003 during the in-place upgrade, see ["0x80070003" error and Windows upgrade fails during "Process Drivers for Migration"](../setup-upgrade-and-drivers/error-0x80070003-during-process-drivers-for-migration.md).
+
+If the issue persists, contact Microsoft Support. In the support request, share the path or file that isn't found. For information about how to identify this information, see the next section.
+
+## More information
+
+To identify the path that Windows Update can't find, follow these steps:
+
+1. On the affected computer, go to the %Windir%\logs\CBS folder (%Windir% represents the Windows directory on the computer's system drive).
+1. Use a text editor to open the most recent CBS.log file, and search for a ", error" string.
+1. Check the log entries that share the same timestamp as the error, and locate the path that's related to the error.
+
+   For example, the following excerpt shows that the issue occurred during the installation of Ntprint.inf (the Windows printer driver):
+
+   ```output
+   2017-12-06 15:30:46, Info    CBS         INSTALL index: 69, phase: 1, result 3, inf: ntprint4.inf
+   2017-12-06 15:30:46, Info    CBS   Doqe: Recording result: 0x80070003, for Inf: ntprint4.inf
+   2017-12-06 15:30:46, Info    CBS   DriverUpdateInstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
+   2017-12-06 15:30:46, Info    CBS   Doqe: Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
+   2017-12-06 15:30:46, Info    CBS   Perf: Doqe: Install ended.
+   2017-12-06 15:30:46, Info    CBS   Failed installing driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
+   2017-12-06 15:30:46, Error   CBS   Startup: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
+   2017-12-06 15:30:46, Info    CBS   Startup: Rolling back KTM, because drivers failed.
+   2017-12-06 15:30:46, Info    CBS   Setting ExecuteState key to: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed
+   2017-12-06 15:30:46, Info    CBS   SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 0
+   2017-12-06 15:30:46, Info    CBS   Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
+   2017-12-06 15:30:46, Info    CBS   Setting original failure status: 0x80070003, last forward execute state: CbsExecuteStatePrimitives
+   2017-12-06 15:30:46, Info    CBS   SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateStageDrivers | CbsExecuteStateFlagRollback | CbsExecuteStateFlagDriversFailed, SubStage: 1
+   ```

support/windows-server/toc.yml

@@ -1150,6 +1150,8 @@ items:
       href: ./high-availability/event-id-5120-cluster-shared-volume-troubleshooting-guidance.md
     - name: Cluster Shared Volume goes offline
       href: ./high-availability/csv-offline-after-component-goes-offline-during-active-io.md
+    - name: Cluster Shared Volumes don't respond during a planned cluster node drain
+      href: ./virtualization/shared-volumes-do-not-respond.md
   - name: Errors when running the Validation Wizard
     items:
     - name: Cluster validation account causes events or messages
@@ -2810,6 +2812,10 @@ items:
     items:
     - name: Can't change the ConfigStoreRootPath value of a Hyper-V cluster
       href: ./virtualization/cannot-change-configstorerootpath-value-hyperv-cluster.md
+    - name: Cluster Shared Volumes don't respond during a planned cluster node drain
+      href: ./virtualization/shared-volumes-do-not-respond.md
+    - name: Unresponsive VMs after cluster failover failure
+      href: ./virtualization/unresponsive-vms-after-cluster-failover-failure.md
     - name: Users can't connect to virtual server after failover
       href: ./virtualization/mac-address-changes-for-virtual-server.md
     - name: Windows updates don't install on VM cluster hosts
@@ -2918,6 +2924,8 @@ items:
       href: ./virtualization/vm-dda-luns-disappear-after-mpio-config.md
   - name: Virtual machine creation
     items:
+    - name: "Troubleshooting guidance: Creating Hyper-V virtual machines"
+      href: ./virtualization/troubleshoot-hyper-v-virtual-machine-creation.md
     - name: Error when you manage a VHD file
       href: ./virtualization/fail-to-manage-vhd-file.md
     - name: Microsoft server software and supported virtualization environments
@@ -2928,12 +2936,12 @@ items:
       href: ./virtualization/vm-missing-0x800704c8-0x80070033-0x800703e3.md
   - name: Virtual machine state
     items:
+    - name: "Troubleshooting guidance: Inaccessible or unresponsive Hyper-V VMs in clustered or standalone environments"
+      href: ./virtualization/hyper-v-start-state-access-failures-clustered-standalone.md
     - name: Get-VMNetworkAdapter command doesn't report IP addresses
       href: ./virtualization/get-vmnetworkadapter-doesnt-report-ip-addresses.md
     - name: Hyper-V environments experience frequent power-offs and rapid disk space consumption
       href: ./virtualization/hyper-v-power-off-rapid-disk-space-consumption.md
-    - name: Troubleshoot Hyper-V virtual machine start, state, and access failures
-      href: ./virtualization/hyper-v-start-state-access-failures-clustered-standalone.md
     - name: Virtual Machines enter the paused state
       href: ./virtualization/virtual-machines-enter-paused-state-low-disk-free.md
     - name: Virtual machine shutdown actions don't run
@@ -3242,6 +3250,8 @@ items:
       href: ./installing-updates-features-roles/cbs-log-file-record-entries-not-repaired-run-sfc.md
     - name: Description of System File Checker (Sfc.exe)
       href: ./installing-updates-features-roles/system-file-checker.md
+    - name: Error 0x80070003 at startup after you install a Windows update
+      href: ./installing-updates-features-roles/error-0x80070003-windows-update-fails.md
     - name: Error 0x8007000d at startup after you install a Windows update
       href: ./installing-updates-features-roles/error-invalid-data-startup-installing-updates.md
     - name: Error 0x800705aa when Windows Update fails