Windows 11 Safe Mode: How to Start It 6 Ways, What to Do Inside, and How to Exit or Fix Stuck in Safe Mode

What Windows 11 safe mode is and when you actually need it

Safe mode is a special way of starting Windows that loads only the essential drivers and services, so a crashing driver, a broken update or stubborn malware cannot get in the way. If your PC crashes, freezes, shows a blue screen or will not behave normally, safe mode is the first diagnostic step a technician takes. It does not delete anything, and it does not fix anything by itself. It gives you a quiet, stripped-down Windows in which repairs become possible.

Microsoft describes safe mode as starting Windows in a basic state, using a limited set of files and drivers. In practice that means a low-resolution desktop, no wallpaper, no third-party startup programs, a generic display driver instead of your graphics card driver, and, in the plain version, no internet. The words "Safe Mode" appear in the corners of the screen so you always know where you are.

Think of it as the difference between a crowded workshop and an empty one. If your problem disappears in the empty workshop, the cause is something that is normally loaded: a driver, a startup app, a security tool, a recent update. If the problem remains even there, you are looking at Windows files, the disk or hardware. That single test narrows a hundred possible causes down to two groups, and it is the reason this guide exists.

Symptoms that call for safe mode

• Blue screen loops after a driver or Windows update (see our blue screen guide for the stop codes).
• Black screen or flickering after installing a graphics driver.
• The PC freezes a few seconds after sign-in, which often points to a startup program or service.
• A program or driver cannot be uninstalled in normal mode because it is in use.
• Suspected malware or adware that comes back every time you remove it.
• A bad Windows update that you want to remove (see Windows will not boot after an update).
• Constant crashes that started right after installing new hardware or software.

When safe mode is not the answer

Safe mode will not repair a failing hard drive, a dead battery, a bad RAM stick, a forgotten password or a locked account. It also does not help if the problem is only a slow computer; for that, our slow computer guide is the better tool. And if Windows cannot even reach the sign-in screen, you will need the recovery routes later in this guide rather than the menu-based ones.

The three kinds of safe mode, and which one to pick

Windows 11 offers three flavours: Safe Mode (key 4 or F4), Safe Mode with Networking (key 5 or F5) and Safe Mode with Command Prompt (key 6 or F6). Pick plain safe mode for repairs on the machine, networking when you must download something, and command prompt when the desktop itself is the thing that is broken.

One detail catches many people: Wi-Fi is often unavailable in plain safe mode with networking on laptops, depending on the driver. If you plan to download something, plug in an Ethernet cable or tether a phone by USB. We note this again in the troubleshooting section.

Two other startup options on the same menu

The Startup Settings screen also contains Disable driver signature enforcement (option 7), Disable early launch anti-malware protection (option 8) and Disable automatic restart after failure (option 9). Option 9 is the hidden gem: when a PC reboots so fast after a blue screen that you cannot read the error, this setting makes it stop and show the code. Leave options 7 and 8 alone unless a technician tells you otherwise, because they lower security.

Which method should you use? A decision table

If Windows still reaches the sign-in screen, use Shift plus Restart. If it reaches the desktop and you can open Settings, use Settings, System, Recovery. If Windows will not start at all, interrupt the boot three times to enter the recovery environment, or boot from a Windows USB. The table below matches your situation to the method with the fewest steps and the lowest risk.

Method 1: Shift plus Restart (works from the sign-in screen)

Hold the Shift key while you click Restart, and Windows opens the blue recovery menu instead of restarting normally. From there, Troubleshoot, Advanced options, Startup Settings, Restart, and then the 4, 5 or 6 key takes you into safe mode. This is the most reliable method for most people because it works even when you cannot sign in.

1. On the sign-in screen, click the Power icon in the lower right corner. If you are already on the desktop, open the Start menu and click Power.
2. Hold down Shift and, while still holding it, click Restart. Keep holding until the blue "Please wait" or "Choose an option" screen appears.
3. Choose Troubleshoot.
4. Choose Advanced options.
5. Choose Startup Settings. If you do not see it, click "See more recovery options" first.
6. Click Restart. The PC restarts to a numbered list.
7. Press 4 or F4 for Safe Mode, 5 or F5 for Safe Mode with Networking, 6 or F6 for Safe Mode with Command Prompt.
8. Sign in with an account that has a password. Remember that PINs often fail in safe mode.

