Table of Contents
Are you running a macOS virtual machine using the OpenCore VMDK method and feeling frustrated every time you boot it up? Instead of a clean Apple logo, you’re greeted by a flood of white diagnostic text scrolling endlessly across the screen. That’s the verbose boot output—a helpful tool for troubleshooting, but an eyesore once your system is stable.
In this guide, I’ll show you exactly how to Remove Verbose from macOS VM in just a few simple steps, so you can enjoy a smooth, silent startup that looks just like a real Mac. No command-line expertise or macOS reinstallation is required. Just follow along, and you’ll have it fixed in under five minutes.
What Causes a Verbose Boot on a macOS VM?
Verbs mode (technically called “verbose mode”) is a boot argument, typically -v , that tells macOS to show all the kernel and driver messages during startup. It’s often left enabled in pre‑made OpenCore configurations to help diagnose boot issues on virtual machines. Once your macOS VM is running reliably, though, there’s no reason to keep seeing this waterfall of console text. The fix is simple: you need to edit your OpenCore configuration file and remove that -v flag. Let me walk you through it.
What You’ll Need
Before we begin, make sure your macOS virtual machine is fully booted, and you’re logged into the desktop. We’ll use two free tools:
- OC Auxiliary Tools (OCAT) – to mount the hidden EFI partition that contains your OpenCore files.
- ProperTree – a Plist editor to safely modify the
config.plistfile.
Both are open source and available on GitHub. I’ll guide you through downloading and using each one step by step.
Step-by-Step: Remove Verbose from macOS VM
1. Download and Launch OC Auxiliary Tools
First, open any web browser on your macOS virtual machine and search for OC Auxiliary Tools. Click the first result that leads to its GitHub page.
Under the Releases section on the right, click the latest available version. Scroll down to the Assets area and download the .dmg file.
Once the download finishes, head to your Downloads folder and double-click the DMG file to mount it. Inside the mounted volume, double-click OCAuxiliaryTools to run the app.
2. Handle macOS Security Prompts
Because OCAT is downloaded from the internet, macOS will block it at first. When you see the warning “OCAuxiliaryTools cannot be opened,” click Close.
Then go to System Settings > Privacy & Security. Scroll down a bit—you’ll see a message saying OCAuxiliaryTools was blocked. Click Open Anyway, enter your macOS password, and click Launch to open the tool.
Once the app opens, you may see a brief warning about modifying system files; dismiss it, and the main dashboard will appear.
3. Mount Your EFI Partition
Now we need to access the hidden EFI partition where OpenCore lives. In the OC Auxiliary Tools menu bar, click Edit and select Mount ESP.
A window will pop up showing all available drives. Look for your virtual SATA hard drive—this is where your macOS VM is installed. Select its EFI entry and click the Mount button. Enter your password when asked and click OK. After a moment, a new volume called EFI will appear in Finder.
4. Download and Set Up ProperTree
While the EFI partition is mounted, let’s get the editor ready. Go back to your browser and search for ProperTree (the macOS Plist editor). Open the first GitHub link that comes up.
On the repository page, click the green Code button, and then choose Download ZIP. When the download completes, go to your Downloads folder and extract the ZIP file. Inside the extracted folder, double-click the ProperTree.command file.
You’ll see a security warning again that ProperTree cannot be opened. Don’t worry—this is the same routine. Open System Settings > Privacy & Security, scroll down, and look for the message saying “ProperTree was blocked.” Click Open Anyway, enter your password, and then click Open to launch the script.
A terminal window will now appear, asking whether you want to install Python (ProperTree requires it). Type Y and press Enter. The installation runs automatically, and after a few seconds, the ProperTree graphical interface will appear.
5. Edit the Config.plist to Remove Verbose from macOS VM
In ProperTree, click File in the top menu, then Open. Navigate to the mounted OpenCore EFI partition, open the OC folder, and select config.plist. Click Open.
You’ll see a structured list of settings. Scroll down until you find the NVRAM section. Inside it, look for an entry called boot-args (this stands for boot arguments). Under its value, you’ll likely see something like -v keepsyms=1 debug=0x100. The culprit is the -v flag. Simply delete the -v (and any extra space it leaves behind), leaving the rest of the string untouched. For example, you might change it to keepsyms=1 debug=0x100.
After you’ve removed the flag, press Command + S (or go to File > Save) to save the config.plist. Now you can close ProperTree.
6. Restart Your macOS VM
Everything is done! Restart your virtual machine. You’ll now see the familiar Apple logo and a progress bar—quiet, clean, and exactly what you wanted. The verbose text is gone for good.
Why should you remove Verbose from macOS VM?
Beyond just a cleaner look, disabling verbose mode makes your macOS VM feel much more polished and authentic. It also reduces unnecessary energy and resource usage during boot because the system doesn’t need to render all that text. If you ever need to troubleshoot in the future, you can easily re-add the -v argument the same way you removed it. But for daily use, a silent startup brings your virtual Mac experience one step closer to the real thing.
Video Tutorial: Remove Verbose from macOS VM
Final Thoughts: Remove Verbose from macOS VM
You’ve just learned how to quickly remove Verbose from macOS VM using nothing more than a couple of free tools and a few minutes of your time. The process might look a little involved at first, but once you’ve done it, you’ll realize how straightforward it really is.
If this tutorial helped you get that clean Apple boot screen back, I’d really appreciate it if you’d give it a thumbs up and subscribe to the channel for more practical macOS virtualization fixes. Got stuck at any point? Drop a comment below, and I’ll do my best to help.
Now reboot your VM and enjoy that beautiful, silent startup—just like a real Mac.
