Cannot find windows license terms?

[Gorstak]

I used to install apps and set them up the way I liked them, then captured the live image and rebooted from it if my system crashed. Since build 1809, I receive "cannot find software license term" message during the bootup proces of my captured image. The only thing changed from original image is my installed apps, or better put, install.wim file, so not sure what is happening with this build? Also, license.rtf is still in my system32 folder, and looks original to me.
I saw some weird help guides with ei.cfg and memory allocation for virtual machines, but I'm running this on my real desktop machine. I've been messing with this for the past 4 days and can't seem to find a solution and fix it. Help?

 

[Solaris17]

Modifying ei.cfg would work. Just make the modification before capturing your wim

 

[Gorstak]

what do you suggest I modify it to, and where do I place that file? I've tried placing it in sources folder on my pendrive with just

[channel]
oem

inside. Didn't work

 

[Solaris17]

what do you suggest I modify it to, and where do I place that file? I've tried placing it in sources folder on my pendrive with just

[channel]
oem

inside. Didn't work

Its needs to be burned into the wim it cant be just some loose file. Was it already displaying the error when you attempted the fix? If so the wim has been tainted and needs to be redone. Atleast thats best practice.

EDIT: you havent modified the unattend.xml have you? The only other time i've come across issues like this was formatting issues with it.

 

[Gorstak]

well microsofts page says to put it into sources folder, not wim file. wim is basically my C: drive. That's probably the entire issue!

 

[Solaris17]

well microsofts page says to put it into sources folder, not wim file. wim is basically my C: drive.

Oh I see, so your still running in audit mode then.

Like this thread where I tried to explain it

https://www.techpowerup.com/forums/threads/how-to-leave-a-workgroup.249408/#post-3939244

and this thread where I literally went over it

https://www.techpowerup.com/forums/threads/guide-making-a-better-diag-drive.249677/#post-3944553

You should not run a system in audit mode in production. It is not meant to do that. I encourage everyone reading this thread to look at this past explination before dumping man hours into trying to solve this problem.

 

[Gorstak]

I do not see ei.cfg mentioned in your post, nor am I in audit mode. And like I said in OP, everything worked fine until latest build.

 

[Gorstak]

update: this seems unfixable, not even backup works in new build.
You can create a recovery drive, but it's fat32 formatted and wont boot if formatted to ntfs, which means only files up to 4GB are allowed.
i've also tried creating a normal 1809 pendrive, and then delete install.wim and boot.wim and copy in winre.wim and rename it to boot.wim, and that works, but can't find image backup on same usb, only on hdd. Then I tried sharing the image backup folder to be a network share, but that requires a password to be used.
Basically, creating a custom installation is impossible.
I solved the issue with minitool shadowmaker 3rd party software without two thirds of ms bullshit...
If you want, you can download it here: http://m.majorgeeks.com/files/details/minitool_shadowmaker_free.html

 

[erpguy53]

better to download a new v1809 ISO image and create a bootable usb pendrive with it using rufus or that minitool shadowmaker
sometimes MS gives MSDN & Visual Studio subscribers updated 1809 ISOs with new cumulative updates (either jan. 2019 or feb. 2019) already integrated.