Decide whether setup is actually frozen
Some stages pause while Windows verifies packages, updates components or scans files. Check whether the window still responds, disk activity continues, or another approval dialog is hidden behind it.
Look for Windows approval behind the installer
Use Alt+Tab and inspect the taskbar for User Account Control, Windows Security, or another installer dialog. An all-users installation can wait for elevation while the main progress window appears stuck.
If setup is genuinely unresponsive
- Do not launch several copies of setup.
- Try closing the installer normally first.
- If it is completely unresponsive, end only that installer task rather than unrelated Windows processes.
- Restart Windows before the next attempt.
- Download a fresh official package if the same file repeatedly freezes.
Use the current Install Manager when it matches your version
For current Windows setups, Python recommends Python Install Manager. If your required version is supported and policy allows it, install the manager and let it manage the runtime.
Collect evidence when it stops at the same stage
If every attempt stops at the same feature or percentage, preserve the installer log and note the exact feature name. Repeated failure at one component is much more actionable than “it hangs.”
Managed devices may be delayed or blocked by endpoint policy; escalate the exact log rather than attempting to bypass policy.
Check whether Python is already partially or fully installed
py list
where.exe python
If a runtime exists but behaves inconsistently, move to the broken-installation repair guide.
Rule out a machine that is simply under heavy load
Open Task Manager and check CPU, disk, memory, and whether Windows Update or security scanning is consuming the machine. On a slow disk, a component stage can look frozen while it is still doing work.
If the installer is responsive and the system shows ongoing activity, give the current operation room to finish. If both the installer and system activity remain dead and the same stage repeatedly hangs after a restart, collect logs and move to a targeted failure diagnosis.
Use activity signals instead of guessing from the percentage
Leave the installer alone while any of these are changing: its status text, CPU time in Task Manager, disk activity, temporary files, or a Windows approval window. A progress bar can remain on one percentage while a component is still being verified.
Treat it as genuinely stuck when the window is unresponsive, there is no hidden prompt, the setup process shows no meaningful activity for an extended period, and the state does not change after the PC is no longer under heavy load. There is no honest universal “wait exactly five minutes” rule.
- Do not start a second installer over the first one.
- Do not end Windows Installer or update services at random.
- After a forced close, restart Windows before one controlled retry and record the stage if it freezes again.
Frequently asked questions
How long should I wait?
There is no universal safe duration because hardware, scanning and components differ. Judge responsiveness and activity, not only the progress percentage.
Can I force-close setup?
If it is truly unresponsive and normal close fails, ending that installer may be necessary. Restart Windows before retrying.
Why does it freeze at the same point?
A repeatable stop suggests a component, permission, policy or system prerequisite; the log is the next evidence.
Related Python fixes
Continue with the page that matches the symptom you see after this step.
References
Installation behavior and commands were checked against current Python documentation on 10 August 2026.