[0x80070002 – 0x4000B] Failed to determine source edition type!

When you run Windows Setup to repair or upgrade your Windows 10 or 11 computer, the Setup fails with the following error:

We can't tell if your PC is ready to continue installing Windows 10. Try restarting Setup.

The setupact.log shows the Installation Type is ‘unknown’ and the Edition Type is empty.

Error CONX Failed to determine source edition type! Error: [0x80070002][gle=0x0000012a]
Info CONX Source OS: Host SKU Info: Edition = 'Professional', Edition Type = '', Installation Type = 'unknown', Product Name = 'Windows 10 Pro', Arch = amd64, StationType = Client Workstation, Stage type = Staged Image

SetupDiagResults.log shows this:

Error: SetupDiag reports abrupt down-level failure.
Last Operation: Finalize
Error: 0x80070002 - 0x4000B
LogEntry: 2023-01-13 16:37:21, Error CONX Failed to determine source edition type! Error: [0x80070002][gle=0x0000012a]

Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.


The error “Failed to determine source edition type” occurs if the InstallationType and EditionID registry values are missing or contain incorrect value data.


  1. Start the Registry Editor (regedit.exe)
  2. Go to the following location:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
  3. Create/Modify the “InstallationType” REG_SZ value and set client as its data.
  4. Create/Modify the “EditionID” REG_SZ value and set the appropriate SKU ID as the data — e.g., “Enterprise”, “Professional”, “Education”, etc. The following table shows the list of possible values for “EditionID”:
    Supported value OS SKU definition
    BusinessN Windows 10/11 Professional N (49)
    CloudEdition CloudEdition (Windows 11 SE (203)
    CloudEditionN CloudEditionN (Windows 11 SE N (202)
    Core Windows 10/11 Home (10/111)
    CoreCountrySpecific Windows 10/11 Home China (99)
    CoreN Windows 10/11 Home N (98)
    CoreSingleLanguage Windows 10/11 Home single language (100)
    Education Windows 10/11 Education (121)
    EducationN Windows 10/11 Education (122)
    Enterprise Windows 10/11 Enterprise (4)
    EnterpriseEval Windows 10/11 Enterprise Evaluation (72)
    EnterpriseG Windows 10/11 Enterprise G (171)
    EnterpriseGN Windows 10/11 Enterprise G N (172)
    EnterpriseN Windows 10/11 Enterprise N (27)
    EnterpriseNEval Windows 10/11 Enterprise N Evaluation (84)
    EnterpriseS Windows 10 Enterprise LTSC (125)
    EnterpriseSEval Windows 10 Enterprise LTSC Evaluation (129)
    EnterpriseSN Windows 10 Enterprise LTSC N (162)
    Holographic Windows 10 Holographic (136)
    IoTUAP Windows 10 IoT Core (123)
    IoTUAPCommercial Windows 10 IoT Core Commercial (131)
    IoTEnterprise Windows 10/11 IoT Enterprise (188)
    PPIPro Windows 10 TeamOS (119)
    Professional Windows 10/11 Professional (48)
    ProfessionalEducation Windows 10/11 Professional Education (164)
    ProfessionalEducationN Windows 10/11 Professional Education N (165)
    ProfessionalWorkstation Windows 10/11 Professional for workstation (161)
    ProfessionalN Windows 10/11 Professional for workstation N (162)
    ProfessionalSingleLanguage Windows 10/11 Professional Single Language (138)
    ServerRdsh Windows 10/11 Enterprise multi-session (175)

Source: Microsoft

This fixes the 0x80070002 – 0x4000B (“Failed to determine source edition type!”) error.

One small request: If you liked this post, please share this?

One "tiny" share from you would seriously help a lot with the growth of this blog. Some great suggestions:
  • Pin it!
  • Share it to your favorite blog + Facebook, Reddit
  • Tweet it!
So thank you so much for your support. It won't take more than 10 seconds of your time. The share buttons are right below. :)

Ramesh Srinivasan is passionate about Microsoft technologies and he has been a consecutive ten-time recipient of the Microsoft Most Valuable Professional award in the Windows Shell/Desktop Experience category, from 2003 to 2012. He loves to troubleshoot and write about Windows. Ramesh founded Winhelponline.com in 2005.

Leave a Comment