Skip to content

Commit eccf724

Browse files
v-tappelgatev-tappelgate
authored
Merge pull request #9583 from v-tappelgate/AB#6960-Windows-11-Upgrade-Failure-Error-0x800F0818
AB#6960: Windows 11 upgrade failure
2 parents f077fb8 + dc1fa67 commit eccf724

File tree

3 files changed

+105
-2
lines changed

3 files changed

+105
-2
lines changed

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

Lines changed: 101 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,101 @@
1+
---
2+
title: Error 0x800F0818 - 0x20003 Occurs During Upgrade from Windows 10 to Windows 11
3+
description: Provides a solution for error 0x800F0818 - 0x20003. This error occurs on some computers when you upgrade from Windows 10 to Windows 11.
4+
ms.date: 08/28/2025
5+
manager: dcscontentpm
6+
audience: itpro
7+
ms.topic: troubleshooting
8+
ms.reviewer: kaushika, jaysenb, kaushika
9+
ms.custom:
10+
- sap:windows setup,upgrade and deployment\installing or upgrading windows
11+
- pcy:WinComm Devices Deploy
12+
---
13+
14+
# "0x800F0818 - 0x20003" error during upgrade from Windows 10 to Windows 11
15+
16+
This article provides a solution for an error that occurs on some computers when you upgrade them from Windows 10 to Windows 11.
17+
18+
## Symptoms
19+
20+
You use one of the following systems to service Windows client computers:
21+
22+
- System Center Configuration Manager (SCCM)
23+
- Windows Server Update Services (WSUS)
24+
- Windows Update for Business
25+
26+
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.
27+
28+
If you run a diagnostic tool such as [SetupDiag](/windows/deployment/upgrade/setupdiag), the tool returns the same error code.
29+
30+
An error entry is logged in the C:\\$Windows.~BT\\Sources\\Rollback\\setupact_rollback.log file that contains text that resembles the following excerpt:
31+
32+
```output
33+
YYYY-MM-DD HH:MM:SS, Info MOUPG InitializeRoutine: MOSETUP_ACTION_IMAGE_EXIT
34+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing SetupResult: [0x800f0818]
35+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Extended: [0x20003]
36+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Scenario: [6]
37+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Mode: [5]
38+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Product: [1]
39+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing Target: [C]
40+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing SQM: [FALSE]
41+
YYYY-MM-DD HH:MM:SS, Info MOUPG ImageExit: Initializing PostReboot: [TRUE]
42+
```
43+
44+
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:
45+
46+
```output
47+
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]
48+
```
49+
50+
```output
51+
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]...
52+
```
53+
54+
```output
55+
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
56+
57+
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]
58+
59+
YYYY-MM-DD HH:MM:SS, Info CBS Failed to check capability logic [HRESULT = 0x800f0818 - CBS_E_IDENTITY_MISMATCH]
60+
```
61+
62+
## Cause
63+
64+
This issue affects devices that have one of the following histories:
65+
66+
- The device previously received a Windows 10 feature update that used a custom SetupConfig.ini file.
67+
- Earlier updates or upgrades to the device used language packs or post-upgrade scripts that were manually configured or deployed.
68+
69+
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:
70+
71+
```output
72+
[SetupConfig]
73+
InstallLangPacks=C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\LP
74+
PostOOBE=C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\SetupComplete.cmd
75+
PostRollback=C:\ProgramData\Temp\Inplaceupgrade\W10_22H2\Scripts\ErrorHandler.cmd
76+
DynamicUpdate=Disable
77+
```
78+
79+
These outdated references cause identity mismatches during the upgrade process. Therefore, the upgrade fails and rolls back.
80+
81+
## Resolution
82+
83+
[!INCLUDE [Important registry alert](../../../includes/registry-important-alert.md)]
84+
85+
To remove the legacy information, follow these steps:
86+
87+
1. On the affected computer, open File Explorer, and then go to C:\\Users\\Default\\AppData\\Local\\Microsoft\\Windows\\WSUS\\.
88+
> [!NOTE]
89+
> If you can't see the AppData folder, select **View** > **Show**, then select **Hidden items** to view hidden files and folders.
90+
91+
1. Delete the SetupConfig.ini file.
92+
93+
1. Open Registry Editor, and then go to the `HKEY_LOCAL_MACHINE\SYSTEM\Setup` subkey.
94+
95+
1. Delete the `UnattendFile` registry entry.
96+
97+
## More information
98+
99+
- [SetupDiag](/windows/deployment/upgrade/setupdiag)
100+
- [Resolve Windows upgrade errors: Technical information for IT Pros](/windows/deployment/upgrade/resolve-windows-upgrade-errors)
101+
- [Windows upgrade log files](/windows/deployment/upgrade/log-files)

‎support/windows-client/toc.yml‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -745,6 +745,8 @@ items:
745745
href: ./setup-upgrade-and-drivers/dynamic-link-library.md
746746
- name: Error when you access a USB storage device
747747
href: ./setup-upgrade-and-drivers/error-when-you-access-usb-storage-device.md
748+
- name: Error 0x800F0818 - 0x20003 Occurs during Upgrade from Windows 10 to Windows 11
749+
href: ./setup-upgrade-and-drivers/error-0x800f0818-during-upgrade-to-windows-11.md
748750
- name: Event ID 219 when a device is plugged into a Windows system
749751
href: ./setup-upgrade-and-drivers/event-id-219-when-device-plugged-in-windows-system.md
750752
- name: Event ID 7000 or 7026 after starting a computer

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Windows 11 Virtual Machine Doesn't Start After Migration From VMware to Hyper-V
33
description: Describes how to configure a Windows 11 virtual machine after you migrate it from VMware to Hyper-V.
4-
ms.date: 08/15/2025
4+
ms.date: 08/26/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
8-
ms.reviewer: kaushika
8+
ms.reviewer: kaushika, warrenw, v-appelgatet
99
ms.custom:
1010
- sap:virtualization and hyper-v\virtual machine state
1111
- pcy:WinComm Storage High avail

0 commit comments

Comments
 (0)