Replies: 2 comments
-
|
Sorry, I have never used Sysprep or Audit Mode, and I don't see a reason to do so. The primary use case of autounattend.xml files generated by my service is to install Windows from start to finish, without the need for Sysprep or Audit Mode. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
No problem. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Good morning.
Up until ISO 23H2, I performed the procedure with the generated autounattend file, completed it without any problems, then installed the created ISO and the installation went smoothly.
I performed the same, with file autounattend, AuditMode-SysPrep procedure with ISO 24/25H2, completed it without any problems or errors, then installed the created ISO, and at about 75% of the installation, I received the message “Windows 11 installation failed.”
Test 1- I copied the wim file from the ISO 25H2 and replaced it with the wim file in the 23H2 structure with the same autounattend file.
The AuditMode-SysPrep procedure completed without any problems, and when I installed the created ISO, the installation proceeded without any problems.
Test 2- I ran the AuditMode-SysPrep procedure with the 24/25H2 ISOs without the autounattend file. The SysPrep procedure completed without any problems, installing the created ISO, and the installation proceeded without any problems.
So it seemed clear to me that the autounattend file with only a few functions (TPM and productKey deactivation) as per the attached file:
https://justpaste.it/2hs4j
Creates some problems during the AuditMode phase with ISO 24\25H2, or is it better to avoid including the autunattend file for Audit mode in the new ISOs?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions