Win11 22H2 Pro only ISO installing as Enterprise Edition

SM03

SM03

Active Member
Messages
511
Reaction score
105
Hi,
I created a 22h2 22622.607 Win11 Pro only ISO from UUDP & there's no other edition included in this ISO
View attachment 8224

modded it via NTL, but after installation, the windows edition installed & shows as Enterprise
View attachment 8227

Using the latest NTLite 2v.3.8.8920 as usual, sharing the PRESET & Log attached if that helps to identify the issue, thanks.
 

Attachments

Last edited:
UUP dump doesn't recognize 22622.607, the highest is 601. 22621.607 is available.
The only way to switch over is by Enablement package.

And abbodi already answered your question. This isn't a NTLite problem.
 
garlin said:
UUP dump doesn't recognize 22622.607, the highest is 601. 22621.607 is available.
The only way to switch over is by Enablement package.

And abbodi already answered your question. This isn't a NTLite problem.
Click to expand...
I made 607 over the top of 601 ISO, by adding the LCU+PSFX of 607 LCU

& I don't understand how abbodi's answer (over there in MDL) is relevant here, in this case, that was a Q about which SSU to use, can you explain?
 
What does dism /get-currentedition report? NTLite cannot determine any better than DISM does.

My point with abbodi is you're aware this isn't an official Insider build.

It's the 80/20 rule. 80% of NTLite's users aren't on the bleeding edge, there's a lot of people still on EOL'ed releases (7, 8.1, 1809, 1903).
If you were nuhi, where would you spend the time supporting (paid) customers? Reporting bugs is useful for visibility, but you could be fixing bugs which disappear by the next release. If something remains broken after several builds, then it deserves a deeper dive.
 
garlin said:
What does dism /get-currentedition report? NTLite cannot determine any better than DISM does.
Click to expand...
In the installed system, dism /get-currentedition obviously reports it as Enterprise, that's what I screenshotted in my earlier post

Apart from NTL, When I load the same ISO, this is what I got via DISM command, checked both, before modding the ISO & after modding the ISO, you can see & check the size difference as well for that matter,
& in both ISO, DISM command reported the same edition i.e. PRO

1. before modding the ISO SS
View attachment 8242

2. After modding the ISO via NTL
View attachment 8238

Update: here, another installation 22622.601 fresh, still same ENT version installed
 
Last edited:
From the Windows Insider Blog:
2022-09-2922621.730 & 22623.730
"Insiders who were previously on Build 22622 will automatically get moved to Build 22623 via an enablement package."
2022-09-2222621.607
2022-09-2122621.601 & 22622.601

I suspect your 22622.607 is not legitimate, since it's missing from the roadmap.
601 is probably the last 22622 build, as Moment 1 is ready to merge into 22621 (it's October). It makes sense to bump Insiders to Moment 2.

22621.730 Pro:
Windows 11 Professional (22H2) x64 - 10.0.22621.730 (en-US)

Mounted:
Image Version: 10.0.22621.730
Current Edition : Professional

View attachment 8248

22623.730 Pro:
Windows 11 Professional (22H2) x64 - 10.0.22623.730 (en-US)

Mounted:
Image Version: 10.0.22623.730
Current Edition : Professional

View attachment 8249
 
garlin
not sure what do you actually mean by 'legitimate'

all my (UUP made) 22622.xxx (601/607) ISOs are nothing but 22621.xxx+ 22622 EP
that's how UUP ISO works, if I disintegrate that EP, it will simply produce 22621.XXX ISO whatever the user wants to

& if we talk about the 'legitimacy' of ISO release point,
all those UUPD ISOs are not official by that term, that released officially by MSFT for the end users
 
SM03 said:
I made 607 over the top of 601 ISO, by adding the LCU+PSFX of 607 LCU
Click to expand...
You're making the assumption this update works correctly on 22622, based on previous experience.

22621 & 22622 are mostly identical, except for the enablement package and default settings. Let's use Occam's Razor: what is the most logical conclusion?

- Prior to your "22622.607", your UUP dump images worked.
- UUP dump doesn't offer 22622.607
- Insider PM's don't mention 22622.607
- This is the only broken release.
- 22623.730 (which replaces 22622 track) works.

My point as back in post #2: This is unrelated to NTLite, and you have an unsupported release.
 
UUP show up with moments 1 and 2 - probably developer builds for sure.
FAQ is no help explaining.
Most actual version can always be found here.
 
garlin said:
You're making the assumption this update works correctly on 22622, based on previous experience.

22621 & 22622 are mostly identical, except for the enablement package and default settings. Let's use Occam's Razor: what is the most logical conclusion?

- Prior to your "22622.607", your UUP dump images worked.
- UUP dump doesn't offer 22622.607
- Insider PM's don't mention 22622.607
- This is the only broken release.
- 22623.730 (which replaces 22622 track) works.

My point as back in post #2: This is unrelated to NTLite, and you have an unsupported release.
Click to expand...
wow, & you completely ignored this part of my earlier post here, where I already told you that have tried 601 as well, but that didn't worked either, same result
Update: here, another installation 22622.601 fresh, still same ENT version installed
Click to expand...

& I never said anywhere in my post that I am sure this issue is causing my NTL modding. Just shared here for possible solution.
 
If you start from a failure source, you usually have the cause of your problems:
Installation to and start with:
Host>Windows 11 Pro (22H2) x64 - 10.0.22622.607 (Which you reported be a problem).
and trying to make changes to the same image:
<Version mode="offline">Windows 11 Professional (22H2) x64 - 10.0.22622.607 (en-GB)</Version>
This is NOT a NTL problem to blame from a faulty insider build installed trying to alter another faulty insiderbuild
 
Last edited:
I've had exactly the same issue with two systems this week. I'm using the official Windows 11 22H2 ISO as downloaded from Microsoft themselves -- 22621.608

It might not necessarily be a NTLite issue, as in my Google adventures I found https://learn.microsoft.com/en-us/a...-windows-11-pro-from-the-microsoft-store.html -- people had this issue before and that was clearly not using anything like NTLite. They managed to get it back from Enterprise to Pro by using some kind of generic Pro upgrade key (VK7JG-NPHTM-C97JM-9MPGT-3V66T). Tried this myself too -- after this, my Windows switched to Pro and Windows stated it was activated by a digital license linked to my Microsoft account.

I used NTLite 2.3.8.8920 but I'm currently in the progress of making a Pro ISO for a third system using the NTLite beta 2.3.8.8937. Let's see if that's going to make a difference. If it fails (and installs Enterprise) I'm also going to see if the official Microsoft ISO itself fails to install Pro too.
 
Here's a simple test case: install Windows twice.
First time as Local user with no networking, second time with the MS account.

Local user with no network demonstrates what the image does by itself. There is no activation from the MS account's license, or MS recognizing this system from before. After restoring the network, does the version change?
 
Could this be because NTL version used on a non-public supported Pro release automatically installs the included Entreprise version to be safe the install go error free despite the involuntary update?
I remember I gave the trick before from ENT2PRO here
 
You must log in or register to reply here.
Back
Top