Welcome. Spinning dots. One minute. Two minutes. The screen is not frozen and Windows is not doing nothing - it is working through a queue, and one item in that queue is taking all the time.
The Welcome screen is the visible tip of the Winlogon stage: Windows loads your profile, applies policy, waits for the network and finishes account checks before it dares show the desktop. When one of those steps stalls - a huge profile, a policy looking for a server that is not there, an online account check on a bad connection - the dots keep spinning honestly, because the work really is still pending. This page decodes which step you are stuck on using three tests that need no tools at all.
The real status lines Windows shows during sign-in. Each line is a different worker doing a different job - which one stays on screen longest names your culprit.
Right after you enter your PIN or password, the User Profile Service loads your profile - the NTUSER.DAT registry hive plus your AppData structure. Group Policy then processes computer and user settings. Network-dependent pieces wait for the connection to be ready. On a Microsoft account sign-in, account verification and sync preparation join the queue. Only when the queue drains does Explorer start and the desktop appear. A stall at Welcome is therefore never random: it is one named worker waiting on something - a file, a server, a network or a service.
Honesty first: after a feature update or a big cumulative update, the first logon legitimately takes minutes. Windows finishes servicing, rebuilds caches and shows Preparing Windows while it works. Give that logon time - interrupting it with a forced power-off can corrupt the very update that was finishing. The problem worth fixing is the logon that is slow every day, on ordinary days, with no update pending. Judge your PC by its normal Tuesday, not by update morning.
Restart, and before signing in, disconnect the network: pull the LAN cable or switch Wi-Fi off from the sign-in screen icon. Then sign in and time the Welcome stage. If the wait collapses, your stall was network-shaped: an account check reaching for Microsoft servers, a policy or drive mapping hunting for a domain server, or a sync service retrying. If nothing changes offline, the queue is stuck on something local - profile or disk - and the network suspects are cleared in one move.
Two more separators. Sign in with a fresh test account: if its Welcome stage is quick, your own profile or account is the heavy item; if it is equally slow, the machine itself is. Then try Safe Mode, which loads a minimal driver and service set: a fast Safe Mode logon points at a third-party service or driver in normal mode, while an equally slow Safe Mode logon points back at the disk or core Windows components.
A Welcome screen that truly never finishes - thirty minutes, no disk activity, no change - is a different fault from a slow one. Do not keep force-restarting into the same wall. Boot into the recovery environment, use System Restore to return to a point before the stall began, and if restore is unavailable, that PC needs the offline repair route rather than logon tuning. Slow is a tuning problem; stuck forever is a repair problem, and mixing the two wastes hours.
The video shows the account-layer fix end to end - if your offline test points at the Microsoft account, this is the exact change to make.
Watch Full VideoOn a healthy SSD system, a few seconds. On a hard drive system, up to about twenty or thirty seconds on an ordinary day is believable. Minutes every day is not normal on any hardware - it means one worker in the queue is waiting on something that eventually times out.
It is loading - or struggling to load - your profile. Usual honest causes: a very large profile, a profile stored on a slow or failing drive, or a roaming profile being copied from a server. The profile-size case in this series shows how to measure and clean it safely.
As a test, completely safe - Windows caches your credentials and signs you in locally. As a daily habit on a Microsoft account it just delays the same checks until the network returns, so treat it as diagnosis: if offline sign-in is fast, fix the account or network cause properly, as the video does by moving to a local account.