If the list does not appear, the "Startup Settings" tile may be missing because the recovery environment is disabled or damaged; jump to Method 5. If a BitLocker screen appears after step 6, type your recovery key and continue.

shutdown /r /o /t 0

Method 2: Settings, System, Recovery, Advanced startup

If you can reach the desktop and open Settings, go to System, then Recovery, click Restart now next to Advanced startup, and follow the same Troubleshoot, Advanced options, Startup Settings, Restart path. It is the same destination as Method 1 with friendlier signposts, which makes it the better choice for less technical users or when you are guiding someone over the phone.

1. Press Windows + I to open Settings.
2. Select System, then scroll to Recovery.
3. Next to Advanced startup, click Restart now. Save your work first: Windows asks you to confirm, and then restarts.
4. On the blue screen choose Troubleshoot, Advanced options, Startup Settings and Restart.
5. Press 4, 5 or 6.

The menu layout in Settings has moved between Windows 11 releases, so if you cannot find Recovery, use the search box at the top of Settings and type "advanced startup". Work or school PCs sometimes hide this button through policy; in that case ask your IT administrator or use the Shift route.

What you should see once you are in

A successful safe mode boot shows a black or dark desktop with the words "Safe Mode" in all four corners, large icons, a low resolution and no wallpaper. The system tray is sparse and the Start menu may look basic. Do not worry about the odd appearance; this is the generic display driver at work. If your screen shows only a cursor on a black background, you probably chose option 6 (command prompt), which is normal for that variant.

Method 3: msconfig Boot tab (and why it is the one that traps people)

Press Windows + R, type msconfig, open the Boot tab, tick Safe boot with Minimal selected, click OK and restart. Windows will boot into safe mode every time until you untick the box, which is both its advantage and its main danger. This is exactly the setting that causes most "stuck in safe mode" calls.

1. Press Windows + R, type msconfig and press Enter.
2. Open the Boot tab.
3. Under Boot options, tick Safe boot.
4. Choose one of the four sub-options:
   • Minimal: normal safe mode (the one you almost always want).
   • Alternate shell: safe mode with command prompt.
   • Active Directory repair: for domain controllers, ignore on home PCs.
   • Network: safe mode with networking.
5. Click Apply, then OK, and choose Restart.

The big advantage of msconfig is repeatability. A technician testing a driver may need three reboots in safe mode, and msconfig avoids repeating the blue menu each time. The big risk is forgetting to reverse it. We recommend a sticky note on the monitor, or better, a calendar reminder, if you use msconfig on a PC that is not yours. The reverse is just as easy: reopen msconfig, clear Safe boot, click OK and restart. Microsoft documents this reversal on its own safe mode page.

Method 1 versus Method 3 in one sentence

Startup Settings (Methods 1 and 2) applies to one boot only, so it cannot trap you. msconfig (Method 3) is persistent, so it can. Pick the one-shot method unless you really need several safe-mode reboots in a row.

Method 4: interrupt the boot three times to reach the recovery environment (Windows will not start)

If Windows cannot reach the sign-in screen, power the PC off with the power button while the logo or spinning dots are showing, repeat this two or three times, and Windows normally opens Automatic Repair and its recovery menu on the next start. From there, Advanced options leads to Startup Settings and safe mode. The exact behaviour depends on the manufacturer's firmware, so treat the count as a rule of thumb rather than a promise.

1. Start the PC. As soon as you see the manufacturer logo and the spinning dots under it, hold the power button for about 5 seconds until it shuts off.
2. Repeat. On the second or third attempt, Windows should show Preparing Automatic Repair and then Automatic Repair or Recovery.
3. Choose Advanced options (or "See advanced repair options").
4. Choose Troubleshoot, then Advanced options, then Startup Settings, then Restart.
5. Press 4, 5 or 6.

