in-place upgrade impossible after clean install using NTlite.iso???

  • Thread starter Thread starter TreeMan
  • Start date Start date
Go to that ISO/USB and remove/rename the .\autounattend.xml file, that's normal Windows behavior.
NTLite did generate it, it's the Unattended portion.
You can temporarily rename it, until booting from that ISO/USB, then rename it back.

Let me know if that helped.

And an advance tip: when removing make sure to keep the Host Refresh/Manual setup compatibility enabled. No worries if you haven't unchecked any compatibilities and removed tons of components.
 
The .iso that's mounted in my screenshot is unaltered/fresh download from media creation tool.

However there was a leftover c:\autounattend.xml
I removed it and I'm still getting the odd behavior.

Is there anywhere else I should look?
 
Update:

tested on PC where I knew there could only be one autounattend.xml on C drive. and now its behaving normally again!

BTW on call with MS support for 3 hours this morning and they insisted that the reason it was behaving this way was because the the ISO I was using wasn't provided by the OEM (dell)

I promptly wasted another 3 hours with Dell support trying to acquire 1809x64.iso News alert: Dell will never provide anyone with an "ISO"


This should have been my first stop. save me 6 hours of grief..

THANK YOU!
 
Setup will use any autounattend.xml file it finds, if it finds more than 1 it hiccups.
 
TreeMan, glad to see that you solved it.
Btw this tool does not save unattended file to C:\Autounattend.xml, unless your image was copied directly to the C: drive while it was edited, without a subfolder to work in.
Btw always extract the ISO to a subfolder.

There is also an option in the tool to copy unattended file to boot.wim and image.wim in the Unattended - toolbar options, make sure that is not enabled so you have more control over this situation if ever needed.
 
nuhi Does that put the Autounattend.xml into the wims themselves? I only ever have it in the root.
 
Back
Top