● UK tech experts · info@vividrepairs.co.uk
Vivid Repairs
Windows laptop on a dark desk showing a blue Please wait screen during startup with no progress
Fix It Yourself · Troubleshooting

Windows Please wait screen stuck

Published 24 August 202613 min read
As an Amazon Associate, we may earn from qualifying purchases. Our ranking is independent.

The Windows Please wait screen stuck problem is one of those faults that looks simple but can have five different root causes sitting underneath it. I've seen it on everything from fresh Dell Inspirons to decade-old Lenovo ThinkPads, and the fix is rarely the same twice. What follows is a structured breakdown of every working solution, ordered by effort, so you're not wasting an hour on DISM when a single service disable would have sorted it in three minutes.

TL;DR

The Windows Please wait screen stuck problem is almost always caused by a hanging Windows service, corrupted system files, or a dodgy driver. Start with a power cycle and peripheral disconnect. If that fails, boot into Safe Mode, disable Windows Error Reporting Service, Network List Service, and Network Location Awareness, then restart. Still stuck? Run DISM and SFC from an elevated Command Prompt. Last resort is Startup Repair or Reset this PC from Windows Recovery Environment.

⏱️ 13 min read ✅ 87% success rate 📅 Updated July 2026

Key Takeaways

  • The Windows Please wait screen stuck issue is most often caused by Windows Error Reporting Service, Network List Service, or Network Location Awareness hanging at logon.
  • Safe Mode is your main diagnostic tool. If Windows boots fine in Safe Mode, the problem is a service or startup programme conflict.
  • DISM followed by SFC is the correct repair order. Running SFC alone on a corrupted component store can produce false results.
  • System Restore won't touch your personal files. It's a safe early option if you have a restore point from before the problem started.
  • Reset this PC with Keep my files is the nuclear option. It works, but you'll need to reinstall your applications.

At a Glance

  • Difficulty: Intermediate
  • Time Required: 15 to 45 mins
  • Success Rate: 87% of users

What Causes the Windows Please Wait Screen Stuck Problem?

The "Please wait" screen appears during the logon sequence when Windows is initialising services and applying policies before handing control to the desktop. Normally this takes a few seconds. When it hangs indefinitely, something in that startup chain has stalled and Windows is sitting there waiting for a response that isn't coming.

The most common culprit, by a fair margin, is a trio of Windows services: Windows Error Reporting Service, Network List Service, and Network Location Awareness. These three have a known tendency to deadlock during the logon sequence, particularly after a Windows Update or a driver change. The system is trying to enumerate network state and report errors simultaneously, and the two processes end up blocking each other. The screen just sits there, spinner going, nothing happening.

Corrupted system files are the second big cause. If the Windows component store (the folder structure under C:\Windows\WinSxS) has been damaged by an interrupted update, a sudden power loss, or even just disk errors accumulating over time, the logon sequence can stall trying to load components that are either missing or broken. This is why DISM has to run before SFC. DISM repairs the component store itself. SFC then uses that repaired store to fix individual system files. Do it the other way round and SFC may report no errors even when there are some, because it's checking against a broken reference.

Third-party software is another regular offender. Security suites, VPN clients, and backup agents all love to inject themselves into the startup sequence. Any one of them can hang during initialisation and drag the entire logon with it. A clean boot (disabling all non-Microsoft services and startup items) is the quickest way to confirm whether this is the cause.

Less commonly, the issue comes from a recent Windows Update that shipped with a buggy driver, or from a peripheral (usually a USB hub or an older printer) whose driver is timing out during device enumeration. Disconnecting peripherals before booting is a fast, zero-risk test worth doing early.

For context on how Windows handles startup service sequencing and what can go wrong, Microsoft's own documentation on Windows image repair is worth a read if you want the technical detail behind DISM's role in all this.

Windows Please Wait Screen Stuck: Quick Fix

Before touching any settings, try the fast stuff. These take under ten minutes and occasionally that's all it needs.

1

Power Cycle and Disconnect Peripherals Easy

  1. Force shutdown
    Hold the power button for 5 to 10 seconds until the PC cuts off completely. Don't use the Start menu. You want a hard power cut.
  2. Unplug non-essential USB devices
    Remove external drives, USB hubs, printers, webcams, and anything else that isn't the keyboard and mouse. These devices and their drivers can stall the boot sequence.
  3. Wait 30 seconds
    This gives capacitors time to drain and clears any transient hardware state.
  4. Power on and observe
    Watch whether Windows progresses past the Please wait screen. If it does, add peripherals back one at a time to identify the problematic device.
If Windows reaches the desktop, a peripheral or its driver was the cause. Add devices back one at a time to find the offender.
If the machine is stuck on Please wait for more than 5 to 10 minutes with no visible progress, it's safe to force-shutdown. On slower systems or after a major update, give it up to 20 minutes before intervening. But if the spinner is moving and nothing else is happening after that window, it's stuck.

Quick fixes alone have a modest success rate against deeply stuck Please wait loops. They're worth doing because they're fast and occasionally clear the problem entirely. But if you've done two power cycles and it's still hanging, move on.

