A user is logged off at the “Now we can go look for any updates” message

You deploy a custom image by using Sysprep.exe and an Unattend.xml answer file that contains the SkipMachineOobe or SkipUserOobe tag.

When users log on, they see the following message, and then they are logged off: 

If users then try to log on again, they can complete the first-time logon process, and they don't see the problem recur.

This problem occurs because the SkipMachineOobe and SkipUserOobe tags are no longer supported. Using these tags is known to cause this problem in Windows 10 Version 1709.

To fix this problem, remove the SkipMachineOobe and SkipUserOobe tags from the Unattend.xml file, and then redeploy the image.

There is currently no method to suppress either the "Now we can go look for any updates" message or the search itself.

For more information, see the “Edit the Unattend.xml file for Windows 10 Enterprise” section of the “Create a Windows 10 reference image” topic on the Windows IT Pro Center website.