Merge pull request #9604 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-26 22:00 UTC

Author: learn-build-service-prod[bot]

support/windows-client/setup-upgrade-and-drivers/error-0x800f0818-during-upgrade-to-windows-11.md

@@ -0,0 +1,101 @@
+---
+title: Error 0x800F0818 - 0x20003 Occurs During Upgrade from Windows 10 to Windows 11
+description: Provides a solution for error 0x800F0818 - 0x20003. This error occurs on some computers when you upgrade from Windows 10 to Windows 11.
+ms.date: 08/28/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, jaysenb, kaushika
+ms.custom:
+- sap:windows setup,upgrade and deployment\installing or upgrading windows
+- pcy:WinComm Devices Deploy
+---
+
+# "0x800F0818 - 0x20003" error during upgrade from Windows 10 to Windows 11
+
+This article provides a solution for an error that occurs on some computers when you upgrade them from Windows 10 to Windows 11.
+
+## Symptoms
+
+You use one of the following systems to service Windows client computers:
+
+- System Center Configuration Manager (SCCM)
+- Windows Server Update Services (WSUS)
+- Windows Update for Business
+
+A feature update from Windows 10 22H2 to Windows 11 23H2 or 24H2 fails in the Safe_OS phase, and generates error 0x800F0818 - 0x20003. After the failure occurs, the update rolls back.
+
+If you run a diagnostic tool such as [SetupDiag](/windows/deployment/upgrade/setupdiag), the tool returns the same error code.
+
+An error entry is logged in the C:\\$Windows.~BT\\Sources\\Rollback\\setupact_rollback.log file that contains text that resembles the following excerpt:
+
+```output
+YYYY-MM-DD HH:MM:SS, Info MOUPG InitializeRoutine: MOSETUP_ACTION_IMAGE_EXIT
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing SetupResult: [0x800f0818]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Extended: [0x20003]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Scenario: [6]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Mode: [5]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Product: [1]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Target: [C]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing SQM: [FALSE]
+YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing PostReboot: [TRUE]
+```
+
+Additionally, multiple error entries are logged in the C:\\$Windows.~BT\\Sources\\Panther\\setupact.log file. The contents of these entries resemble the following excerpts:
+
+```output
+YYYY-MM-DD HH:MM:SS, Info MOUPG SetupHost::Initialize: CmdLine = [/Product Client /PreDownload /Package /Priority Normal /Quiet /ReportId 96CEE****************3-2D4E1B1306F5.1 /FlightData "RS:24944" "/CancelId" "C-757a2**********************4256ca34" "/PauseId" "P-757a20**********************" "/CorrelationVector" "otIKT***B0mTOyAl.1.1.28.4" "/DownloadSizeInMB" "3046" /InstallLangPacks C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\LP /PostOOBE C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\SetupComplete.cmd /PostRollback C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\ErrorHandler.cmd /DynamicUpdate Disable /Compat IgnoreWarning]
+```
+
+```output
+YYYY-MM-DD HH:MM:SS, Info MOUPG SetupManager: Copying user-provided langpack package files from [C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\LP] -> [C:\$WINDOWS.~BT\LangPacks\User]...
+```
+
+```output
+YYYY-MM-DD HH:MM:SS, Info CBS Appl: Evaluating package applicability for package Microsoft-Windows-Xps-Xps-Viewer-Opt-Package~31bf3856ad364e35~amd64~~10.0.22621.1, applicable state: Installed
+
+YYYY-MM-DD HH:MM:SS, Info CBS Package doesn't match FOD for the current OS, package: Microsoft-Windows-LanguageFeatures-Basic-hu-hu-Package~31bf3856ad364e35~amd64~~10.0.19041.1, expected:Microsoft-Windows-LanguageFeatures-Basic-hu-hu-Package~31bf3856ad364e35~amd64~~10.0.22621.1 [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]
+
+YYYY-MM-DD HH:MM:SS, Info CBS Failed to check capability logic [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]
+```
+
+## Cause
+
+This issue affects devices that have one of the following histories:
+
+- The device previously received a Windows 10 feature update that used a custom SetupConfig.ini file.
+- Earlier updates or upgrades to the device used language packs or post-upgrade scripts that were manually configured or deployed.
+
+The upgrade failed because of a legacy SetupConfig.ini file that contains hard-coded paths to outdated language packs and scripts. Those language packs and scripts aren't compatible with Windows 11. The path to the legacy file typically is C:\Users\Default\AppData\Local\Microsoft\Windows\WSUS\SetupConfig.ini. The contents of the file resemble the following excerpt:
+
+```output
+[SetupConfig]
+InstallLangPacks=C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\LP
+PostOOBE=C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\SetupComplete.cmd
+PostRollback=C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\ErrorHandler.cmd
+DynamicUpdate=Disable
+```
+
+These outdated references cause identity mismatches during the upgrade process. Therefore, the upgrade fails and rolls back.
+
+## Resolution
+
+[!INCLUDE [Important registry alert](../../../includes/registry-important-alert.md)]
+
+To remove the legacy information, follow these steps:
+
+1. On the affected computer, open File Explorer, and then go to C:\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\\.
+   > [!NOTE]  
+   > If you can't see the AppData folder, select **View** > **Show**, then select **Hidden items** to view hidden files and folders.
+
+1. Delete the SetupConfig.ini file.
+
+1. Open Registry Editor, and then go to the `HKEY_LOCAL_MACHINE\SYSTEM\Setup` subkey.
+
+1. Delete the `UnattendFile` registry entry.
+
+## More information
+
+- [SetupDiag](/windows/deployment/upgrade/setupdiag)
+- [Resolve Windows upgrade errors: Technical information for IT Pros](/windows/deployment/upgrade/resolve-windows-upgrade-errors)
+- [Windows upgrade log files](/windows/deployment/upgrade/log-files)