Two cautions. Hard power cuts are not free: a drive that is writing during a forced shutdown can be left in an inconsistent state, so use this method only when Windows is already failing to start and not as a casual shortcut. And on some laptops, holding the power button too long into the sequence triggers a firmware reset that has nothing to do with Windows. If the sequence leads to a loop that never offers advanced options, go to our dedicated guide to the automatic repair loop.

What to try from the recovery screen besides safe mode

Once you are in the recovery environment, safe mode is only one of the tools. In many failures, one of these is faster:

• Startup Repair: fixes common boot file problems automatically.
• Uninstall Updates: removes the latest quality update or feature update without needing to boot Windows. This is often the quickest fix when a problem started right after Patch Tuesday.
• System Restore: returns system files and drivers to an earlier restore point without touching your documents, if restore points exist.
• Command Prompt: lets you run sfc, DISM, chkdsk and bcdedit offline (see the command blocks).

Method 5: boot from a Windows 11 USB drive (when the recovery environment is missing)

A Windows installation USB drive gives you the recovery tools even when the built-in recovery partition is damaged. Boot from it, choose Repair your computer, then Troubleshoot, Advanced options, and either Startup Repair, Uninstall Updates or Command Prompt. You create the drive on any working PC, and it costs only the price of an 8 GB or larger USB stick.

1. On a working PC, download the official Windows 11 installation media from Microsoft's download page and create a bootable USB with the Media Creation Tool. The drive will be erased, so use a blank one.
2. Plug the USB into the broken PC and power it on. Press the boot menu key straight away (commonly F12, F9, Esc or F10, depending on the brand; check the logo screen or the manual).
3. Select the USB drive (the entry may be labelled UEFI: followed by the brand name).
4. On the first Windows Setup screen, pick the language and click Next. Do not click Install now.
5. Click Repair your computer at the lower left.
6. Choose Troubleshoot, then Advanced options, and pick your tool.

A subtle point worth knowing: Startup Settings, and therefore the 4, 5, 6 menu, is not always offered when you repair from installation media. That is not a problem, because you can set safe mode yourself with a command from this environment. This is Method 6, and we show it with the correct identifier, which is different from the one you use inside Windows.

Method 6: the bcdedit command (for technicians, scripts and remote sessions)

Run bcdedit /set {current} safeboot minimal from an elevated Command Prompt inside Windows, or bcdedit /set {default} safeboot minimal from the recovery Command Prompt, then restart. Windows boots into safe mode on every restart until you delete the flag. It does exactly what the msconfig tick box does, written directly into the boot configuration.

:: Safe mode (minimal)
bcdedit /set {current} safeboot minimal

:: Safe mode with networking
bcdedit /set {current} safeboot network

:: Safe mode with command prompt
bcdedit /set {current} safeboot minimal
bcdedit /set {current} safebootalternateshell yes

:: Restart to apply
shutdown /r /t 0

If you are in the recovery Command Prompt (from WinRE or the installation USB), the running system is the recovery image and not your Windows installation, so {current} points to the wrong thing. Use {default} for your installed Windows instead.

:: In recovery Command Prompt (WinRE or installation USB)
bcdedit /set {default} safeboot minimal
exit

Then choose Continue to boot into safe mode. If you have more than one Windows installed, run bcdedit /enum all first and read the identifier for the right entry. To undo any of these, see the removal commands in the stuck in safe mode section; they are the most important lines in this article.

Remote support note

A remote technician cannot reach safe mode through a regular remote desktop session, because most remote tools do not load in plain safe mode. Safe mode with networking works with some tools when they are configured to run as a service, and a few enterprise tools are built for it. If you are in the middle of a session with us and a safe mode step is needed, we guide you through it by phone, or we use a safe-mode-capable method with your consent.

The F8 myth on laptops and modern PCs

Tapping F8 during startup no longer opens the safe mode menu on a normal Windows 11 PC. Fast UEFI firmware and SSDs leave no time to tap, and Windows 11 does not show the old boot menu by default. Use Shift plus Restart instead. Many older guides still recommend F8, which is why so many people think safe mode is broken when it is only the guide that is out of date.

You can re-enable the old text-style menu with the command below, but we do not recommend it as your main method because it depends heavily on your firmware, and it has no effect on firmware that boots in under two seconds.

:: Turn the legacy F8 menu on
bcdedit /set {default} bootmenupolicy legacy

