If Windows setup stays on Getting ready for roughly 30 to 60 minutes, treat it as stuck. Getting ready means Windows Setup is still finishing installation tasks, but it may also be paused by attached hardware, update activity, or a disk problem. First disconnect flash drives, external drives, docks, and other non-essential USB hardware, then restart and try again before blaming an update or a failing drive. Ignoring it can leave you with a half-finished install, repeat reboot loops, or a repair job that gets harder each attempt. This guide helps you tell a normal pause from a peripheral, update, or hardware fault and pick the safest next step.

Triage table

symptom pattern likely cause safest next action when to stop waiting
Clean install on Windows 10 or 11 sits on Getting ready before the first desktop appears Setup is finalizing files, partitioning, or drivers; less commonly, boot media or USB conflicts Wait if the drive light still flashes, then unplug non-essential USB devices and retry setup After 2-3 hours with no screen change
Upgrade after a reboot shows “Getting Windows Ready. Don’t turn off your computer” Windows Update is finishing a monthly cumulative update or feature update Leave it alone first; if frozen past the limit, restart into recovery and use Startup Repair When the screen is unchanged for more than 2 hours
Windows 10 or Windows 11 setup loops back to the same screen after each restart Unfinished updates, damaged system files, or a bad driver state Disconnect peripherals, then run Startup Repair from recovery media When the same screen returns twice in a row
Setup hangs only when an external SSD, USB drive, or extra internal disk is attached USB/media conflict or a multi-drive boot conflict Unplug all non-essential drives and boot from only the installer media Immediately after the first failed attempt
Setup gets stuck after a forced restart, disk light stops, or files seem damaged Disk errors, insufficient free space, or corrupted system files Boot recovery media, then run SFC and DISM from recovery tools if available When the screen does not change for 2-3 hours

What the screen usually means

What the screen usually means
Windows 11 setup screen shows the ready-to-install step

Getting ready can be normal for a while during a clean install, reinstall, or post-reboot setup phase. Windows Setup is still finishing file copy, hardware detection, or account and language setup. On Windows 10 and Windows 11, the same pause can also happen while Windows Update completes a large change in the background.

Normal completion during setup

Short pauses are common after a reboot or when Windows Setup is preparing partition changes. A security update often takes 5-30 minutes, a monthly cumulative update usually takes 15-60 minutes, and a major feature update can take 30 minutes to 2 hours. Those windows are not guarantees, but they are a useful baseline.

Suppose a 512 GB SSD is finishing a clean reinstall and the screen sits still for 45 minutes, but the drive activity light keeps blinking. That can still be normal. The same pause on a machine with a black screen, no disk activity, and no fan or LED change is more suspicious.

Signs the process may be frozen

It is more likely frozen when the message never changes, the drive light stops, and nothing happens after multiple hours. Many support guides use 2 to 3 hours as the point to stop waiting and start troubleshooting.

A common first-time mistake is forcing repeated restarts before checking what is attached. If a USB flash drive, external hard drive, or extra internal disk is confusing the boot path, the same screen can return forever until those devices are removed.

How long should you wait?

Wait long enough to cover the normal finish time for the type of setup, but not so long that you miss a real stall. For a small update, 30 to 60 minutes is a reasonable wait. For a large feature update, about 2 to 3 hours is the outer edge many support guides use before canceling or troubleshooting.

Short waits that are usually safe

If this is a post-reboot update and the message is the standard “Getting Windows Ready. Don’t turn off your computer”, give it time before touching anything. That screen can appear while Windows 10 or Windows 11 is finalizing an update loop, unpacking files, or rolling settings forward.

When a longer wait is still reasonable

Keep waiting if you can still see signs of activity, such as blinking storage LEDs, occasional fan changes, or progress that has only slowed. Unplugging a USB drive can let the installer continue when the stall is caused by attached hardware rather than setup itself. Peripheral checks matter before panic.

When to stop waiting and troubleshoot

Stop waiting if the screen has not changed for about 2 to 3 hours, the device has restarted into the same place more than once, or you cannot boot back into a working desktop. At that point, the safest next step is a clean disconnect of peripherals, then recovery tools rather than random restart cycles.

