I have used succesfully this method several times in Win 8.1
Last week I tried a clean install of Win 10 and the nightmare begun.
No matter what I do I always end up with this error message after lauching Sysprep
Tried with different medias. The last one downloaded from Microsoft Tech Bench, as recomended in Windows 10 ISO Download Tutorial.
In audit mode I double checked that Windows was really seeing the drive where I intend to move the User folder as D: (actually it is an array-0 of two HDs). Also checked that DVD drive was F:
My relocate.xml goes as follow:
<?xml version="1.0" encoding="utf-8"?>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<cpifflineImage cpi:source="wim:F:\sources\install.wim#Windows 10 Pro" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
The build of Windows 10 I'm trying to install is:
I also disconected the LAN cable during installs.
Tried in UEFI mode. Got this:
Tried in simple BIOS. Got this:
And now I have used all my bag of tricks and with no result and no clue from this cript error message.
I need help.
[Image Edited by Mod]
Last edited by essenbe; 01 Jul 2016 at 08:39.
A RAID system? If so the most probable cause is that sysprep does not recognize RAID controller. The empty error message and failing OOBE boot can also be caused by false drive assignments (in your case D: not being D: even if you see it as D: in Audit Mode) or wrong bit architecture in answer file.
You could try adding the /generalize switch to your sysprep command, it removes all hardware related information and drivers while sysprepping, letting Windows to start OOBE phase with installing generic Windows drivers. When OOBE starts after generalizing it checks the hardware, installs generic drivers and then starts updating them when finally booted to desktop.
A generalized image usually has less issues in going through OOBE after Syspep. I always generalize my Windows install images in order to create a totally hardware independent system image to be used for deployment to all my computers as told in this tutorial: Windows 10 Image - Customize in Audit Mode with Sysprep - Windows 10 Forums
To use /generalize switch with Sysprep command, replace the command told in Method One Step 3 in this tutorial with following command:
Code:%windir%\system32\sysprep\sysprep.exe /generalize /oobe /reboot /unattend:d:\relocate.xml
My recommendation in case the above does not work is to forget this method, clean install normally and use this method to relocate documents, pictures and such: Storage Save Locations - Change in Windows 10 - Windows 10 Forums
Alternatively, seeing that your Windows 10 is PRO edition giving you Hyper-V you could try creating a sysprepped install image on a Hyper-V virtual machine and try if that image could be deployed to your PC.
Thank you very much for the very fast response.
I will give the /gereralize option a try.
What is dificult to understand is that this is the same hardware I used the sysprep method and Win 8.1
The motherboard RAID controller and the wrong letter assignment issues should come up at that time but they didn't.
The same hardware, the same method.
Worked with Win 8.1 but not working this time.
I should go back to my rice field...
Thank you for this. I made a small change that I believe simplifies things quite a bit for Method One . When doing the initial clean install, create a "TempAdmin" account. (Windows tries to get you to start with an email address/Microsoft account but you can get to the option to just enter a user ID instead of email address). Then after running the sysprep routine and rebooting, create your real admin account during the re-started install procedure. Then delete the TempAdmin account after the install completes.
There is no need for a temporary admin account, rebooting to Audit Mode uses the built-in admin instead. Any additional accounts are not needed.
Excuse me, I've tried method one:
after reboot, ctrl+shift+f3;
while in audit mode, use diskpart to assign the drive I wish to use to D;
create relocate.xml in D:\; (also changed the vim path F:\ , the letter of my win10 usb stick)
open command prompt(admin);
type in %windir%\system32\sysprep\sysprep.exe /oobe /reboot /unattend:d:\relocate.xml
the system restarts and everything seems to be normal(wifi selection, customize/express settings, etc), but before I advance to the account creation part, the computer restarts and goes back(to wifi selection and stuff) like the first time, and this just loops infinitely.
To check whether it's because I didn't make sysprep work, I went to audit mode again, and checked to find out that C:\users actually did get moved to D:\users. On a side note, the start menu in audit mode also stopped working completely.
Moreover, I've also editted relocate.xml to make it assign to C:\users and tried again and see if it would revert to normal. After executing sysprep and restarting, I was able to make it to the user creation menu like normal. What is exactly the problem? Any help is much appreciated.
You mentioned "infinite" reboot loop, do you mean you have let Windows to reboot at least three times?