:: Turn it back off (restore the default)
bcdedit /set {default} bootmenupolicy standard

Also note that the "F8 does nothing" complaint on a laptop with a function-key lock sometimes means the key needs the Fn key held as well. On some laptops F8 is the volume or display-brightness key. That is a keyboard-layout issue, not a Windows issue.

BitLocker and safe mode: save your key first

Changing boot settings or entering the recovery environment can make a BitLocker-protected PC ask for its 48-digit recovery key. If device encryption is on, retrieve the key from your Microsoft account (account.microsoft.com/devices/recoverykey) or from your IT administrator before you start. Without it, you can be locked out of your own drive, and no technician can bypass that safely or legitimately.

Not every safe mode boot triggers the prompt, and modern PCs with a TPM often continue silently. But the cost of checking is tiny and the cost of a surprise is a weekend of stress. Look for the key on the account page for the Microsoft account used to set up the PC, in an Entra ID or work account, in a printout or in a USB file you saved earlier. If you manage multiple PCs, record who holds each key.

We cover the entire topic, including how to read the key ID on the blue screen and match it to the right key, in BitLocker recovery key after a Windows update. Suspending BitLocker before you make boot changes (Control Panel, BitLocker Drive Encryption, Suspend protection) is a further precaution; it lets you reboot a few times without prompts, but resume protection afterward.

What to do once you are in safe mode: the repair playbook

Safe mode is a workbench, not a destination. Once inside, the usual order is: test whether the problem disappears, then remove the most recent change (update, driver or program), then repair system files, then scan for malware, and only then consider System Restore or a reset. Work from the least destructive step to the most destructive, and change one thing at a time so you know what fixed it.

Step 0: the one-minute diagnostic

Use the PC for a few minutes in safe mode. Does it still crash, freeze or show the blue screen? The result decides your path:

Fix 1: uninstall the latest Windows update

If trouble began right after an update, remove it. In safe mode open Settings, Windows Update, Update history, Uninstall updates, pick the most recent entry and uninstall it. If Settings will not open, use the command line. The first command lists installed updates, the second removes one by its number (replace the digits with the real KB).

:: List recent updates (newest first)
powershell -command "Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10"

:: Remove a specific update (example number only)
wusa /uninstall /kb:5000000 /quiet /norestart

Some updates, notably the servicing stack, cannot be removed, and the command will say so. On a PC that will not start at all, the recovery environment's Uninstall Updates option does the same job. After removal, pause updates for a few days to avoid an immediate reinstall, and watch release notes so you know when a corrected build is out. Our Windows Update stuck or failing guide covers the follow-up.

Fix 2: roll back or remove a bad driver

Graphics, network and storage drivers are the usual suspects. Press Windows + X, choose Device Manager, expand Display adapters, right-click the adapter and pick Properties, Driver, Roll Back Driver. If the button is grey, choose Uninstall device and tick "Attempt to remove the driver for this device" if offered. On restart Windows installs a basic driver, and you can then fetch a stable version from the manufacturer; see how to update drivers safely.

For a driver that keeps coming back, list third-party drivers and remove it by its published name:

:: List installed third-party drivers
pnputil /enum-drivers

:: Remove one (replace oemXX.inf with the real name)
pnputil /delete-driver oemXX.inf /uninstall /force

Be careful: removing a storage or chipset driver can make the PC unbootable. Only remove what you have identified as the problem, and write the published name down first.

Fix 3: repair Windows system files (copy-paste block)

Open the Command Prompt as administrator (in safe mode with command prompt, you already have one). Run these in order and let each finish. They can take 10 to 30 minutes, and the progress counters occasionally pause, which is normal.

:: 1. Check and repair protected system files
sfc /scannow

:: 2. Repair the component store (needs time; internet helps)
DISM /Online /Cleanup-Image /RestoreHealth

:: 3. Run sfc once more after DISM
sfc /scannow

:: 4. Schedule a disk check at next restart (answer Y)
chkdsk C: /f