Likely causes, ranked

Most often, the culprit is not the installer itself. Peripheral conflicts come first, then unfinished Windows Update activity, then damaged system files, then disk or hardware faults. Those causes can overlap, especially on multi-drive systems or older machines with slow HDDs and external storage attached.

Peripherals and USB boot conflicts

USB drives, external hard drives, docks, card readers, and even extra internal disks can confuse Windows Setup. That points to device detection, not a dead installer.

Use this first when the hang starts right after booting the installer, or when the machine has multiple drives attached. The fewer devices connected, the fewer chances Windows has to pick the wrong boot or target disk.

Unfinished Windows Update activity

Windows Update can hold the system on this screen after monthly cumulative updates or major feature updates. It can also get stuck in an update loop, where the same stage repeats after reboot. That is common after a forced shutdown during setup or after a failed update attempt.

When setup is stuck after an update-heavy reboot, the recovery path matters more than another normal restart. Startup Repair is the first tool to try because it targets boot recovery after a failed setup or forced shutdown.

Corrupted system files

Damaged files can keep setup from moving past the same stage, especially if Windows was already unstable before the reinstall or upgrade. SFC and DISM are the standard pair here. SFC checks protected system files, and DISM repairs the Windows image first so SFC has a clean base.

If Windows can still boot to the desktop or Safe Mode, that pair is worth running before deeper repair. If it cannot boot, use recovery media first, then run the commands from the recovery Command Prompt if available.

Disk, storage, or hardware faults

Insufficient free space, disk errors, failing storage, and slow HDD behavior can all stall setup. A slow mechanical drive may take much longer than an SSD, and a nearly full system disk can leave Setup with nowhere to stage files. Multi-drive layouts can make the wrong disk look like the right one.

If setup only fails when an external SSD or second internal drive is present, treat it like a device conflict first. If it fails even with a single target disk attached, storage health rises on the list.

Should you unplug USB devices?

Yes. If Windows setup is stuck on Getting ready, unplug every non-essential USB device before retrying. That includes flash drives, external hard drives, docks, printers, controllers, and spare card readers. Keep only the installer media, keyboard, and mouse attached until the setup passes the stuck point.

Remove external drives and non-essential hardware

  1. Shut down the PC.
  2. Unplug all external drives, docks, adapters, and USB storage.
  3. Disconnect any extra internal drive only if the system is easy to open and you already know which disk is the target.
  4. Start the PC and retry Windows Setup from the same install media.

Retry setup with the fewest devices attached

  1. Leave only one monitor, one keyboard, one mouse, and the installer USB connected.
  2. Enter the boot menu and choose the installer device directly.
  3. Allow the same Getting ready screen to run for up to 2-3 hours if this is a feature update.
  4. If it moves forward, reconnect devices one at a time after the desktop loads.

Check multi-drive systems and external SSDs

  1. Open BIOS or UEFI setup and confirm the correct boot disk order.
  2. Disconnect external SSDs before retrying a clean install or reinstall.
  3. If the wrong disk is selected in Setup, go back and choose the intended target disk carefully.
  4. If the hang returns only with one specific drive attached, that drive is the leading suspect.

Can updates or system files block setup?

Can updates or system files block setup?
Windows Update screen shows available updates and a download button

Yes. A bad update state or corrupted system files can leave Windows 10 or Windows 11 sitting on the same screen. The safest next move is recovery, not blind restarts. Use Startup Repair first if the machine will not progress, then try Safe Mode, SFC, and DISM if Windows can reach them.

Use Startup Repair after a forced shutdown

  1. Force the PC off, then boot from Windows installation media or recovery media.
  2. Select Repair your computer > Troubleshoot > Advanced options > Startup Repair.
  3. Let it complete once before choosing anything else.
  4. If it fails, return to Advanced options and continue with the next recovery step.