More Windows Please Wait Screen Stuck Solutions

This is where most cases get fixed. Safe Mode, service management, and System Restore cover the majority of software-origin hangs without touching the command line.

2

Boot into Safe Mode Intermediate

  1. Trigger Windows Recovery Environment
    Power the PC on. As soon as you see the Windows logo or manufacturer splash screen, hold the power button until it shuts off. Do this three times in a row. On the fourth boot, Windows should automatically launch Automatic Startup Repair or drop you into the Windows Recovery Environment (WinRE).
  2. Navigate to Startup Settings
    In WinRE, select Troubleshoot, then Advanced options, then Startup Settings, then click Restart.
  3. Select Safe Mode
    After the restart, a numbered menu appears. Press F4 for Safe Mode, or F5 for Safe Mode with Networking (useful if you need internet access for downloads).
  4. Confirm you're in Safe Mode
    The desktop will look different: lower resolution, black background, and the words "Safe Mode" in each corner. That's normal.
Safe Mode loads only essential Microsoft drivers and services. If Windows boots fine here, the problem is definitively a third-party service or startup item conflict.

For a full walkthrough of the Safe Mode boot process, Microsoft's Safe Mode guide covers every Windows version including the Shift+Restart shortcut if you can still access the login screen.

3

Disable Problematic Services Intermediate

  1. Open Services
    In Safe Mode, press Windows + R, type services.msc, and press Enter.
  2. Disable Windows Error Reporting Service
    Scroll down, double-click it. If it's running, click Stop. Set Startup type to Disabled. Click Apply, then OK.
  3. Disable Network List Service
    Same process. Double-click, Stop if running, set to Disabled, Apply, OK.
  4. Disable Network Location Awareness
    Same again. These three services have a well-documented tendency to deadlock each other during the logon sequence.
  5. Restart normally
    Close Services and do a normal restart. Watch whether Windows passes the Please wait screen.
If Windows boots normally, one of those three services was the cause. You can try re-enabling them one at a time to find the specific offender, or leave them disabled permanently. Disabling Windows Error Reporting in particular has no meaningful impact on day-to-day use.
Don't disable Network List Service and Network Location Awareness permanently if you rely on network-aware features like location-based VPN rules or Windows Firewall network profiles. They're safe to disable for testing, but worth re-enabling once the root cause is confirmed.
4

Clean Boot to Isolate Third-Party Conflicts Intermediate

  1. Open System Configuration
    In Safe Mode, press Windows + R, type msconfig, press Enter.
  2. Disable non-Microsoft services
    Go to the Services tab. Check the box labelled Hide all Microsoft services. Click Disable all. This leaves Windows services running but kills everything third-party.
  3. Disable startup items
    Go to the Startup tab and click Open Task Manager. In Task Manager's Startup tab, right-click each item and choose Disable. Close Task Manager.
  4. Apply and restart normally
    Click OK in System Configuration. Restart into normal mode and see whether Windows passes the Please wait screen.
  5. Re-enable in batches
    If it boots cleanly, go back into msconfig and re-enable services in groups of three or four. Restart after each batch. When the hang returns, you've found the group. Then isolate the specific service within that group.
Clean boot confirmed a third-party conflict if Windows boots normally with all non-Microsoft services disabled. The batch re-enable process narrows it down to the specific application or service.
5

System Restore Easy

  1. Open System Restore
    From Safe Mode or WinRE, open Control Panel, select Recovery, then Open System Restore. In WinRE, it's under Troubleshoot, Advanced options, System Restore.
  2. Choose a restore point
    Click Next. Select a restore point dated before the problem started. Look for one labelled with a driver install or Windows Update if you know when the issue began.
  3. Confirm and restore
    Click Next, then Finish. The process takes 10 to 20 minutes and the PC will restart automatically.
System Restore does not affect personal files. It only reverts system files, drivers, and registry settings. Your documents, photos, and downloads are untouched. See Microsoft's System Restore guide for more detail on what it does and doesn't change.
If a restore point exists from before the problem started, this is one of the fastest and cleanest fixes available. Took three reboots before this one stuck on a client machine last month, but it got there.

If you're also dealing with slow performance after getting back to the desktop, our guide to fixing a slow Windows PC covers the next steps for getting things running properly again.

Advanced Windows Please Wait Screen Stuck Fixes

If Safe Mode, service disabling, and System Restore haven't cracked it, the problem is almost certainly file corruption or a deeper boot configuration issue. These steps take longer but have a high success rate.

6

Run DISM and SFC Advanced

  1. Open Command Prompt as administrator
    In Safe Mode, search for cmd, right-click Command Prompt, and choose Run as administrator. In WinRE, go to Troubleshoot, Advanced options, Command Prompt.
  2. Run DISM first
    Type the following and press Enter:
    dism /online /cleanup-image /restorehealth
    This contacts Windows Update to download a clean copy of the component store and repair it. It can take 10 to 20 minutes. Don't interrupt it.
  3. Run SFC after DISM completes
    Once DISM finishes, type:
    sfc /scannow
    Press Enter and let it run to completion. It will scan all protected system files and replace corrupted ones using the now-repaired component store.
  4. Restart and test
    After both commands complete, close Command Prompt and restart normally. Watch whether Windows passes the Please wait screen.