If DISM cannot reach its source in plain safe mode, repeat it in safe mode with networking, or point it at the install media with DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.wim:1 /LimitAccess (replace D: with the drive letter of the mounted ISO or USB). From a recovery command prompt, replace /Online with /Image:C:\ and add /ScratchDir:C:\, because drive letters differ inside WinRE. Run diskpart then list volume to confirm which letter holds Windows.

Fix 4: scan for malware

Most malware does not load in safe mode, which makes it easier to find and remove. Use safe mode with networking so definitions can update, and open Windows Security, Virus & threat protection, Scan options. Choose Microsoft Defender Antivirus (offline scan) for a deep scan; Windows restarts and scans before it fully loads. Alternatively, run your usual antivirus from safe mode. A second opinion from a reputable on-demand scanner is reasonable, but avoid installing three tools at once. For the complete process read how to remove a virus from your computer.

If you find real malware, assume passwords typed on that machine are compromised and change them from a different, trusted device. This matters more than the cleanup itself.

Fix 5: System Restore

Run rstrui.exe (Windows + R) and pick a restore point from before the problem. System Restore reverts system files, drivers and registry settings, and does not delete your documents. It does remove programs installed after that point. Restore points exist only if System Protection was enabled on the drive, and not every PC has it on by default. If the list is empty, skip this step.

:: Open System Restore
rstrui.exe

:: Check whether System Protection is on (look for restore points)
vssadmin list shadows

Fix 6: find a bad startup app or service (clean boot)

If the issue vanishes in safe mode but returns in normal mode, do a clean boot. In msconfig, on the Services tab tick "Hide all Microsoft services" and then "Disable all"; in Task Manager, Startup apps, disable everything. Restart, then re-enable half at a time until the problem returns. It is the same method as bisecting a bug, and it works. Remember to restore normal startup when finished, in the same msconfig window.

Fix 7: create or test another user account

If a single profile is broken, a new local administrator account can show you. Safe mode with command prompt is perfect for this, because it is a clear text interface. Replace the example names with your own.

net user TempFix ChooseALongUniquePassword1 /add
net localgroup administrators TempFix /add

Sign in with the new account after a normal restart. If the problem is gone, the old profile is corrupt; copy your data across and retire the old account. Delete TempFix when finished with net user TempFix /delete. Use a strong unique password, and never leave a test account lying around with a weak one.

How to exit safe mode in Windows 11

To leave safe mode, simply restart the computer: click Start, Power, Restart. Microsoft states that restarting should be enough to return to normal mode. If the PC boots back into safe mode, the safe boot flag is set, and you must clear it in msconfig or with bcdedit. The sections below cover each case in the order you should try them.

1. Normal restart. Power, Restart (not Shut down, then Start, which on Windows 11 with Fast Startup may behave differently for some settings). Wait for the sign-in screen and look for the "Safe Mode" text in the corners. If it is gone, you are done.
2. msconfig. Windows + R, msconfig, Boot tab, clear Safe boot, OK, Restart.
3. bcdedit. Open an administrator Command Prompt and run the commands in the next section.
4. Recovery route. If you cannot reach a desktop, use the recovery Command Prompt (also below).

(Get-CimInstance Win32_ComputerSystem).BootupState

Stuck in safe mode: why it happens and the fixes, in order

A PC that keeps rebooting into safe mode almost always has a persistent safe boot flag, set by the msconfig Safe boot box or by a bcdedit /set safeboot command. Clear it with bcdedit /deletevalue {current} safeboot, then restart. If you cannot reach a command prompt inside Windows, run bcdedit /deletevalue {default} safeboot from the recovery Command Prompt. Fixes are ordered here from least to most effort.

Fix A: untick Safe boot in msconfig

1. Press Windows + R, type msconfig, press Enter.
2. Open the Boot tab.
3. Clear the Safe boot checkbox. If the checkbox is already clear, move to Fix B.
4. Click Apply, OK, then Restart.

Fix B: delete the flag with bcdedit (copy-paste)

Open Command Prompt as administrator (in safe mode: Start, type cmd, right-click, Run as administrator). Run each line, then restart.

:: Remove the safe boot flag
bcdedit /deletevalue {current} safeboot

:: Remove the command-prompt (alternate shell) flag, if it was set
bcdedit /deletevalue {current} safebootalternateshell

