Windows 10 can't show the EULA

LeoI07

New Member
I've been trying to make a slimmed down version of Windows 10 using NTLite. I'm testing it out in a virtual machine. I got an ISO with a working installation process, but only once. Every other time, after getting past the product key and edition selection screens, the installer threw an error:
Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.
EULAError.png
I know I could just automate the setup process so that the license terms are automatically accepted without having to "read" them. The thing is, I want to have my custom Windows 10 version installed from a single ISO, where it loads a 32-bit installer that allows you to select which architecture you want to install (which I already know how to do), but automating the setup process causes neither of the two options to show up.
Please let me know if you have an idea about how to fix this.

Here's the preset used:
 

Attachments

Last edited:

nuhi

NTLite developer
Staff member
Hi,

mostly it could be a wrong product key, try with none set.
Second is when people mix wrong boot.wim (may be adjusted, check on the web how) and try to make AIOs, so first see if no changes and just creating the ISO has the same issue, then it's not related to NTLite.

If it's not any of that, please attach the preset used which triggers the issue for review.

Thanks.
 

LeoI07

New Member
Hi,

mostly it could be a wrong product key, try with none set.
Second is when people mix wrong boot.wim (may be adjusted, check on the web how) and try to make AIOs, so first see if no changes and just creating the ISO has the same issue, then it's not related to NTLite.

If it's not any of that, please attach the preset used which triggers the issue for review.

Thanks.
I attached the preset, is the issue being reviewed?
 

nuhi

NTLite developer
Staff member
I attached the preset, is the issue being reviewed?
But I replied, saying it's the product key or wrong/unadapted boot.wim when dealing with AIO situations ("custom Windows 10 version installed from a single ISO").
You didn't reply anything to it, so what is there to test.
In other words, I know of no component that can break EULA...but of course there could be regressions, so if you cover all of the mentioned causes, let me know if you can confirm it with just using the preset on an official full Microsoft ISO.

Thanks.
 

LeoI07

New Member
But I replied, saying it's the product key or wrong/unadapted boot.wim when dealing with AIO situations ("custom Windows 10 version installed from a single ISO").
You didn't reply anything to it, so what is there to test.
In other words, I know of no component that can break EULA...but of course there could be regressions, so if you cover all of the mentioned causes, let me know if you can confirm it with just using the preset on an official full Microsoft ISO.

Thanks.
I've tried disabling all automation and AIO functionality, and it still throws the error.
 

Kasual

Well-Known Member
I've tried disabling all automation and AIO functionality, and it still throws the error.
Try a clean source and don't use unattended, if you see the error again, please feed back.

Edit:
I have seen: you are runnng Pro version in host and edited Home Single Language version, the Single Language isn't equal to non-singe language, there could be the issue when your computer is branded,like an Asus or Sony.
 
Last edited:

LeoI07

New Member
Try a clean source and don't use unattended, if you see the error again, please feed back.

Edit:
I have seen: you are runnng Pro version in host and edited Home Single Language version, the Single Language isn't equal to non-singe language, there could be the issue when your computer is branded,like an Asus or Sony.
I was using the Single Language version because it's the most slimmed down, so it served as the best base for what I was aiming for. The host machine is a MacBook Pro (13-inch, non-Retina) running Windows with Boot Camp, and it doesn't appear to be branded within the OS, so I don't see the problem there.
 

George King

New Member
This problem with Windows Setup Engine should be caused with missing License in install.wim / install.esd.
Be sure, your image have License files here
Code:
install.wim\%ImageIndex%\Windows\system32\%LanguageCode%\Licenses
If you don't have it, copy it from other location into mounted image and commit changes and try setup again

This is how Windows 10 Professional Licences folder look on my real system.
Code:
C:\WINDOWS\System32\cs-CZ\Licenses\OEM
C:\WINDOWS\System32\cs-CZ\Licenses\Volume
C:\WINDOWS\System32\cs-CZ\Licenses\_Default
C:\WINDOWS\System32\cs-CZ\Licenses\OEM\Professional
C:\WINDOWS\System32\cs-CZ\Licenses\OEM\Professional\license.rtf
C:\WINDOWS\System32\cs-CZ\Licenses\Volume\Professional
C:\WINDOWS\System32\cs-CZ\Licenses\Volume\Professional\license.rtf
C:\WINDOWS\System32\cs-CZ\Licenses\_Default\Professional
C:\WINDOWS\System32\cs-CZ\Licenses\_Default\Professional\license.rtf
I discovered this when I tried create Single Language edition of Windows 7 Thin PC with removed English language pack and integrated Czech. This folder doesn't exist and I received same error, when Windows 8+ Setup Engine was used.
 

LeoI07

New Member
This problem with Windows Setup Engine should be caused with missing License in install.wim / install.esd.
Be sure, your image have License files here
Code:
install.wim\%ImageIndex%\Windows\system32\%LanguageCode%\Licenses
If you don't have it, copy it from other location into mounted image and commit changes and try setup again

This is how Windows 10 Professional Licences folder look on my real system.
Code:
C:\WINDOWS\System32\cs-CZ\Licenses\OEM
C:\WINDOWS\System32\cs-CZ\Licenses\Volume
C:\WINDOWS\System32\cs-CZ\Licenses\_Default
C:\WINDOWS\System32\cs-CZ\Licenses\OEM\Professional
C:\WINDOWS\System32\cs-CZ\Licenses\OEM\Professional\license.rtf
C:\WINDOWS\System32\cs-CZ\Licenses\Volume\Professional
C:\WINDOWS\System32\cs-CZ\Licenses\Volume\Professional\license.rtf
C:\WINDOWS\System32\cs-CZ\Licenses\_Default\Professional
C:\WINDOWS\System32\cs-CZ\Licenses\_Default\Professional\license.rtf
I discovered this when I tried create Single Language edition of Windows 7 Thin PC with removed English language pack and integrated Czech. This folder doesn't exist and I received same error, when Windows 8+ Setup Engine was used.
Thanks for the advice, it worked. I traced the problem to an absence of the English language pack.
However, when I try to install the OS, after the installer restarts into the second phase, it gives me a blue screen of death with this information:
Stop code: PAGE_FAULT_IN_NON_PAGED_AREA
What failed: volmgr.sys
Screenshot coming soon

There are several "volmgr.sys" files in the WinSXS folder, so I can't really tell which one, if any, is missing or broken. Is there a way I can fix it?
 

garlin

Active Member
Thanks for the advice, it worked. I traced the problem to an absence of the English language pack.
However, when I try to install the OS, after the installer restarts into the second phase, it gives me a blue screen of death with this information:

Screenshot coming soon

There are several "volmgr.sys" files in the WinSXS folder, so I can't really tell which one, if any, is missing or broken. Is there a way I can fix it?
Sounds like a possible driver issue.
 

garlin

Active Member
Could you post the updated preset, since the first attachment has no drivers. PAGE_FAULT_IN_NON_PAGED_AREA is a serious error pointing to restricted memory, which tends to be kernel drivers. Missing libraries wouldn't cause this type of error.
 

garlin

Active Member
I don't see anything obvious.

Go with nuhi and George King's advice, confirm the preset works on a clean, non-AIO ISO distribution. If you didn't download it from MSFT, can't be sure if the builds are mixed or matched.
 

LeoI07

New Member
I don't see anything obvious.

Go with nuhi and George King's advice, confirm the preset works on a clean, non-AIO ISO distribution. If you didn't download it from MSFT, can't be sure if the builds are mixed or matched.
It does work, I was always using WIMS made from ESDs from ISOs created by the media creation tool.
 

nuhi

NTLite developer
Staff member
LeoI07, thanks, tried and cannot replicate this.
Note that it is a 32-bit image in the preset, so that's what I used, still cannot make it crash with your preset.

Maybe in the future retry with the latest NTLite at that time, and x64 image if the machine can run it.
Could be a driver issue after all, I would be surprised that the identical ISO not edited does not produce the same result.
If you ever need a driver to integrate, like a disk controller, check this guide.
 

Kasual

Well-Known Member
There would be scsidev driver (at first), Windows Subsystem for Linux (probably not), BitLocker Drive Encryption, mobilePC, Enhanced Storage, Hyper-V.
 

boydf

New Member
I'm having the exact same issue. I'm not setting anything different from many times in the past. Something has changed with NTLite updates. Hope you can resolve. Am going to try again with a clean source iso and not set any unattended settings.
 

nuhi

NTLite developer
Staff member
I'm having the exact same issue. I'm not setting anything different from many times in the past. Something has changed with NTLite updates. Hope you can resolve. Am going to try again with a clean source iso and not set any unattended settings.
Make sure to isolate the preset doing it for my testing, and which exact Windows image to replicate this.
Other than the mentioned already, the wrong product key being entered under unattended setup, that's expected.
Or replacing the boot.wim, keep the one that came with in the original ISO.

Thanks.
 
Top