Windows 10 unattend.xml (sysprep answer file) challenge
-
@MRCUR Thanks for the XML, it does open up in SIM but produces this when tested in the real world:
-
@Boyan-Biandov Your image has a driver it doesn’t like if you are getting that, for the most part I don’t really audit mode anymore. I do what I need to do in Windows and go straight to OOBE from there makes it cleaner and easier to deal with. I am still using the same XML I have posted here and it still works so you might want to check your drivers.
Always keep in mind that you can get past that by hitting Shift F10 sometimes and running Explorer. Then you can check the Setup,log in the Panther folder to see what is happening.
-
Thanks, driver I don’t know about but there’s definitely something that baffles me: why would it look for the xml in this directory? I’m stumped on this one…Do you all have to copy the xml file to both locations before running sysprep against one of the copies?
2016-07-09 08:11:52, Error [oobeldr.exe] User input error was detected in unattend file. Error: [0x0] 2016-07-09 08:11:52, Info IBS UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure... 2016-07-09 08:11:52, Info IBS UnattendDumpSetting: ------Unattend setting error / warning------ 2016-07-09 08:11:52, Info IBS UnattendDumpSetting: Error code = 0x8030000b 2016-07-09 08:11:52, Info IBS UnattendDumpSetting: Pass = oobeSystem 2016-07-09 08:11:52, Info IBS UnattendDumpSetting: Component name = [Microsoft-Windows-Shell-Setup] 2016-07-09 08:11:52, Info IBS UnattendDumpSetting: -------------------------------------------- 2016-07-09 08:11:52, Info IBS UnattendErrorFromResults: Error text = Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].
-
@Boyan-Biandov That’s the directory that sysprep is actually run from & where logs are sent. I don’t believe the directory location is your issue.
-
@MRCUR said in Windows 10 unattend.xml (sysprep answer file) challenge:
@Boyan-Biandov That’s the directory that sysprep is actually run from & where logs are sent. I don’t believe the directory location is your issue.
You’ve been super patient so I really want to thank you for that and I don’t mean to contradict every post, I mean it. So it was exactly that, I had to copy my xml file to BOTH locations and then everything worked. Either I’m nuts or nobody had tested the November build of Windows 10 Pro ISO (the one that comes with SP1 integrated so to speak; version 1511 build 10586.420) to discover all those regularities. The ISO is MAK license specific (not retail) straight off eOpen under an EA (same key, few thousand activation allowed). I’ve monkeyed with sysprep for a decades and this is the first I see crazy crap like this
-
@Boyan-Biandov Hmm, that’s really odd. The unattend file I posted is what I still use today on brand new installs of 10586 (the Nov update) and I place the file (named unattend.xml) in C:\Windows\system32\sysprep - that’s it, nowhere else. Below is the sysprep command I execute (I run this from C:\Windows\system32\sysprep):
sysprep.exe /generalize /oobe /shutdown /unattend:unattend.xml -
@MRCUR I actually put it in both out of habit, if you look at my scripts, (I think I have them posted) I delete the xml from both locations. But again this is habit form doing it for so many years.
-
@Psycholiquid I did see it in your script but I have NEVER put it in \panther just the \sysprep as you posted your command so maybe your habit saved you from facing my “challenges” lol
-
Hi,
i also use the xml outside the sysprep folder:
/unattend:c:\pathtoxml\unattend.xmlRegards X23
-
@Boyan-Biandov I also have basically re-used my Win7 unattend, though I did run it through the Win10 SIM to validate it. The only place I put it is in C:\Windows\Systems32\Sysprep folder. However, I have had the “Windows could not parse…” error and in looking at the setuperr.log in C:\Windows\Panther\UnattendGC folder (this one is different than the setuperr.log in C:\Windows\Panther, I don’t recall how though), it pointed me in the general direction of the <ProductKey>xxx</ProductKey> entry in “Specialize” pass. I ended up removing all product key entries and don’t have the error anymore. I have never really used audit mode, I just enter product key during installation and run “c:\Windows\System32\SLMGR.VBS” /ato" to re-activate after imaging (in setupcomplete.cmd). Good luck!
Edit: Forgot to mention that it always seemed to me that the unattend in C:\Windows\Panther was a post-sysprep record with all the sensitive data removed from the file by Windows as it processed it. I never before ran into any instructions to put it both places so I never have. Now if someone could tell me how they make the Win10 Default User profile keep the pinned icons on the taskbar I’d be the happiest camper alive.