:: Show the entry to confirm no safeboot line remains
bcdedit /enum {current}

:: Restart
shutdown /r /t 0

If a line returns "The element data type specified is not recognized" or "element not found", that flag simply was not set, and you can ignore the message. Both commands are safe to run when nothing is set. A lingering bootmenupolicy legacy setting does not cause safe mode, but if you used it for F8, restore it with bcdedit /set {current} bootmenupolicy standard.

Fix C: you cannot reach the desktop (safe mode with command prompt is the only thing that loads)

Safe mode with command prompt opens a black window and no desktop. You already have what you need: in that window, type the Fix B commands directly. If a window is not elevated, you will see "Access is denied". In that case the shell runs as an administrator account normally, so check you signed in with an administrator account.

Fix D: boot to recovery and clear it offline

If safe mode crashes, or you cannot sign in, use Method 4 or Method 5 to open the recovery Command Prompt, then run:

:: In the recovery Command Prompt
bcdedit /deletevalue {default} safeboot
bcdedit /deletevalue {default} safebootalternateshell
bcdedit /enum
exit

Choose Continue. Use {default} here, not {current}, for the reason covered in Method 6. If bcdedit /enum shows several entries, check the one whose path reads \Windows\system32\winload.efi and use its identifier in place of {default}.

Fix E: the boot configuration is damaged

If bcdedit reports that the boot configuration data store cannot be opened, or Windows will not start at all, the store is damaged. From the recovery Command Prompt run Startup Repair first. If that fails, the standard rebuild sequence is below. It is a more advanced procedure, so only use it when you understand your disk layout, and have a backup or a technician at hand.

bootrec /fixmbr
bootrec /fixboot
bootrec /scanos
bootrec /rebuildbcd

On UEFI systems, bootrec /fixboot sometimes returns "Access is denied". That is a known quirk of some systems and builds, and it needs extra steps that assign a letter to the EFI System Partition and use bcdboot. Because mistakes can leave the PC unbootable, this is the point at which most people are better served by a pro. See our boot failure 0xc0430001 guide for an example of the process.

Fix F: stuck in safe mode and sign-in fails

If you reach the safe mode sign-in screen but cannot get in, use the Sign-in options link to switch from PIN to password. For a Microsoft account, you must type the actual Microsoft account password. If you do not remember it, reset it from another device through the account recovery page, then retry. A password change made online may need a network connection to the PC to take effect; if the PC is offline, the last known password may still be what Windows accepts until it reconnects.

Troubleshooting table: stuck in safe mode

Why your PC might drop into safe mode on its own

Occasionally a PC enters safe mode that you never asked for. The common reasons are a leftover safeboot flag from a technician or a tool, repeated failed starts that lead to the recovery environment, a repair utility that sets a flag and does not clear it, or in rare cases malware that forces safe mode to disable your security tools. If it keeps returning after you clear the flag, scan the PC and look at who has been working on it. Check Event Viewer, Windows Logs, System, around the time of the last restart for hints, and consider that a failing drive can cause repeated crashes that look like a safe mode loop.

When safe mode itself misbehaves: Wi-Fi, mouse, sign-in and work PCs

Most safe mode complaints come down to four things: no Wi-Fi because plain safe mode has no network, a PIN that will not work, a tiny low-resolution screen, or a work PC whose policy blocks the recovery menu. Each has a short answer, and none means the PC is broken.

• No internet. Plain safe mode never has it. Use option 5 (networking). If Wi-Fi still fails, the wireless driver is likely not part of the safe set; plug in Ethernet or tether a phone by USB.
• PIN or fingerprint fails. Use Sign-in options and type the account password. This is the single most common surprise.
• Low resolution, big icons. Expected; the generic display driver is running. It returns to normal once you boot normally with a working graphics driver.
• Touchpad or touchscreen behaves oddly. Some precision touchpad drivers do not load. A USB mouse solves it for the session.
• Work or school PC. Policy can hide Advanced startup or require an administrator. Your organisation may also hold the BitLocker key. Ask IT rather than working around it.
• Windows 11 in S mode. You still can enter safe mode through the recovery menu; command-line steps in this guide may be limited by the S mode restrictions.
• Virtual machines. Use the same recovery methods inside the guest; Shift plus Restart works well.

