Wrong Windows 10 version on install?

Tannah

New Member
When I create a Windows 10 2004 pro image with NTlite: 2.0.0.7580, When I install it reports that it is Windows 10 2004 Enterprise?
I'm rather confused, I didn't do anything different. I've created images with NTlite before.
Any insights?
 

Tannah

New Member
So to clarify I'm using the Windows 10 X64 2004 iso created by the Media Creation Tool.

To try and figure this out, I used the iso to create a Windows 10 2004 Home image, and though NTlite 2.0.0.7580, applying all the same settings.
When I install the Windows 10 Home 2004 image onto a computer it does report home.
 

nuhi

NTLite developer
Staff member
Hi,

thanks for reporting.

most importantly what does the Windows report, please post a screenshot of the start - run - winver
If it's Pro, then NTLite just needs a reading correction, I did change something around that due to the new deployed image loading support.
Again if it's Pro, please send me the reg export of
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion
But trim the subkeys, or just send a screenshot of the location, right side.
 

Tannah

New Member
Hello nuhi,

Thank you for your response.
I reinstalled windows 10 Pro/Enterprise 2004 again to get the information you requested.

This information is from before applying the fix of changing Enterprise to Pro that I posted in my previous post.
I hope this is helpful
*I should add this install does have a active Windows 10 Pro licence associated with the computer.

Capture.PNG
 

Attachments

Last edited:

Tannah

New Member
Hello nuhi,

Here same files after I change it to pro using the method in that website.
I hope you are able to glean some information from this.

after key change.PNGwinver after.PNG
 

Attachments

nuhi

NTLite developer
Staff member
Thanks Tannah.

Since Windows also recognize it as Enterprise, it's not a readout bug, but actually wrong Windows version was installed.

If it's repeatable, meaning you load a Pro version and it installs an Enterprise one, can I get a preset (xml file with settings) replicating the issue?
Also make sure that there is no Unattended file (e.g. .\autounattend.xml) in the ISO itself already or that you copy it after editing, as that can have in it automatic install of a certain edition - of course ntlite-created one can stay, you can check in it what does it state under:
Code:
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>Windows 10 Pro</Value>
                        </MetaData>
                    </InstallFrom>
 

Clanger

Well-Known Member
make sure that there is no Unattended file (e.g. .\autounattend.xml) in the ISO
or anywhere on the system during install. windows will look everywhere for an answer file. i hate multi edition images :mad:
 

Tannah

New Member
Ok, You gave me a Idea I'm going to try first. That and the computer I'm testing with needs to be finished.
This preset XML I've used with minor tweaks since 1809. I've found it quite stable.
The Odd thing is that I made a image of Home from this same script and multi image without a issue. Enterprise isn't even a option in the image.
ntsnip.PNG

I'll post that XML after I try tweaking a setting, to see if it resolves my issue. Microsoft may have changed something.
 

nuhi

NTLite developer
Staff member
Thanks.
In the preset (same code is used to generate autounattend.xml from that part) it is set correctly:
Code:
                        <InstallFrom>
                            <MetaData>
                                <Key>/IMAGE/NAME</Key>
                                <Value>Windows 10 Pro</Value>
                            </MetaData>
                        </InstallFrom>
Are you sure that maybe ISOs weren't mixed up, for example forgot to update the USB stick with the current image and/or .\autounattend.xml on it?
I know the question seems silly, but I don't see any other reason to install the wrong image.

Btw you can also use Remove Unnecessary Editions option on the Apply page to remove other editions, that way it would be impossible to install the wrong one.
 

Tannah

New Member
Hi nuhi,
No the ISO that I'm using does not have enterprise edition. I posted a picture above of what the ISO loads into ntlite initially
I use Rufis 3.11 to take the ISO and put it on a flash Drive. Rufis quick formats the drive before applying the ISO
There is a autounattend.xml as part of the ISO, But NTlite creates it.
I'll try the remove un-needed removal. I think it just pulls of windows pe?


