SCCM OSD Stuck on “Just a moment…”

We ran into an odd SCCM OSD issue where builds would get roughly halfway through and then hang indefinitely on a “Just a moment…” screen before eventually timing out — with no crash, no obvious error, and nothing conclusive in the usual logs.

The investigation

We went through the standard troubleshooting playbook: hardware diagnostics, network diagnostics, driver checks — all came back clean, and none of it explained why the build would freeze at that exact point every time.

The actual fix

The real cause turned out to be much simpler than any of the diagnostics we’d run: pressing Alt+Tab during the “stuck” screen revealed a hidden error dialog sitting behind it, reporting that a selected role could not be installed as part of the task sequence. Disabling the offending Add Role step in the task sequence resolved the issue completely, and builds completed without any further problems.

Takeaway

If a task sequence appears to hang rather than fail outright, check for a hidden dialog window before assuming it’s a deeper hardware, network, or WinPE issue — task sequence error dialogs can sometimes render behind the main progress screen rather than on top of it, especially during role/feature installation steps, making a genuine error look like a silent freeze.

Still Worth Checking First on Current Configuration Manager (Updated for 2026)

This same “hidden dialog behind the progress screen” behaviour is unchanged on current Configuration Manager (2603) — there’s still no built-in mechanism that surfaces a blocked role/feature-installation error on top of the OSD progress UI, so Alt+Tab remains the fastest way to rule this out before diving into log analysis. If Alt+Tab doesn’t reveal anything, the next place to check is smsts.log itself (typically under X:\Windows\Temp\SMSTSLog during WinPE, or C:\Windows\CCM\Logs\Smstslog once the OS has applied) for the specific step that’s actually stalling.