Windows ERROR_NO_SYSTEM_MENU (0X0000059D) fix
This error pops up when an app tries to open a system menu on a window that doesn't have one. Usually happens with old or broken software.
You're working away, and suddenly a popup says: ERROR_NO_SYSTEM_MENU with code 0X0000059D. Usually this happens when you click something in an old business app — like a point-of-sale system from 2005, or a custom inventory tool written in VB6. Or maybe you're trying to right-click a taskbar icon, and the whole thing freezes for a second, then this message appears.
I ran into this last month with a client's ancient accounting software. Every time they tried to close a window using the X button, boom — error. The app was trying to open the system menu (that little icon in the top-left corner of most windows) but the window didn't have one. Windows built that window without the WS_SYSMENU style flag, so there's no menu to open.
Root cause in plain English
The system menu is that little dropdown you get when you click the app icon in the title bar — it has Restore, Minimize, Maximize, Close. Some windows, especially in older or poorly-written software, don't bother including that menu. Windows doesn't care until something (usually the app itself or a bad plugin) tries to programmatically open that menu. Then it hits a wall and throws this error.
It's not a virus, not a hardware problem. It's a broken call from an app that's trying to do something its own window doesn't support.
How to fix it
Skip messing with system files or registry edits — that's overkill here. The real fix is simpler. Try these steps in order.
Step 1: Force-close the offending app
Open Task Manager (Ctrl+Shift+Esc). Find the app that's throwing the error. It's usually the one that was in focus when the error appeared. Right-click it and choose End Task.
If it won't die, you can run taskkill /f /im name.exe in Command Prompt (run as admin). Replace name.exe with the actual process name — look in the Details tab to find it.
Step 2: Reinstall the app
Once the app is closed, uninstall it via Settings > Apps > Installed apps. Reboot, then install the latest version from the developer's site. If it's a custom app, ask the developer for a version that doesn't rely on the system menu.
Step 3: Run in compatibility mode (for old apps)
If reinstalling doesn't help and you need this old app to work right now, right-click its shortcut > Properties > Compatibility tab. Check Run this program in compatibility mode for: and pick an older Windows version — try Windows 7 or Windows XP SP3. Apply and relaunch.
Step 4: Use Process Monitor to find the exact trigger
If the error keeps popping up but you don't know which app is responsible, download Process Monitor from Microsoft Sysinternals. Set a filter for Result contains NO_SYSTEM_MENU or just ERROR_NO_SYSTEM_MENU. Recreate the error. The log will show the exact process name and path. That's your culprit — uninstall or disable it.
Still stuck? Check these
- Shell extensions: Some right-click menu handlers (like old WinRAR or Dropbox versions) can try to access the system menu. Use
ShellExViewto disable third-party extensions temporarily and test. - Taskbar plugins: If this happens when you click the taskbar, try
Restart Windows Explorerin Task Manager. If it comes back, check for custom taskbar tools (like 7+ Taskbar Tweaker). - Corrupted system files: Run
sfc /scannowin an admin Command Prompt. But honestly, this error is almost never a system file issue — it's an app problem.
Had a client last month whose entire print queue died because of this — turned out their label printing software was trying to open a system menu on a hidden window. Reinstalled the printer driver pack and it vanished. Point is: look at what's running, not what Windows thinks.
Was this solution helpful?