I don't know how relevant this is, but the computer I was installing ISO to originally was a Asus a15 with a AMD Ryzen 7 4800H Processor.
On a Dell XPS 15 7590 Running a Intel Core i7-9750H, the Same ISO installs as Windows 10 Pro? But there are other issues.
For some reason on the Dell XPS 15 7590 it appears that part of the image does not install The programs that are in the Post setup, and some of the registry files, but not all the registry files?
Perhaps this can give a idea of where it was switching from Pro to Enterprise. But I find it odd that the image seems not to be installing fully?
As a side note when though and install the programs and registry files manually it does seem to cause any issues.

As confused as ever. Any insight would be appreciated. Is there a log file or somthing where I can see whats actually going on?
 

nuhi

NTLite developer
Staff member
Hi Tannah,

thanks for the info.
Puzzling indeed, as stated earlier next time use the Remove Editions option on the Apply page to remove all of the other unused editions, that way it would be impossible to install the wrong one.
As there is no Enterprise to begin with, then there must be some kind of a recovery partition on that machine, depending how the setup was started.
Make sure to boot it in UEFI mode from the bios, and that the prompt to boot from the USB stick was seen counting, then press any key.

As a sidenote there also the .\Sources\ei.cfg which may influence it, remove it manually before editing the image, there is also a component for it "Edition configuration file (EI.cfg)" if you want the tool to do it - and if it's even present, doesn't have to be, but when it is, in it is also written what to install.
NTLite does autoedit that normally, but it's worth checking.

Regarding the post-setup, it can be that an installer half-way threw an error or a prompt then the rest got skipped.
To debug that see here.

And the reg files, please use Integrate - Registry page for those, not Post-setup unless they require reapplying after.
And when using integrate - reg, if it still doesn't apply half of it, add those to the post-setup page for reapplying.
Sometimes user settings (HKCU) get reset on creating the profile after setup, so it's expected and not even post-setup reapply helps there.
But we can check that in more detail once you have a reliable setup.

Thanks.
 

Tannah

New Member
Hello nuhi,
Its booting in UEFI mode on this Dell laptop, I don't believe there is a way to boot this Laptop in non-UEFI.

I looked at the original Windows 10 2004 ISO from the Microsoft media creation downloader, and also the one that was processed by NTlite in .\Sources\ there was no ei.cfg file? I attempted doing a recursive search in the ISO root for ei.cfg but didn't come up with any files matching files.

As to the post-setup installer: I found the C:\Windows\Setup\Scripts\SetupComplete.cmd which would infer it was not run. I changed the @Echo off and put a pause a the end of the script before it would delete anything. Then ran SetupComplete.cmd as Administrator. Oddly there were no errors? I'll post a snip of it.

The registry files I set are in the Integrate - Registry category in NTlite. I'll have to go though them manually to see which applied and which did not.

setupcmd.PNG
I'm starting to wounder if this is a Dell Oddity? I'll have to try this on another computer and see what is shows.

Any insight would be appreciated.
 

nuhi

NTLite developer
Staff member
That setupcomplete execution looks good.

To invoke it on systems that skip it, e.g. usage of OEM product keys, use the Unattended - toolbar - OEM SetupComplete option
 

scaramonga

New Member
Yup, I've had this for a while now. Always 'Enterprise' after install, despite stripping all other editions out. Also never activates automatically, have to always enter my key each time to manually activate, which in turn, changes the edition to 'Pro'. I suspect because it's detecting that 'Enterprise' is not hardware activated on the system.

HP Laptop here, which originally had 'Home' on it.
 
Last edited:

nuhi

NTLite developer
Staff member
From the point of activation it's clear, but what images do you guy use if it has such an issue?
Also is it the same if not edited?

If only editing it causes it, I would need an exact image pre-edit uploaded somewhere and the exact preset causing the issue, link it in a private message - should not distribute images publicly.

Thanks.
 

scaramonga

New Member
I'll do a fresh install with the new H2 image, with latest CU (487) - the one that fixes the defrag bug, amongst others, this afternoon, and report back after I have edited the image and installed on laptop. If 'Enterprise' shows as version installed, then I'll PM you a link to unedited image with my preset :)
 

tharri

New Member
Watching with interest.... I had this same problem the last time I tried installing 2004 Pro. I ended up installing 1709 and didn't bother debugging it at the time.
 
Top