SOLVED: Created NTlite ISO won't let me do inplace upgrades?

wingers

New Member
Hi

Have just created a NTLite'd ISO of 2004 following same steps I had noted down when I did it for 1903

But if I try and use this created ISO to update an existing Windows 10 earlier build to Windows 10 2004 the setup.exe is launching like it would to do a fresh install rather than an upgrade?

Can't fathom out what I have done differently / wrong?

If I try using the original Windows 10 2004 ISO I used as source it works, so must be something I have missed when creating the NTLite version?

Any thoughts please?
 
but I am trying to create an ISO to use to update multiple machines, just like I have before - how does host refresh help me as that is for machine I am building on and that is already up-to-date
 
No I didn't

This is really weird - if I double click the NTLite created ISO and then double click setup.exe it goes straight into a setup for a clean install

But if I extract all the files from the ISO and then run setup.exe it allows me to choose to upgrade existing system as expected

Never seen that before.....
 
Okay as per reply from Dino Nuhagic - "this is because of the autounattend.xml file - either remove it or rename it then it would work as it did before"

I can confirm this logic works, BUT as per my replies here and to Dino a previous 1903 build using NTLite 1.8.0.7120 ISO I have which has the autounattend.xml file works fine for upgrades whether files extracted or ISO just mounted in Windows by double clicking it - so behaviour has definitely changed for me at least

But anyway not a problem as I now know why and a workaround so problem closed
 
Last edited:
I know you've already solved this, but the solution I've used in the past was to run "sources\setupprep.exe" instead of "setup.exe".
 
I know you've already solved this, but the solution I've used in the past was to run "sources\setupprep.exe" instead of "setup.exe".
Very nice, will check and if successful (setup.exe has a bunch of switches which are welcome) or autounattend.xml detected, switching to that in the tool's Host Refresh.
 
Back
Top