Tech Troubleshooting

Safe Mode on Windows and macOS: When and How to Use It for Troubleshooting

Laptop screen showing a Safe Mode boot selection menu in a minimal interface.

Key Takeaways

  • Safe mode loads your OS with only essential drivers and system files, excluding third-party software.
  • Windows and macOS have different methods for entering safe mode — neither requires advanced technical skill.
  • Use safe mode to confirm whether a problem is caused by software, a driver, or the OS itself.
  • Most everyday troubleshooting tasks, like uninstalling a bad driver, can be completed from within safe mode.
  • Exiting safe mode simply requires a normal restart on both Windows and macOS.
5–20 min
Intermediate

What you will need

Access to your computer's administrator account username and password
Basic familiarity with restarting your computer
Knowledge of which OS version your computer runs (Windows 10/11 or macOS Ventura/Sonoma/etc.)
For Mac users: know whether your Mac uses an Intel processor or Apple Silicon (M-series chip)

What Safe Mode Actually Does

Safe mode is a stripped-down version of your operating system that loads only the drivers and system files your OS absolutely requires to run. Third-party applications, non-essential drivers, and most startup programs are bypassed entirely. Think of it as your OS with everything optional switched off.

This minimal environment is valuable because it creates a controlled baseline. If a problem — say, a persistent crash or a frozen desktop — disappears in safe mode but reappears in normal mode, you can confidently conclude that the OS core itself is not at fault. The cause is something layered on top: a browser extension, an antivirus program, a graphics driver, or another piece of third-party software.

Safe mode is one of several built-in diagnostic approaches available on modern computers. For a broader look at what Windows and macOS offer natively, see our guide to built-in diagnostic tools. And if you're curious how each OS handles fundamental tasks differently, this OS comparison provides useful context.

Back Up Before You Begin

If your computer is experiencing serious instability — such as frequent crashes or failure to boot — back up important files to an external drive or cloud storage before attempting any troubleshooting. Safe mode is a diagnostic environment, not a recovery tool, and it does not protect your data from hardware failures.

Tools and Access You'll Need

Safe mode doesn't require any special software, but a few things must be in place before you start.

What you will need

Access to your computer's administrator account username and password
Basic familiarity with restarting your computer
Knowledge of which OS version your computer runs (Windows 10/11 or macOS Ventura/Sonoma/etc.)
For Mac users: know whether your Mac uses an Intel processor or Apple Silicon (M-series chip)
Required

Windows PC or laptop

The device you'll boot into Windows Safe Mode for troubleshooting.

Required

Mac computer (Intel or Apple Silicon)

The device you'll boot into macOS Safe Mode; the entry method differs by chip type.

Optional

External keyboard (Mac users)

Required on some Mac desktops to hold the Shift key during startup for safe mode entry.

Required

Administrator account credentials

Safe mode on both platforms may require admin login to make system-level changes.

Step-by-Step Instructions

Follow the steps below in order. Steps 2 through 4 cover platform-specific entry methods — skip to the one that matches your device.

1

Identify what problem you're trying to isolate

Before entering safe mode, write down exactly what's going wrong: crashes, a specific app failing, display problems, or slow performance. This helps you test systematically once inside safe mode rather than guessing. If the issue is absent in safe mode, a third-party driver or app is the likely culprit.

Tip: Check if the problem appeared after a recent Windows Update, driver installation, or new app install — that timing often points directly to the cause.
2

Enter Safe Mode on Windows 10 or 11

Open SettingsSystemRecovery. Under Advanced startup, click Restart now. After the restart, select TroubleshootAdvanced optionsStartup SettingsRestart. When the Startup Settings screen appears, press 4 for Safe Mode or 5 for Safe Mode with Networking (useful if you need internet access to download a fix).

Tip: If Windows won't boot at all, interrupt startup three times by holding the power button during boot — Windows will automatically open the Recovery Environment.
3

Enter Safe Mode on a Mac with Apple Silicon (M-series)

Shut down your Mac completely. Press and hold the power button until you see Loading startup options. Select your startup disk, then hold Shift and click Continue in Safe Mode. Log in as normal — your Mac will display Safe Boot in the menu bar to confirm the mode is active.

Warning: Do not release the Shift key until the login screen appears, or your Mac may boot normally instead.
4

Enter Safe Mode on an Intel-based Mac

Shut down your Mac. Turn it on, then immediately press and hold the Shift key. Release Shift when the login window appears. The words Safe Boot will appear in red at the top-right corner of the login screen. Log in to confirm you're in safe mode.

Tip: Intel Macs with FileVault encryption may require you to log in twice — once to unlock the disk and again to access the desktop.
5

Perform your troubleshooting tasks

With safe mode active, attempt to reproduce the original problem. If it's gone, use this opportunity to uninstall recently added apps, roll back a driver (on Windows: Device Manager → right-click the device → PropertiesDriverRoll Back Driver), or delete problematic startup items. On macOS, you can remove login items via System SettingsGeneralLogin Items.

Warning: Avoid installing new software or making major system changes while in safe mode — some installers require full system services and may behave unpredictably.
6

Exit safe mode and verify the fix

On both Windows and macOS, simply restart your computer normally — do not hold any keys. The system will boot back into its full operating environment. Test whether the original problem has been resolved. If the issue returns, safe mode has confirmed it's software-related, and you can continue investigating with that confidence.

Tip: Run your computer for 15–30 minutes after the normal restart before concluding the fix worked, especially for intermittent crashes.

Test in Safe Mode First

If the problem you're experiencing — such as a crash or display glitch — disappears entirely in safe mode, the cause is almost certainly a third-party app, browser extension, or recently installed driver. Use that insight to narrow your investigation before returning to normal mode.

When Safe Mode Doesn't Resolve the Issue

If your problem persists even in safe mode, the issue likely lies within the core OS, your hardware, or a corrupted system file rather than a third-party application. On Windows, tools like System File Checker (sfc /scannow run from an elevated Command Prompt) can scan and repair corrupted system files. On macOS, Disk Utility's First Aid function can check and repair filesystem errors.

Hardware problems — a failing drive, overheating, or faulty RAM — will not be resolved by safe mode at all, since safe mode only controls which software loads. If you suspect hardware, the logical next step is running platform-specific hardware diagnostics (Windows Memory Diagnostic or Apple Diagnostics, respectively).

It's also worth distinguishing safe mode from simply restarting. A restart clears temporary software states and can fix many minor glitches on its own — but it doesn't isolate which software caused the problem the way safe mode does. For more on what different power states do and don't fix, see common myths about restarting and sleep mode.

Don't Use Safe Mode as Your Regular Environment

Safe mode disables networking features, audio drivers, and many system services. It is intended only for short-term troubleshooting. Running your computer in safe mode long-term can prevent updates from installing and may cause unexpected application behavior.

Tech Troubleshooting Editorial Team is the collective byline for our editorial team and contributor network. Articles published under this byline or an editorial pen name are researched, written, and reviewed according to our editorial standards for clarity, consistency, and independence before publication.

View all articles by Tech Troubleshooting Editorial Team →
Disclaimer: The content on this site is for informational purposes only and is not a substitute for professional advice. Always consult a qualified professional for guidance specific to your situation.