Windows 10: Image Windows 10 laptops with DISM (or other free tool)

Can't see any errors in your answer file, just a strange computer name (RENAME). I guess that's an OK name if your purpose is to remind users to change the PC name.

 

Yeah, that was me that put that name in the answer file. Just a reminder.

So I copied your answer file to my image and still get prompted at the language screen so I'm guessing I've screwed something up in my image or it's the version I'm using.

I may just start over as I now have no idea what's going on! *Eek

 

Let's check that you are doing this correctly. No offence, I just don't know how experienced you are with the process.

• You install Windows on a technician machine from a valid, standard install media (not your customized ISO)?
• You reboot to Audit Mode before any user accounts have been created, when installation is done and stops to ask regional settings?
• You customize Windows as you wish and sysprep with /generalize switch?
• You capture the image and deploy it to a production machine?

Is answer to all four questions above Yes?

 

I'm not offended at all *Tongue I have imaged machines in the past but it's been a while and have not done this for Windows 10. I'm happy to admit I've screwed up or don't know something!

To answer your questions, the answer is YES to all of them.

So I have just tried a fresh install of Windows 10 Enterprise LTSB 1607 in a VM. I didn't make any changes or install any updates and I was still prompted after booting off the ISO for the language selection despite using an answer file.

These are the steps I took:

• Install Windows 10 Enterprise LTSB 1607 (en-gb_windows_10_enterprise_2016_ltsb_x64_dvd_9060114.iso)
• At Get Going Fast screen hit Ctrl+Shift+F3 to enter Audit mode
• Click Cancel on the Sysprep dialog after reboot
• Install VMware tools and reboot and clicked Cancel on the Sysprep dialog again
• Copied (your) answer file to c:\windows\system32\sysprep\unattend.xml
• Ran: c:\windows\system32\sysprep\sysprep.exe /generalize /oobe
• Power on VM, boot from original installation ISO and do a Shift F10 at the language screen to go to cmd
• Dism /capture-image /imagefile:d:\install.wim /capturedir:c:\ /name:System
• Shutdown machine
• Create a new ISO with the new install.wim using UltraISO
• Create new VM and install Windows using newly created ISO (with customised wim and answer files)
• And this is when I get prompted for the language selection expecting an unattended install

 

One test I would like to ask you to do:

Repeat steps 1 through 5 on your list. Step 6, run sysprep command with additional /reboot switch:

Code: c:\windows\system32\sysprep\sysprep.exe /generalize /oobe /reboot[/quote]
Let Windows sysprep and restart, does it skip OOBE now or do you still get normal OOBE?

 

OK, first test done. Copied your answer file from post #28, didn't change a character in it, run Sysprep on freshly installed Windows 10 Enterprise LTSB 2016.

Worked without issues, setup skipped OOBE. This is the first stop after installation:




No issues, worked exactly as it should.

I cannot understand why it does not work for you.

 

So I ran through steps 1 to 6 but for step 6 I ran this instead (/restart didn't work)

Code: c:\windows\system32\sysprep\sysprep.exe /generalize /oobe /reboot[/quote] After doing all this and rebooting I am back at the "Get going fast" screen:

 

Oh hang on! After I clicked "Use express settings" it took me to the login screen and I can see your username "Kari" so I guess it worked?

 

That was a typo, I fixed it already but apparently you read my post before typo was fixed. The restart switch is /reboot, not /restart as I first wrote. Sorry.

Really strange. Did you see this post?

 

No need to apologise *Biggrin

Ok, so I have done two tests using steps 1 through to 6. Test 1 was with your answer file and Test 2 was with my answer file. Both tests worked successfully. For my answer file I got prompted for my accounts name but besides this I wasn't prompted for anything!

Now, the confusing thing is, how do I now get this working with a customised install.wim and updated ISO? The tests above verify that the answer file is working correctly so what is causing this to not work later on?

(thanks for all your help, you've been terrific!!)

 

Only difference I can see is that I use Hyper-V VM as technician machine, you use VMware. That shouldn't matter, though.

I'll run one more test, capturing install.wim, making ISO, clean installing from it. This takes time, an hour and half to two hours. Will post back.

 

Thanks Kari, I'm starting from the beginning again to see if it makes any difference!

 

Just to let you know, I have to take a break. I will promise I will continue testing and troubleshooting tomorrow. I've done pretty much nothing else today than this, I am sorry but I need to stop now for today.

 

That's ok, I had to take a break too! I'll post some more findings tomorrow.

 

So after starting from the beginning again I have come to the following conclusion(s):

• My answer file works when I reboot the VM after running /generalize/ oobe /reboot and the unattended install works 100%
• If I take the customised install.wim file and use dism /apply-image after booting off the original Windows 10 ISO, the answer file works and the unattended install (again) works 100%
• This is where it goes wrong: If I open the original Win10 ISO in UltraISO and then replace the original install.wim with my own custom install.wim and create a new (customised) ISO with my own install.wim file then when I boot off this new ISO it prompts me at the language screen for user input. So I'm guessing that either I am doing something wrong in UltraISO or this program doesn't work properly with updating Windows 10 ISOs.

I'm going to try seeing if there are any other options to update an original Windows 10 ISO with a customised install.wim tomorrow.