macOS Error Code 9000: How to Fix It
Medium 30-90 minutes High Severity
Verified July 2026
- Error Code
- 9000
- Brand
- macOS
- Product Type
- operating_system
- Severity
- High
- DIY Difficulty
- Medium
- Estimated Fix Time
- 30-90 minutes
Ad
Tools You'll Need
- Mac computer running macOS
- Console app (built into macOS, found in Applications > Utilities)
- Disk Utility (built into macOS, found in Applications > Utilities)
- Time Machine or external backup drive
- Stable internet connection (for downloading updates)
- Optional: third-party uninstaller app (e.g., AppCleaner)
How to Fix Error Code 9000
-
Force Restart Your Mac
Save any open work before restarting if at all possible. Unsaved documents may be lost during a force restart. -
Check for macOS Software Updates
Back up your Mac using Time Machine or an external drive before installing major macOS updates. -
Review Console Logs for WindowServer Errors
-
Identify and Remove Problematic Third-Party Apps
-
Reset NVRAM and SMC
NVRAM and SMC resets are safe and non-destructive. Your files and apps will not be affected. -
Boot into Safe Mode and Test Stability
-
Disable Login Items and Launch Agents
-
Check and Repair Disk Permissions with Disk Utility
Do not interrupt the First Aid process once started, as this could cause additional disk errors. -
Create a New User Account to Isolate the Issue
-
Reinstall macOS as a Last Resort
Back up all important data to an external drive or Time Machine before reinstalling macOS, even though the process is designed to preserve user data.
Ad
When to Call a Professional
Contact Apple Support or visit an Apple Authorized Service Provider if: the WindowServer crashes persist after a full macOS reinstall, your Mac shows signs of hardware failure (artifacts on screen, random shutdowns, overheating), you suspect a failing GPU or logic board, or your Mac is under AppleCare+ warranty and you want a hardware diagnostic performed at no additional cost. You can also book a Genius Bar appointment at apple.com/retail.Frequently Asked Questions
What is WindowServer on a Mac and why does it crash?
WindowServer is a core macOS system process that manages everything displayed on your screen — windows, the dock, menu bar, and all visual elements. It can crash due to corrupted system files, buggy third-party apps that interact with the display layer, outdated macOS software, overloaded GPU resources, or corrupted user preference files. Error Code 9000 specifically signals that this process terminated unexpectedly and had to be restarted.
Will macOS Error Code 9000 cause me to lose my files?
In most cases, no. The WindowServer crash itself does not delete or corrupt your personal files. However, any unsaved work in open applications at the moment of the crash may be lost. After recovering from Error Code 9000, your documents, photos, and other files should remain intact. It is still best practice to keep a current Time Machine backup.
Why does macOS Error Code 9000 keep happening repeatedly?
Recurring WindowServer crashes usually point to a persistent underlying cause: a recently installed app that conflicts with the display server, a corrupted user preference or cache file, an outdated macOS version with a known bug, or — less commonly — failing graphics hardware. Work through the troubleshooting steps methodically, paying special attention to removing recently installed third-party apps and testing in a new user account to isolate the source.
Does resetting NVRAM fix macOS Error Code 9000?
Resetting NVRAM can help if the WindowServer crash is related to corrupted display or graphics settings stored in non-volatile memory, such as incorrect screen resolution settings or display configuration data. It is not a guaranteed fix for all causes of Error Code 9000, but it is a safe, quick step worth trying early in the troubleshooting process since it has no negative side effects.
Can a bad external monitor or display cable cause macOS Error Code 9000?
Yes. A faulty or incompatible external display, a damaged video cable, or a defective adapter (such as a USB-C to HDMI or Thunderbolt adapter) can cause WindowServer to crash when it struggles to communicate with the display hardware. Try disconnecting all external monitors and adapters, then restart using only your built-in display. If the crashes stop, test each external display and cable individually to identify the faulty component.