STATUS_APPHELP_BLOCK (0XC000035D) fix: App launch blocked by AppHelp

You double-click an old program you've used for years. Nothing happens. Then you check Event Viewer and see STATUS_APPHELP_BLOCK with code 0XC000035D. This usually happens with programs from the Windows XP or Vista era — like an old accounting tool, a legacy game, or a custom business app. The trigger is often a Windows Update that changed the AppHelp compatibility database, or you recently installed a newer version of Windows 10 or 11 that tightened compatibility checks. The AppHelp dialog showed up, decided the app might cause problems, and cancelled the launch.

What's going on under the hood

The AppHelp service (apphelp.dll) is part of the Program Compatibility Assistant (PCA) in Windows. When you start a program, Windows checks it against a built-in database of known compatibility issues. If it finds a match — say, an app that tries to write to protected system folders or uses an outdated API — it pops up a dialog warning you. If you click "Cancel" or the dialog fails for any reason, Windows kills the process. That dialog cancel is exactly error 0XC000035D.

The real fix isn't just clicking "OK" on the dialog — the dialog might not even appear visibly. The real fix is to bypass or disable the AppHelp check entirely for that app, or globally if you trust your software.

Fix: Disable AppHelp for the problematic program (registry edit)

This is the cleanest fix for a single stubborn app. It tells Windows to skip the AppHelp check for that executable only.

1. Press Windows + R, type regedit, hit Enter. Click Yes if UAC asks.
2. Go to this key:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\
3. Right-click the AppCompatFlags key (the folder), choose New > Key. Name it NoAppHelp.
4. Inside the NoAppHelp key, right-click the right pane, choose New > String Value. Name it the full path to your program's .exe file. For example: C:\Program Files\OldApp\oldapp.exe
5. Double-click that new string value. Set the value data to 1. Click OK.
6. Close Registry Editor. Launch the app again.

After step 6, the program should start without the AppHelp dialog interfering. If it doesn't, double-check the path — if you mistype it, the fix won't apply.

Fix: Turn off Program Compatibility Assistant globally

Use this if the registry fix didn't work, or if you're seeing the error with multiple old programs. This disables the entire AppHelp monitoring service.

1. Press Windows + R, type services.msc, hit Enter.
2. Scroll down to Program Compatibility Assistant Service. Right-click it, choose Properties.
3. In the Startup type dropdown, change from Automatic to Disabled. Click Stop if the service is running.
4. Click Apply, then OK. Restart your PC.
5. Try launching the blocked program again.

Disabling this service stops AppHelp checks for all programs. If you run a lot of legacy apps, it's a trade-off — you lose the occasional helpful compatibility warning. I've had it disabled for years on my own machines without any issues.

Fix: Use the compatibility troubleshooter (built-in Windows tool)

This sometimes works, especially if the AppHelp dialog is actually visible but you missed clicking the right option.

1. Right-click the program's shortcut or .exe file. Choose Properties.
2. Go to the Compatibility tab. Click Run compatibility troubleshooter.
3. Windows will scan the program. It'll show recommended settings. Click Try recommended settings.
4. Click Test the program. If it starts, click Next, then Yes, save these settings.
5. If it still fails, close the troubleshooter. In the Compatibility tab, manually set Run this program in compatibility mode for and pick an older Windows version (Windows 7 or Vista usually works). Click OK.

Fix: Block AppHelp via Group Policy (Windows Pro/Enterprise only)

If you manage multiple PCs, or if the registry edit didn't stick, use Group Policy.

1. Press Windows + R, type gpedit.msc, hit Enter.
2. Go to Computer Configuration > Administrative Templates > Windows Components > Application Compatibility.
3. Double-click Turn off Program Compatibility Assistant.
4. Set it to Enabled. Click OK.
5. Restart your PC.

If the error still shows up after all these steps

That's rare, but possible. Here's what to check next:

• Is the program 16-bit? 16-bit apps won't run on 64-bit Windows at all. Check the file: if the .exe is in a folder called system or was made for Windows 3.1, you need a virtual machine with Windows XP 32-bit.
• Is antivirus blocking it? Temporarily disable your antivirus (or Defender) and try launching. Some security software hooks into AppHelp and can cause the error even after you disable PCA.
• Did a recent Windows Update cause this? Check your Update History. Uninstall the latest cumulative update if the error started right after installing it. Go to Settings > Update & Security > View update history > Uninstall updates.
• Is the program signed with an expired certificate? This can trigger AppHelp too. Right-click the .exe, go to Properties > Digital Signatures. If the signature is invalid, you might need to reinstall an older version of the app.

The vast majority of the time, though, the registry fix (first fix above) solves it. I've used it dozens of times for customers running legacy line-of-business apps. You're fine.