Windows: updates, crashes, recovery tools & everyday quirks

Before touching any tool, spend a couple of minutes establishing what actually changed and what "not working" means. This usually points straight at the answer and keeps you from running the wrong fix on the wrong layer.

What changed recently?

Most "it suddenly broke" problems trace to one of a short list: a Windows update, a newly installed program, a driver update, new or moved hardware, or a power event (an outage or an unplugged charger). Windows is a snapshot of its most recent change — so if a problem began right after something, that something is your best first suspect.

Is it one thing, or the whole system?

If a single app misbehaves while everything else is fine, the problem is almost always that app or its settings, not Windows itself. If the whole machine is affected — slow, crashing, or unable to start — you're dealing with a system-level cause: files, drivers, or hardware. Telling these apart saves a lot of wasted effort.

What's happening right now?

Pick the closest match to jump to the right part of the guide. If you'd rather not use the tool, the sections and tables below cover every path — nothing here is only available through the selector.

Updates are how Windows delivers security fixes, new features, and — importantly — driver and component updates that other fixes rely on. That's also why a stuck or failing update feels so much worse than it needs to: a lot of other troubleshooting assumes the system is reasonably current, so a broken update can quietly cause downstream problems.

How updates normally work

Windows downloads updates in the background and installs them, often at a convenient time or on the next restart. "Quiet" updates are fine; the trouble starts when an update stalls partway, fails to install, or — less commonly — installs and then breaks something. Most stuck-update problems are environmental (no space, wrong clock, a corrupted update cache) rather than fatal, which is why the fixes below lean on clearing the environment first.

The safe first steps

1. Restart. A genuine reboot (not sleep) clears a surprising number of stuck updates. If it's stuck installing, let it finish first — interrupting a mid-install is the one thing to avoid.
2. Run the built-in troubleshooter. Settings → System → Troubleshoot → Other troubleshooters → Windows Update. It resets a few of the update services and flags common problems.
3. Check the date and time. Update checks fail if the system clock is off. If it's wrong, fix it (and note that a drifting clock can be a sign of a failing battery on a laptop).
4. Check free disk space. Updates need room to download and stage. A nearly full system drive is a frequent, easy-to-miss cause.

Identifying and removing a problem update

If a specific problem started right after an update, that update is a strong suspect. In Settings → Windows Update → Update history you can see what was installed and, in many cases, uninstall a recent update. Some updates (like cumulative security updates) can't be removed the same way, and removing an update isn't a fix for the underlying cause — but it's a reasonable, reversible step to confirm whether that update was the trigger.

When rolling back is appropriate

If a major (feature) update caused serious problems, Windows offers an option to go back to the previous version. This is time-limited — it's only available for a limited number of days after the upgrade — and it removes apps and updates installed after the upgrade. It's the right call when a big update clearly broke the system; it's not worth reaching for minor issues that a single update-removal or a fresh update cycle would handle.

Resetting the update components (advanced)

Before a major update

Big updates are the ones worth a little preparation. Back up anything important, note the apps you rely on (and any that are unusual or business-critical), make a system restore point, and glance at whether there are known issues with the current update. It takes a few minutes and is the difference between a routine upgrade and a stressful one.

A crash is Windows deliberately stopping the machine to avoid letting a serious error corrupt data or hardware. The blue screen of death (BSOD) is the visible form of that stop, and it always shows a stop code — the single most useful piece of information about what went wrong. Different codes point to different culprits, so there is no one universal fix; the value is in reading the code and working the likely causes in order.

Read the stop code

Note the stop code shown on the blue screen (for example, a code followed by the name of a driver in parentheses). If the machine reboots too fast to read it, you can often find the most recent crash in Event Viewer (under Windows Logs → System, look for the BugCheck source) or in a minidump file under C:\Windows\Minidump. The code and the driver name, if any, tell you whether to suspect a driver, memory, or the disk.

The usual suspects

In rough order of how often they turn out to be the cause: a driver (especially one that just updated, or one for a new device), recently installed software, corrupted system files, and then failing hardware such as RAM or a disk. Overheating and power issues can also surface as crashes, typically under load.

Investigating the crash

Two built-in tools make this concrete. Reliability Monitor shows a timeline of crashes and failures, so you can see exactly when the problem started and whether it lines up with an update or install. Event Viewer holds the detailed system and application logs, where the BugCheck entries name the crash and often the module involved. Together they turn "it crashed" into "it started crashing after Tuesday's driver update," which is a much more actionable statement.

A safe order for crash problems

1. Note the stop code and when the crashes began.
2. Do a clean boot (below) to rule out conflicting software and services.
3. Address the likely driver — roll it back if it was recently updated, or update it if it's old.
4. Check the files with SFC, then DISM.
5. Suspect hardware if the code points to memory or storage, or if crashes persist after the software steps.

If crashes are frequent or the code points to a specific hardware fault, the dedicated blue screen guide goes deeper into reading the dump and testing the hardware.

Windows ships with a family of recovery tools, and the confusion is that they sound alike but do very different things. Some repair the existing install, some roll it back, some reinstall it. Picking the right one — and understanding how much it will touch — is the whole game. Here's the family at a glance, and then each tool in turn.

