[German]I'm posting some information here in the blog for administrators who distribute Windows to devices using AutoPilot. It seems that the deployment process gets stuck immediately after accepting the Terms of Use (TOU). A meaningless error message appears and nothing works anymore.
Microsoft has offered the option of deploying Windows 10 or Windows 11 to devices using AutoPilot in Intune since 2017. The whole process is described in this Microsoft document, for example.
However, it now appears that the process of rolling out Windows 10 or 11 suddenly freezes as soon as the Terms of Service (TOU) have been confirmed. Nothing works anymore. I don't know how often the TOU option is selected by administrators in Intune during the AutoPilot rollout (you can also accept the Terms of Use in advance).
MVP Rudi Ooms recently addressed this issue and described it in his blog post Autopilot Enrollment Fails after Terms of Use. If I understand correctly, CloudExperienceHost (a web app) crashes when the Terms of Use (TOU) have changed.
The error is not caused by the Conditional Access policy or incompatibilities between tenants. The reason is a problem in the JavaScript code of the CloudDomainJoin package. Windows Autopilot downloads this from Microsoft during the OOBE phase and stores it in the local app data of the defaultuser0 profile.
Microsoft can dynamically update the JavaScript package without releasing a Windows update. However, there is a problem: if the forwarding of the terms of use in the current package fails, the registration of a new version of the terms of use will also fail. The error "Something went wrong: You accessed an unexpected page" will appear.
Rudi Ooms analyzed the problem in his blog post and also provides tips on a workaround: Simply accept the Terms of Use (TOS) in advance, or restart the device if the error occurs. Once consent has been registered, the registration will continue successfully.