Three realistic scenarios (illustrative)

These are illustrative examples built from common patterns, not records of real clients. They show how long each fix typically takes and which path is the cheapest.

Scenario 1: black screen after a graphics driver update

A home user installs a new graphics driver on a Wednesday evening. After the restart, the screen goes black right after the logo. Pressing keys does nothing. They power off three times, Windows opens Automatic Repair, and they choose Advanced options, Startup Settings, Restart, then press 5. In safe mode with networking they open Device Manager, roll back the display driver, and restart normally. The desktop comes back. Time: about 25 minutes, cost: nothing, lesson: write down the driver version before updating. See also our black screen guide.

Scenario 2: a small office laptop stuck in a safe mode loop

An accountant's laptop reboots into safe mode every morning after a helpful colleague used msconfig the day before and forgot to untick Safe boot. The office assumes the PC is broken and plans to buy a replacement. A technician opens msconfig, clears Safe boot, restarts, and the laptop is normal in under three minutes. The conversation takes longer than the fix. A 60-minute remote session at 119.99$ CAD would have been plenty, and DIY would have cost nothing if the checklist above had been handy.

Scenario 3: a PC that will not enter safe mode and shows a BitLocker screen

A freelancer's laptop crashes after a firmware update and drops into recovery, where a BitLocker screen asks for a 48-digit key. The key is saved in the Microsoft account, found on a phone in two minutes. After entering it, they run Startup Repair, which fails, then use Command Prompt to run chkdsk C: /f, which finds and fixes file system errors. Windows starts again, but the drive's health is questionable, so they back up the same day and book a drive check. Total time about 90 minutes. The lesson: save the key first, and after any disk error, treat the backup as urgent. Our data recovery after a Windows update guide explains what to do if files seem missing.

What it costs in Canadian dollars: DIY versus a technician

Starting, using and leaving safe mode costs nothing in software. The real cost is your time and the risk of making the situation worse. A remote technician session is a single 60-minute Expert Consultation at 119.99$ CAD, taxes extra, and a typical safe mode problem fits in that hour.

Before paying for any new hardware, spend one hour on safe mode diagnostics. Most "my PC is dead" calls turn out to be a driver, an update or a stuck setting. If the diagnostics show a failing drive, the priority switches from fixing to rescuing data, and DIY tools can make damage worse; stop and call a professional at that point. Our comparison of recovery versus backup explains why.

When to call a pro

Call a technician if Windows will not reach safe mode after the recovery routes, if bcdedit reports a damaged boot store, if you hear clicking from the drive, if BitLocker will not accept any key, or if you suspect malware and the PC holds business or banking data. Stopping early is cheaper than a wrong command on a drive that holds your only copy of important files.

IT Cares has provided remote and on-site IT support in Quebec and across Canada since 2014. We can walk you through safe mode by phone, run the repairs remotely once you can reach a desktop, or arrange help on site in Quebec. Call 1 (888) 711-9428 or book a session from the button below. Related first aid pages: blue screen fixes, laptop black screen and the automatic repair loop.

Official resources

• Microsoft Support: Start your PC in safe mode in Windows (covers Startup Settings keys and the msconfig exit).
• Microsoft Learn: BCDEdit /set reference, which documents the safeboot options.
• Microsoft Learn: Advanced troubleshooting for Windows boot problems.

One-page summary to keep

Frequently asked questions

Related guides

• Windows 11 automatic repair loop and stuck on Working on updates
• BitLocker recovery key after a Windows update
• Windows will not boot after an update: fix
• Fix the blue screen of death in Windows 11
• Black screen of death: how to fix it
• Laptop black screen fix
• How to update drivers safely
• How to remove a virus from your computer
• Windows Update stuck or failing: how to fix it
• Data recovery after a Windows update or reinstall
• Fix Windows 11 boot failure 0xc0430001
• GPU driver crashed: fix

Sources and official references

Last verified: October 1, 2026

• Microsoft Support: Start your PC in safe mode in Windows
• Microsoft Learn: BCDEdit command-line options
• Microsoft Learn: Windows Recovery Environment (Windows RE)