Repair vs. restore vs. reset vs. reinstall

The pattern to hold onto: repair keeps everything and just fixes it, restore keeps your files but rolls back the system, reset reinstalls (your choice on files), and a clean install wipes the slate. Always work down that list, not up it.

How to reach the recovery environment

Most recovery tools live in the Windows Recovery Environment (WinRE), reached through "Advanced Startup." You can get there several ways: from within Windows via Settings → System → Recovery → Advanced startup → Restart now; by holding Shift while choosing Restart; or, when Windows won't start, by forcing a power-off and on a couple of times so it enters automatic recovery on its own. A recovery USB or Windows install media (choose "Repair your computer") is the fallback when none of the above work.

These are the "check the files and the disk" tools, run from an elevated (administrator) Command Prompt. They're safe, in-place repairs — none of them touch your personal files — and together they cover the two most common system-level causes: corrupted files and a faulty disk. The order matters: fix the files before you dig into the disk, and fix the component store before you expect file repair to fully succeed.

System File Checker (SFC)

SFC scans your current Windows installation and replaces damaged protected system files with healthy copies from the component store. It's the safe first command to run for unexplained crashes, odd behavior, or update failures, and it's non-destructive.

DISM

DISM works a level deeper, repairing the component store that SFC depends on. You run it when SFC says it can't fix something, and then run SFC again so it can use the now-healthy store. It's safe but can be slow, because it may need to download repair files.

CHKDSK

CHKDSK checks a drive's file system and, on request, repairs problems and marks bad sectors. Use it when a disk-level issue is suspected — errors, unexpected unallocated space, or a drive that's acting up. A couple of nuances: on recent Windows versions /scan lets it check the current drive without forcing a reboot; on older systems you may be offered to schedule the check for the next restart (because it needs the volume idle); and /r is the heavier option that also locates bad sectors and recovers readable information.

"Windows won't start" covers several different situations — nothing happens, it powers on but never reaches the desktop, it loops, or it's stuck on the loading screen. The key is to find out how far along the boot process it gets, because that tells you whether the problem is power/hardware, the boot records, a failing disk, or a stuck update or service.

Windows not starting at all