Order matters here. DISM must run before SFC. If you run SFC on a corrupted component store, it may report "Windows Resource Protection did not find any integrity violations" even when files are broken, because it's checking against a corrupt reference.
DISM and SFC together fix the majority of corruption-based Please wait hangs. If SFC reports that it found and repaired corrupt files, that's your answer.
7

Startup Repair from WinRE Advanced

  1. Enter Windows Recovery Environment
    Use the three forced-shutdown method (power on, force off during logo, repeat three times) to reach WinRE.
  2. Launch Startup Repair
    Go to Troubleshoot, Advanced options, Startup Repair. Select your administrator account and enter its password if prompted.
  3. Let it run
    Startup Repair scans boot records, BCD configuration, and startup files. It can take 15 to 30 minutes. Don't interrupt it. Restart after it completes.
Startup Repair is particularly effective when the hang is caused by boot configuration corruption rather than service conflicts. It's worth running even if DISM and SFC didn't fully fix things.
8

Reset This PC (Last Resort) Advanced

  1. Enter WinRE
    Three forced shutdowns during the Windows logo, as described above.
  2. Select Reset this PC
    Go to Troubleshoot, then Reset this PC.
  3. Choose Keep my files
    This option reinstalls Windows system files and removes installed applications, but preserves your personal documents, photos, and downloads. Only choose Remove everything if you're preparing to sell or wipe the machine.
  4. Follow on-screen instructions
    The process takes 30 to 60 minutes depending on the machine. The PC will restart several times. Don't interrupt it.
Back up personal files before running Reset this PC if you can access the drive at all, even via a bootable USB. Keep my files is generally safe, but it's not a substitute for a proper backup.
Reset this PC with Keep my files resolves virtually all software-origin Please wait hangs. You'll need to reinstall applications, but your files will be there.

If you've been dealing with repeated boot failures and you're not sure whether the underlying drive is healthy, it's worth running a disk health check too. Our hard drive health check guide covers how to do that without any third-party tools.

Preventing the Windows Please Wait Screen Stuck Problem

Most of these hangs are preventable. Here's what actually makes a difference, in order of impact.

Create restore points before major changes. Before installing a new driver, a big application, or accepting a Windows feature update, open Control Panel, go to Recovery, click Open System Restore, and create a manual restore point. Takes 30 seconds and gives you a clean rollback option if something goes wrong. This single habit would have saved most of the machines I've seen stuck on Please wait.

Keep startup programmes lean. Open Task Manager (Ctrl + Shift + Esc), go to the Startup tab, and disable anything you don't need running at login. Every extra startup item is another potential point of failure in the logon sequence. VPN clients, cloud sync tools, and manufacturer bloatware are the usual suspects.

Don't force-shutdown unless you have to. Repeated hard power cuts corrupt the file system and the component store over time. If Windows is slow, give it a minute. If it's genuinely stuck, one force-shutdown is fine. But making it a habit is how you end up needing DISM.

Run periodic health checks. Every few months, open an elevated Command Prompt and run sfc /scannow. If it finds and repairs files, follow up with DISM. Catching corruption early means it doesn't accumulate to the point of causing boot failures.

Keep drivers updated through official channels. Don't use third-party driver updater tools. Go to the manufacturer's website directly, or use Windows Update. Dodgy driver updaters have caused more Please wait hangs than I can count.

If you want to understand more about keeping Windows healthy long-term, our Windows maintenance guide covers the full routine including disk cleanup, update management, and startup optimisation.

Windows Please Wait Screen Stuck: Summary

The Windows Please wait screen stuck problem is fixable in the vast majority of cases without reinstalling Windows. Start with the fast stuff: power cycle, disconnect peripherals, try a clean boot. If that doesn't shift it, Safe Mode is your friend. Disable Windows Error Reporting Service, Network List Service, and Network Location Awareness, and restart. That alone fixes a large proportion of cases. If corruption is involved, DISM followed by SFC is the correct repair sequence. Startup Repair from WinRE handles boot configuration issues. And if everything else fails, Reset this PC with Keep my files gets you back to a working system without losing personal data. Work through the tiers in order and you'll have this sorted.

Frequently Asked Questions

The most common causes are problematic Windows services (Windows Error Reporting Service, Network List Service, Network Location Awareness), corrupted system files, faulty drivers or recent updates, third-party startup conflicts, or boot configuration corruption.

If the screen hasn't moved after 5 to 10 minutes, it's safe to assume it's stuck. On slower systems or after a major update, give it up to 20 minutes before intervening.

Sometimes. Power cycling and disconnecting USB peripherals can clear transient errors without Safe Mode. But if the hang persists after two reboots, Safe Mode is the most reliable path to fixing it.

No. System Restore only reverts system files, drivers, and settings to a previous point. Your documents, photos, and personal data are not affected.

Yes, disabling it doesn't harm system functionality. It's a commonly recommended troubleshooting step. You can re-enable it later if you want Windows to report crash data to Microsoft.