Thanks in advance Adam .
Thanks in advance Adam .
I tested also with EFI boot and it doesn't work. EFI is not supported by VirtualBox for Windows and for a VM I see no benefit in using it so I'm not looking for a workaround. Worth noting though.
Don't enable EFI here:
Or you'll get this when you boot from your PE ISO.
[QUOTE=adamf;194072 I tested also with EFI boot and it doesn't work. [/QUOTE]
But according to David he have Windows 10 vm in EFI: Windows 10 Image - Customize in Audit Mode with Sysprep
After a bit more testing, to make it work with EFI you have to do this: (I know this is off on a bit of a tangent from this tutorial, but you can boot PE using both BIOS and EFI in VirtualBox only the ISO method doesn't work with EFI).
1. Create a new VHD
2. Make sure it is top of your list by altering the SATA ports. Note: Remember what SATA port Windows was on for step 7!
3. Format it in Windows and assign a drive letter (for example:V)
4. Write the PE Image using MakeWinPEMedia /UFD C:\WinPE_amd64 V: ( https://technet.microsoft.com/en-us/library/dn293200.aspx )
5. Remove the Windows 10 installation ISO and PE then boots OK.
7. When you have finished with PE disconnect the PE drive and reset to SATA port for Windows to its original value from step 2. The default is zero. Otherwise Windows will not boot.
Last edited by adamf; 11 Feb 2015 at 11:54. Reason: Added step 7
I was using 32 bit but otherwise the same. (Apologies I've not been near a computer today to feed back how I did - but it looks like you covered it anyway.)
I did find that if I did a full shutdown (shutdown /s /t 10) then I could press F12 in Virtualbox at startup, and select a boot device without needing to swap around the order of the disks.
It feels better to use the full shutdown rather than the 'hybrid shutdown' version in any case , because it means I'm starting with an image at the point when it's properly switched off, rather than partially hibernated.
Apparently Microsoft has got the Sysprep issues resolved in the latest Build 10041, released yesterday 18th of March 2015. Sysprep is working again as it should, I have already successfully customized the Windows 10 Build 10041 image as told in this tutorial.
There seems to be an issue though with the Windows ADK for Windows 10 Technical Preview, I had to create the answer file using ADK for Windows 8.1 and the 8.1 install.wim file. However, the end result was a fully functioning sysprepped Windows 10 Build 10041.
I will check a few more details to be absolutely sure I will tell the correct procedures, doing a few more test installs. I will update the tutorial within next few days and post again here when you can start using this method again.
Just a status update:
I have been installing and sysprepping since Wednesday evening all the time except sleeping a little every now and then. It's 3 AM Saturday now and I am slowly getting there, already seeing clear patterns as what can be done and what's a no go.
Good news is, after the disastrous bugs in Sysprep process in Build 9926 it finally (mostly) works in Build 10041. Even the <FolderLocations> tags work again without issues making it possible to relocate the complete Users folder and everything it contains to another drive.
Bad news is that to succeed you need a few workarounds, simply and easy to do but hopefully no longer needed when the 10 is finally released.
I will update this tutorial as soon as I can without hesitation offer working Sysprep scenarios. This weekend most probably but latest early next week.
WarningFirst Build 10074 Sysprep tests done, it looks that the CopyProfile is again broken. All scenarios I have now tested have failed if CopyProfile is set true. Please notice this is just a preliminary warning, I got the ISO created only a few hours ago and have done only 6 Sysprep runs testing different scenarios.
I will update the tutorial as soon as I have some definitive factual information.
I am somewhat disappointed, the CopyProfile=TRUE in answer file will still in Build 10122 cause an endless reboot loop when sysprepped and booted to OOBE.
This is an essential setting for image customization, I am sure it will be fixed. In the meantime I will prepare a video later today to show what can be done at the moment, and how it should be done. I will post the video link here when ready.
I also asked Gabe Aul if he has some more information on this subject, let's wait and see what he says.