Rule out the physical layer before anything else: is it actually getting power (cable, outlet, a laptop charger that's genuinely charging)? Do the fans spin and the screen light up at all? If there's no sign of life, it's almost certainly power or hardware, not Windows, and the built-in tools won't help until the machine can at least power on. Once it's powering on but not reaching Windows, you move into the recovery path below.

Boot loops and Automatic Repair

If Windows repeatedly restarts and eventually shows the "Automatic Repair" screen, it has tried to fix a startup problem and cycled. That screen is your entry point to Advanced options. Work it in order: Startup Repair first (it's automatic and low risk), then System Restore if a recent change is the likely cause, then Uninstall Updates if a recent update triggered it, and Safe Mode if you suspect a driver or app. Most boot loops resolve at one of these steps.

Stuck on the loading screen

A machine that sits on the spinning-dots loading screen can be a slow or failing disk, a stuck update, or a service that hangs during startup. Give it a real amount of time first — a struggling disk can take several minutes. If it's genuinely stuck, force a power-off and on, and let Windows enter recovery. If it then repeatedly fails, follow the boot-loop path above; if the disk is the suspect, a CHKDSK from the recovery Command Prompt is the relevant tool.

Boot configuration problems

When the boot records themselves are damaged, Windows can't find how to start, and you get errors about a missing or corrupted boot manager. Startup Repair handles many of these automatically and is the right first attempt. If it doesn't, the recovery Command Prompt has the bootrec commands that rebuild the boot records. Because these modify the boot configuration, they're for genuine boot problems — not something to run routinely — and they're explained with their purpose below.

Reaching recovery when you can't get to Windows

If the machine won't reach Windows and the built-in recovery won't engage on its own, you can usually force it: power it off and on, and when you see the Windows logo / spinning dots, force it off (hold the power button) and repeat a couple of times — Windows then enters recovery automatically. A recovery USB or install media with "Repair your computer" is the reliable fallback. From there, all the recovery tools are available.

If the machine won't even power on or won't reach the point of showing a Windows logo at all, the problem is likely below Windows — and if it's a storage device that's not being detected, the hard drive guide is the right next read.

Most of the time a "broken" Windows is really a stuck component, not a broken system. These are the everyday hiccups, each with the quick fix and, where relevant, the deeper one. The common thread: restart the relevant process or reset the specific app before you assume anything bigger is wrong.

Slowness is a symptom, not a cause, so the goal is to find what's actually consuming resources and then address that. Task Manager is the tool that turns "it's slow" into "this process, or this disk, is the problem," and most performance fixes follow from that single observation.

Use Task Manager to find the culprit

Open Task Manager (Ctrl + Shift + Esc) and look at the Processes tab, sorted by the column that matches the complaint: high CPU means something is working hard, high Memory means you're out of RAM headroom, high Disk means something is reading or writing heavily. A single process pinned at 100% on any of these is your starting point. The Performance tab gives the overall picture — how full the CPU, RAM, and disk are, and the disk type (HDD vs SSD), which matters a great deal for speed.

Trim the startup apps

A large share of "slow to get going" comes from too many programs launching at boot. In Task Manager's Startup apps tab (or Settings → Apps → Startup) you can disable the ones you don't need at login. This is one of the safest, highest-value performance fixes there is, because it only affects what auto-starts — not your files or your installed programs.

High disk usage in particular

When disk usage sits near 100%, the cause is often one of: a mechanical HDD (which is simply slow for modern workloads), the Windows Search indexer working, an update installing in the background, or a disk that's starting to fail. An SSD is the single biggest upgrade for an old slow machine. If the disk is the suspect and it's also making noise or dropping out, treat it as a hardware problem — and the hard drive guide covers when a drive is failing.

Quick wins, in order

1. Restart — a real reboot clears a lot of accumulated slowness.
2. Update Windows — performance and stability fixes ship regularly.
3. Trim startup apps — remove what you don't need at login.
4. Check disk space and health — a nearly full or failing drive slows everything.
5. Look for the resource hog in Task Manager and deal with that specific process.

A driver is the small piece of software that lets Windows talk to a piece of hardware, which is also why a bad driver is one of the top causes of crashes and device problems. Device Manager is where you see the state of every device, and where you update, roll back, or disable a driver. The guiding principle: when a device or a crash started after a driver change, the driver is the first thing to look at.

Device Manager

Open Device Manager (run devmgmt.msc, or right-click the Start button and choose it) and expand the categories. A device with a warning icon is telling you there's a problem with its driver. From there you can update the driver (letting Windows search), roll it back to the previous version if a recent update broke it, or disable the device. For a specific device, the manufacturer's own driver from its website is usually the most reliable source — it's worth avoiding generic "driver updater" utilities, which are a common source of new problems.

When a new driver causes trouble

If something broke right after a driver updated (a crash, a device that stopped working, audio or Wi-Fi cutting out), the cleanest fix is to roll that driver back to the previous version in Device Manager. It's reversible and targeted. If rolling back isn't an option, uninstall the driver and let Windows reinstall it, or grab the known-good version from the manufacturer.

Clean boot

A clean boot starts Windows with only the minimum drivers and services, disabling startup programs and third-party services. It's the definitive way to answer "is a piece of software or a driver causing this?" — if the problem disappears in a clean boot, you then re-enable things in groups to find the culprit. You set it up from System Configuration (msconfig): the Services tab (with "Hide all Microsoft services" ticked) and the Startup tab. Remember to reverse it when you're done, or the machine stays in a stripped-down state.

When it's hardware, not software

Some problems are physical: failing RAM, a degrading disk, overheating, or a loose connection. The clues are crashes with memory- or storage-related stop codes, a drive that's noisy or dropping out, or a machine that runs hot and slows down under load. At that point the software tools (SFC, DISM, a clean boot) will have done their job and come up empty, and the next step is testing or replacing the hardware — which is a different kind of work than Windows troubleshooting. If Wi-Fi, Bluetooth, or audio specifically are the victims, the Wi-Fi guide and sound guide cover those paths in detail.

Everything above fits into one order, and the order is the point: light and reversible before heavy and destructive. Follow it top to bottom and stop as soon as the problem is resolved — you rarely need to reach the bottom.

1. Back up anything that matters — or at least before you do anything irreversible.
2. Identify what changed recently, and whether it's one app or the whole system.
3. Do the safe, reversible steps first — a full restart, the right built-in troubleshooter, a clean boot.
4. Check the files with SFC, then DISM; check the disk with CHKDSK if a disk problem is in play.
5. Use the right recovery tool — System Restore for a recent change, Startup Repair for a bad boot, Uninstall updates for a bad update, Safe Mode to remove a bad driver or app.
6. Escalate to a reset only when the system is too damaged to repair.
7. Reinstall only when a reset won't do it.

Reset This PC and a clean install are the two heavy options, and both are recoverable-in-principle but painful-in-practice if you're unprepared. The difference between a smooth reset and a stressful one is almost entirely the preparation. Do this before either.

• Back up your files — documents, photos, and anything you can't re-download, ideally to an external drive or the cloud. A "Keep my files" reset is safer, but a backup is the guarantee.
• Write down your accounts and passwords — especially your Microsoft account, plus any logins you rely on.
• Note your licenses and product keys — for software you purchased, and anything that needs re-activation.
• List the apps you use — so you know what to reinstall, and which ones need a license or an account.
• Capture your network details — Wi-Fi passwords, and any network or printer setup you'd have to redo.

The distinction to keep clear: a reset (Reset This PC) reinstalls Windows from within Windows and can keep your files; a clean install builds Windows fresh from media and removes everything. If the machine is stable enough to run a reset, that's usually the less painful of the two. If it won't stay on long enough, a clean install from media is the reliable route — which makes the backup above the thing that makes it bearable.

The whole method in tickable order — safe and reversible steps first, the file and disk checks in the middle, and the data-safety decision before anything heavy. Ticks are saved in this browser only.