Boot Verbose Mode: What It Is and How to Enable It

Boot verbose mode is a diagnostic setting that displays detailed text on screen while your operating system starts up, showing every driver, service, and process as it loads. You enable it by adding a boot parameter or changing a setting in your system configuration, and it helps you see exactly where a boot failure or slowdown occurs. This article explains how to turn it on for Windows, macOS, and Linux, how to read the output, and how to turn it off when you’re done.

What Is Boot Verbose Mode?

Boot verbose mode replaces the normal splash screen (like the Windows logo or Apple logo) with a rolling list of text messages. Each line typically shows a timestamp, the name of a driver or service, and a status message such as “loaded,” “failed,” or “waiting.” The purpose is to give you a real-time view of the boot sequence so you can spot the exact component that hangs, errors, or takes an unusually long time.

It is a diagnostic tool, not a performance feature. It does not make your computer boot faster or slower in any meaningful way (the text rendering adds a negligible amount of time). It is meant for troubleshooting, and most users turn it off after they find the problem.

How to Enable Verbose Boot on Windows

Windows has a built-in setting called “Enable verbose boot status” that you can turn on without any third-party tools. Here’s how:

1. Press Win + R, type msconfig, and press Enter.
2. Go to the Boot tab.
3. Check the box next to OS boot information (this is the verbose mode option).
4. Click OK and restart your computer.

After restarting, you’ll see a list of drivers loading instead of the Windows logo. To turn it off, uncheck the same box and restart again.

If you prefer using the command line, you can also enable it with bcdedit in an elevated Command Prompt:

bcdedit /set bootstatuspolicy displayallfailures
bcdedit /set {current} bootmenupolicy legacy

The first command shows all failures, not just the first one. The second command is optional and changes the boot menu style, which some users find easier to read. To disable, set bootstatuspolicy back to ignoreallfailures and bootmenupolicy to standard.

How to Enable Verbose Boot on macOS

On a Mac, verbose mode is called Verbose Mode and it’s part of the startup options. To use it:

1. Shut down your Mac completely.
2. Press the power button and immediately hold Command + V.
3. Release the keys when you see white text on a black background.

This is a one-time setting — it only applies to that single boot. If you want to make it permanent (for example, if you’re debugging a recurring issue), you can set it with the nvram command in Terminal:

sudo nvram boot-args="-v"

To remove it, run sudo nvram boot-args="" or use sudo nvram -d boot-args to delete the variable entirely.

Note that on newer Macs with Apple silicon (M1 and later), the Command+V method still works, but you may need to wait a moment after pressing the power button before holding the keys.

How to Enable Verbose Boot on Linux

Linux distributions vary, but most use a bootloader called GRUB. To enable verbose mode (which is often called “nomodeset” or “quiet” removal):

1. Reboot your computer and hold Shift (on BIOS systems) or press Esc repeatedly (on UEFI systems) to get the GRUB menu.
2. Highlight the kernel you want to boot, press e to edit.
3. Find the line starting with linux (or linux16).
4. Remove the word quiet and optionally splash if present.
5. Press Ctrl+X or F10 to boot.

This is a one-time change. To make it permanent, edit the GRUB configuration file:

sudo nano /etc/default/grub

Find the line GRUB_CMDLINE_LINUX_DEFAULT and remove quiet and splash from inside the quotes. Save the file and run sudo update-grub (on Debian/Ubuntu) or sudo grub-mkconfig -o /boot/grub/grub.cfg (on Arch).

What the Output Tells You

Verbose boot output looks cryptic at first, but it follows a pattern. On Windows, you’ll see lines like:

Loaded driver \SystemRoot\System32\drivers\ntfs.sys

On macOS, you’ll see lines like:

com.apple.driver.AppleIntelCPUPowerManagement: loaded

On Linux, you’ll see lines like:

[    3.456789] sd 0:0:0:0: [sda] Starting disk

Key things to watch for:

• Errors or “failed” messages — a driver that fails to load can cause a hang or a crash.
• Long pauses between lines — if the output stops for several seconds, that’s the component causing the delay.
• The last line before a freeze — that’s usually the culprit.

If you see a line that ends with “failed” but the boot continues, it may not be critical — some drivers are optional. Only a few failures in a row indicate a real problem.

Common Problems and Misconceptions

One common misconception is that verbose mode is the same as “safe mode.” It is not. Safe mode loads a minimal set of drivers; verbose mode loads everything normally but shows you the details. They serve different purposes.

Another issue: on Windows, the msconfig option only works if you have administrative rights. If you don’t, you’ll get an error. Use an elevated prompt instead.

On macOS, if you set nvram boot-args="-v" and later forget it, your Mac will always boot in verbose mode. That’s harmless but annoying. You can check current boot-args with nvram boot-args and clear it with sudo nvram -d boot-args.

On Linux, removing quiet will also remove the splash screen (the logo animation). Some distributions use plymouth for the splash; if you want to keep the splash but add verbose text, that’s not directly possible — you have to choose one or the other.

When Should You Use Verbose Mode?

Use verbose mode when you have a specific boot problem:

• Your computer hangs or freezes during startup.
• Boot takes much longer than it used to.
• You see a blue screen or kernel panic before the desktop appears.
• You recently installed new hardware or drivers and now it won’t boot.

It’s not useful for everyday use. The text scrolls quickly and provides no benefit once the system is running. Turn it off after you’ve identified the issue.

Frequently Asked Questions

Q: Does verbose boot mode slow down my computer?
No. The text rendering takes a fraction of a second. The boot process itself is unchanged. If you notice a slowdown, it’s coincidental or due to a separate issue.

Q: Can I enable verbose mode on a laptop with a broken screen?
Yes, but you won’t see the output. You’d need to connect an external monitor or use a serial console (rare on consumer laptops). In that case, verbose mode isn’t helpful.

Q: How do I take a screenshot of verbose boot output?
You can’t take a normal screenshot because the OS isn’t fully loaded. Use your phone to take a photo of the screen, or on Linux you can redirect the output to a file using dmesg after boot.

Q: Is verbose mode the same as “boot logging”?
No. Boot logging writes the same information to a file (like ntbtlog.txt on Windows). Verbose mode shows it on screen. You can use both simultaneously.

Q: Will verbose mode fix my boot problem?
No, it only shows you the problem. You still need to update, reinstall, or remove the offending driver or service. But it tells you where to start.

Q: Can I enable verbose mode on Android or iOS?
Not easily. Android has a hidden boot log that you can access with adb logcat -b all after boot, but it’s not a text-on-screen mode. iOS doesn’t expose a user-facing verbose boot option.

Related

• Discord Gray Screen: Causes & Fixes
• MGS2 Master Collection vs Original: Which to Play?
• AI Agent Runtime Security: Enterprise Buyer Guide

in t | Time to boot (min) | min | 5 | 0
in d | Distance (optional) | km | 0 | 0
out pace | Boot speed score | - | 100 / t | 2
out speed | Effective speed | km/h | d / (t / 60) | 2