OSD progress hidden behind a “Just a moment” screen Windows 10 1709 -> Fix

OSD progress hidden behind a “Just a moment” screen Windows 10 1709 -> Fix

I noticed an issue when deploying Windows 10 1709 via Task-Sequence-> after the first reboot during the step “Setup Windows and Configuration Manager” the machine came back with “Just a moment” and the progress bar was hidden. My task-sequence had no unattend file applied during the capture. I found the solution by creating an unattend file that hide’s Wifi Setup and disabled user and computer OOBE. The step was added during the step “Apply Operating System”:

The XML-File includes the following:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="‪http://schemas.microsoft.com/WMIConfig/2002/State‬" xmlns:xsi="‪http://www.w3.org/2001/XMLSchema-instance‬">
<cpi:offlineImage cpi:source="wim:c:/mount/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

Copy smsts.log automatically on a network share if error in OSD

Target: Copy the smsts.log to a network share during a task-sequence if there is any error in the task-sequence / except the option “Continue on error” is set.

Sometimes it can be hard if you request an smsts.log from a location where you don’t have real IT on side.
You need to know at which step the installation process stopped. During OSD, if the disk is already partitioned, within Windows or before, if it’s a x64 system or x86….

There is the possability to copy the logs automatically to a network share. I exported the example Task-Sequence which can be downloaded here: Download

You only need to copy the .zip file on an network share and import the task-sequence in the ConfigMgr Console.

The example Task-Sequence includes the following steps:

This will do the following if you have an error in the task-sequence.

On the file-share you will have a folder with the device name:

And inside the folder the smsts.log:

All steps more detailed:

In my productive TS all steps are one level / folder under the “Task Sequence” step:


1. Log Capture:

Options of this step:

2. Connect to Network Folder / create a network-share before with everyone at least write access.

3. Create folder on the share for Computer

4. Copy the smsts.log to the share directory

5. Display a Popup that there was an error and you need to check the logs.

Error message during failure in OSD:

I found the source / Idea on the following Blog-Post: https://systemcenterguru.wordpress.com/2013/11/02/capturing-task-sequence-log-files-during-osd-deployment/