Check Safe Mode if Windows can boot

  1. Open Settings > System > Recovery > Advanced startup.
  2. Select Restart now.
  3. Go to Troubleshoot > Advanced options > Startup Settings > Restart.
  4. Choose Safe Mode, then remove recent drivers or update changes from Device Manager or Windows Update.

Run SFC and DISM when files may be damaged

  1. Open Command Prompt as administrator, or use Command Prompt from recovery media.
  2. Run sfc /scannow.
  3. Then run DISM /Online /Cleanup-Image /RestoreHealth.
  4. Restart and check whether setup passes the same screen.

Roll back or clear a bad update when available

  1. Open Settings > Windows Update > Update history.
  2. Select Uninstall updates if a recent update preceded the hang.
  3. If the system is still stuck, use Recovery > Advanced startup and return to the update or repair tools.
  4. For repeated update failures, use Microsoft’s Troubleshoot problems updating Windows path from recovery or support.

When to suspect storage or hardware

Suspect storage or hardware when the problem persists after all peripherals are removed and the update path has been ruled out. That includes repeated hangs on the same disk, unusually slow progress on an aging HDD, or failures that return after disk-related recovery tools. At that point, the install media may be fine while the target system is not.

Not enough free space

  1. Boot into Windows, Safe Mode, or recovery media if possible.
  2. Check the target drive in File Explorer or Disk Management.
  3. Free space on the system partition before retrying setup.
  4. If the machine cannot boot, use recovery tools to remove large temporary files or back up data first.

Disk errors or failing storage

  1. Open an elevated Command Prompt.
  2. Run chkdsk C: /f if Windows can boot, or use recovery command prompt if it cannot.
  3. Run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth if the OS is reachable.
  4. If errors keep returning, back up files and replace the drive.

Slow HDD versus SSD timing

  1. Check whether the target disk is a spinning HDD or SSD in Task Manager > Performance or Disk Management.
  2. Give HDD-based installs the full 2-3 hour window before declaring a freeze.
  3. Use the same installer on an SSD if possible to compare behavior.
  4. If only the HDD path fails, storage speed or wear is likely involved.

If that didn't work, try this next

  1. Back up anything you can still reach from recovery or another PC.
  2. Use recovery media to run Startup Repair again.
  3. Retry the install with only one target drive attached.
  4. If the drive still stalls, replace the storage or ask the PC maker for service options.

Before a major update or reinstall, unplug extra storage and leave only the boot drive attached. That removes one of the most common causes of repeat stalls.

Keep reading

Frequently asked questions

Why is Windows install stuck at getting ready?

Most often, Windows Setup is waiting on hardware detection, finishing an update, or dealing with a device conflict. If the screen has not changed for more than 2 hours, unplug non-essential USB devices, then retry. If that fails, move to Startup Repair or file repair.

How long should getting ready take before I troubleshoot?

For a security update, 5-30 minutes is common. For a monthly cumulative update, 15-60 minutes is common. For a major feature update, 30 minutes to 2 hours is common. If nothing changes after 2-3 hours, stop waiting and start troubleshooting.

Should I unplug USB devices if Windows setup is stuck on getting ready?

Yes. Disconnect flash drives, external hard drives, docks, and other non-essential hardware before retrying. Keep only the installer, keyboard, and mouse attached.

Can a bad update or corrupted system files cause getting ready to hang?

Yes. An unfinished Windows Update, especially a monthly cumulative update or feature update, can leave the system on the same screen. Corrupted files can do the same. If Windows can boot, run sfc /scannow and then DISM /Online /Cleanup-Image /RestoreHealth.

What should I try first if Windows 11 install is stuck at getting ready?

Start with peripherals. Shut down, unplug external drives and USB storage, then boot again with only the installer, keyboard, and mouse attached. If it is an update-related stall, wait up to 2-3 hours total before using Startup Repair from recovery media.

Can storage or hardware issues cause Windows setup to freeze on getting ready?

Yes. Low free space, disk errors, a failing drive, and very slow HDDs can all slow or stop setup. If the problem disappears when an external SSD or extra drive is removed, that points to device or boot-path conflict. If it stays, inspect the target disk next.