Experienced users who have done sysprep, know the important rule to disable networking while in audit mode.
The reason is WU wants to update everything, including installed UWP apps, while you're working. And this results in image generalize failing, or broken user apps on first logon. A workaround is run Remove-AppxPackage before exiting audit.
Amar Honnungar has a different answer, making sysprep not touch Appx packages.
Windows: Sysprep fails with “Package xy installed for a user, but not provisioned for all users”
Remove lines from C:\Windows\System32\sysprep\Generalize.xml:
With sysprep skipping those steps, it's safe to have networking or even have WU running. Edit Generalize.xml in the mounted image, or replace it from $OEM$.
The reason is WU wants to update everything, including installed UWP apps, while you're working. And this results in image generalize failing, or broken user apps on first logon. A workaround is run Remove-AppxPackage before exiting audit.
Amar Honnungar has a different answer, making sysprep not touch Appx packages.
Windows: Sysprep fails with “Package xy installed for a user, but not provisioned for all users”
Remove lines from C:\Windows\System32\sysprep\Generalize.xml:
Code:
<imaging exclude="">
<assemblyIdentity name="Microsoft-Windows-AppX-Sysprep" version="10.0.19041.1566" publicKeyToken="31bf3856ad364e35" processorArchitecture="amd64" versionScope="NonSxS"/>
<sysprepOrder order="0x1A00"/>
<sysprepValidate methodName="SysprepGeneralizeValidate" moduleName="$(runtime.system32)\AppxSysprep.dll"/>
<sysprepModule methodName="SysprepGeneralize" moduleName="$(runtime.system32)\AppxSysprep.dll"/>
</imaging>
With sysprep skipping those steps, it's safe to have networking or even have WU running. Edit Generalize.xml in the mounted image, or replace it from $OEM$.