Windows cannot find the Microsoft Software License Terms. Make sure the installation sources are valid and restart the installation.

J

johnny7pop

New Member
Messages
24
Reaction score
3
Hello
I think I have found a small issue in the latest, and some of previous versions of NTLite that introduced edition change removal (probably not 100% sure).
After removal of said component windows setup cannot start due to missing licence.rtf
"Windows cannot find the Microsoft License Terms. Make sure the installation sources are valid and restart the installation"
files from windows/system32/en-us/licences

To bypass this I've backed up the file from iso before edit and put them back into install.wim but I think they probably shouldn't be removed in the first place.

The second issue that I have and have not encountered or found cause for it is after first reboot during installation I have black screen and that's in the end can't do anything, while I have used very similar preset in the previous versions of NTLite in the past in the latest version I get the black screen or would get critical service failed, often damaging the rest of the boot systems, (multi boot partitions for testing)

While I had managed to narrow down in regards to critical service failed was caused by previous versions of NTLite when custom backup was selected and if image was edited for the second time would repeat custom backup removal would cause this.
With the black screen after first restart during installation I have no clue what's going on.
Preset attached.
 

Attachments

Last edited:
Yes, a user reported this problem, nuhi must protect this file also for non-Pro versions (Enterprise among others).
When this component is deleted
It's in the to-do list
 
Thanks for the reply, any advice on the second issue ?
I had used the same preset in the older version of NTLite and 2025.4.10406 hoping it will be partially compatible and it actually works windows installed without a problem, so there is probably something new in between them versions yet I cannot say which one is.
 
Oh no, I mixed up two posts.
What do you call a custom backup ?
 
Sorry clean update backup custom, but after testing this is not a problem in latest version, the only problem is that using this preset in the latest version of NTlite installation during first reboot gives me a black screen basically telling me game over while if I use this preset in the older version it works just fine.
 
Okay, with the same preset, it's fine with the old version of NTLite, but it's an error with the latest version, right ?
Strange, nothing has changed in this Custom cleaning option (for updates).
 
No, this preset was firstly made in the latest version and it would not install, first reboot and black screen when it should be starting services getting devices ready and so on it just like freezes and stuck, using that preset on the older version NTLite works fine, at this time I'm going through with it again and will recheck "windows setup and deployment/audit mode" and see if it makes any difference.
 
OK I think I finally got to the bottom of it
"Edition change support" component removal didn't just break the licences files that blocked the installation, I would copy the licences.rtf files where they should be and installation would start, but it would eventually fail anyway after first restart the black screen was caused by it, I don't know what files have been removed alongside the licences files but they where needed for the system to install.
I thought it was something else, some other component that I've removed but it's the same component.
Still best would be for an expert to investigate. I'm sure nuhi will get around it in no time whenever he has the time.
 
Yes, there are multiple .rtf files which are kept with the Pro versions, for example
Enterprise versions use the .rtf files from the Pro versions.

Keep this component until a fix is added in a future version of NTLite

EDIT : Example of files kept

Code: 
System32\xx-xx\Licenses\OEM\Professional\license.rtf
System32\xx-xx\Licenses\Volume\Professional\license.rtf
System32\xx-xx\Licenses\_Default\Professional\license.rtf

System32\Licenses\neutral\OEM\Professional\license.rtf
System32\Licenses\neutral\Volume\Professional\license.rtf
System32\Licenses\neutral\_Default\Professional\license.rtf
 
Last edited:
There was 3 of them in the folder _Default OEM and Volume each has EnterpriseS folder i it and the license.rtf file but adding them back will let the installation to start but it will fail at first reboot, I don't know what other files where removed along with edition change support so yeah this currently breaks the install, or at least in cases of LTSC / Enterprise channels.
 
Nuhi will fix the problem fairly quickly for "Enterprise" edition, I think
 
Thank you, the reason was that IOTEnterpriseS edition actually has EnterpriseS license, "IOT" part is ignored.
I could not replicate with other editions.

Fix will be in the next update when more changes are collected.
 
I think there is one more I'm not 100% sure about but it seems that VBScript seems bugged, marked as recommended but it was removed anyway, and that caused AMD chipset drivers unable to install, had to redo the whole image. Just now I had loaded an image and just unchecked VBScript and it actually shows removing both 32bit and VBScript (64) too.
 

Attachments

  • VBScript.png
    VBScript.png
    204.6 KB
You must log in or register to reply here.
Back
Top