support/windows-client/toc.yml

@@ -745,6 +745,8 @@ items:
       href: ./setup-upgrade-and-drivers/dynamic-link-library.md
     - name: Error when you access a USB storage device
       href: ./setup-upgrade-and-drivers/error-when-you-access-usb-storage-device.md
+    - name: Error 0x800F0818 - 0x20003 Occurs during Upgrade from Windows 10 to Windows 11
+      href: ./setup-upgrade-and-drivers/error-0x800f0818-during-upgrade-to-windows-11.md
     - name: Event ID 219 when a device is plugged into a Windows system
       href: ./setup-upgrade-and-drivers/event-id-219-when-device-plugged-in-windows-system.md
     - name: Event ID 7000 or 7026 after starting a computer

support/windows-server/toc.yml

@@ -2816,6 +2816,8 @@ items:
     items:
     - name: Can't add a second Fibre Channel adapter
       href: ./virtualization/cannot-add-second-fibre-channel-adapter-hyperv.md
+    - name: "Can't connect to Hyper-V shared storage on Windows Server 2016"
+      href: ./virtualization/cant-connect-to-hyper-v-shared-storage-on-windows-server-2016.md
     - name: Error message after you put the page file on another drive other than the drive C
       href: ./virtualization/error-message-page-file-another-drive-guest-operating-system.md
     - name: FCoE IO failures on Hyper-V guests

support/windows-server/virtualization/cant-connect-to-hyper-v-shared-storage-on-windows-server-2016.md

@@ -0,0 +1,59 @@
+---
+title: Can't Connect to Hyper-V Shared Storage on Windows Server 2016
+description: Provides guidance for troubleshooting connection issues that involve shared storage in a Windows Server 2016 Hyper-V environment.
+ms.date: 08/26/2025
+manager: dcscontentpm
+audience: itpro
+ms.topic: troubleshooting
+ms.reviewer: kaushika, simonw, v-appelgate
+ms.custom:
+- sap:virtualization and hyper-v\storage configuration
+- pcy:WinComm Storage High Avail
+---
+
+# Can't connect to Hyper-V shared storage on Windows Server 2016
+
+This article provides guidance for troubleshooting connection issues that involve shared storage in a Windows Server 2016 Hyper-V environment.
+
+## Symptoms
+
+You experience connection issues such as in the following scenarios:
+
+- You can't use Hyper-V virtual machines (VMs) to access or connect to shared storage.
+- VMs that rely on shared storage don't function correctly.
+
+These scenarios are especially difficult to diagnose because they don't generate specific error codes.
+
+## Cause
+
+Such connection issues most likely have one or more of the following causes:
+
+- Shared storage settings aren't correctly configured within the Hyper-V environment.
+- Virtualization-specific settings aren't correctly configured in Windows Server 2016.
+- Network settings, such as storage paths, aren't correctly configured.
+- Network connectivity is interrupted.
+
+## Resolution
+
+> [!IMPORTANT]  
+> Before you start troubleshooting, make sure that the following conditions are true:
+>
+> - You have Administrator-level permissions for the Windows Server 2016 computer.
+> - The Hyper-V role is correctly configured on the computer.
+> - The computer meets all relevant hardware and software requirements for shared storage. For more information, see [Windows Server storage architectures with Hyper-V](/windows-server/virtualization/hyper-v/storage-architecture).
+> - You're familiar with the procedure to configure Hyper-V and shared storage environments.
+
+To resolve the connection issue, follow these steps:
+
+1. Check your shared storage configuration. Make sure that the shared storage is correctly configured and accessible within your Windows Server 2016 environment.
+1. In Hyper-V, check the storage path settings.
+1. Check the network interfaces and switches between the computer and the shared storage devices. Make sure that they're correctly configured.
+1. Make sure that the computer successfully connects to the shared storage devices.
+1. In Hyper-V Manager, check the configuration of the VMs. Verify that the VMs correctly map to the shared storage.
+1. Make sure that the shared storage is online, and that the computer can access it.
+
+If the issue persists, collect the following information, and then contact Microsoft Support:
+
+- Notes that describe any adjustments that you made to the configuration and any observed changes in behavior.
+- Any events from the event log that might relate to the issue.
+- The results of any other diagnostic tests that you used on the system.

support/windows-server/virtualization/windows-11-vm-wont-start-after-migrating-from-vmware-to-hyper-v.md

@@ -1,11 +1,11 @@
 ---
 title: Windows 11 Virtual Machine Doesn't Start After Migration From VMware to Hyper-V
 description: Describes how to configure a Windows 11 virtual machine after you migrate it from VMware to Hyper-V.
-ms.date: 08/15/2025
+ms.date: 08/26/2025
 manager: dcscontentpm
 audience: itpro
 ms.topic: troubleshooting
-ms.reviewer: kaushika
+ms.reviewer: kaushika, warrenw, v-appelgatet
 ms.custom:
 - sap:virtualization and hyper-v\virtual machine state
 - pcy:WinComm Storage High avail