STATUS_PROCESS_IN_JOB 0X00000124 — what it means and how to fix it

When does this error pop up?

You're trying to run a program — maybe a game, a development tool like a Python script, or a server application — and Windows hits you with STATUS_PROCESS_IN_JOB (0X00000124). The full message says something like: "The specified process is part of a job." This happens most often on Windows 10 and 11, and sometimes on Windows Server 2016/2019/2022.

The typical trigger: you've got a background process that's already running inside a job object. That job object has restrictions set — maybe CPU limits, memory caps, or a rule that prevents new processes from being created. When you try to launch a second copy of that same program (or a related one), Windows checks the job, sees it's already tied to the job, and says "no."

I've also seen this with Task Scheduler tasks that run under a job, with some antivirus suites that wrap processes in jobs for sandboxing, and with debugging tools (like WinDbg) that attach to a process already in a job.

Root cause in plain English

Windows has a feature called a job object. Think of it like a container for processes. It lets you control how much CPU, memory, or time a group of processes can use. It's useful for servers and running untrusted code. But here's the catch: once a process is inside a job, Windows won't let you start another process from that same executable if the job explicitly blocks new processes. The error 0X00000124 is Windows telling you: "This process is already owned by a job. You can't start it again until the job releases it or you kill the original."

The fix isn't complicated, but it's not always obvious. You have to either remove the process from the job, change the job's restrictions, or find out who created the job in the first place.

The fix: step by step

I'm going to give you three methods. Start with Method 1 — it works 80% of the time. If it doesn't, move to Method 2. Method 3 is the nuclear option for stubborn cases.

Method 1: Kill the existing process and restart

1. Open Task Manager. Press Ctrl+Shift+Esc.
2. Go to the Details tab. Look for the program you're trying to run. For example, if it's notepad.exe, find all instances of notepad.exe.
3. Right-click each instance and select End task. Watch for a confirmation dialog — click End process if it appears.
4. Now try launching your program again. If the error's gone, you're done. If not, go to Method 2.

Expected outcome: After killing the process, the job object usually releases its hold. The new process should start clean. If you still see the error, the job is persistent or created by something else.

Method 2: Find and remove the job object manually

1. Open an elevated Command Prompt. Press Win+X, then click Command Prompt (Admin) or Windows Terminal (Admin).
2. Run this command to list all job objects:

   handle -p job

   (You need Sysinternals Handle installed. You can download it from the link, or use the portable version.)
3. Look for the job name that matches your program. It'll look something like \BaseNamedObjects\Job followed by a number or name.
4. Once you've identified the job, run:

   handle -c [job_handle_value]

   Replace [job_handle_value] with the actual handle number from the list. For example, handle -c 0x1234.
5. Confirm you want to close that handle. Then try starting your program.

Expected outcome: Closing the job handle should free the process. If the error still appears, the job is recreated automatically — likely by a service or scheduled task.

Method 3: Disable the service or task that creates the job

1. Press Win+R, type services.msc, and press Enter.
2. Look for services that might be sandboxing processes — examples include Windows Defender, App-V, Windows Sandbox, or any third-party security suite.
3. Right-click the service, select Properties, and set Startup type to Disabled.
4. Click Stop to stop it immediately. Then restart your computer.
5. If the problem doesn't come back, that service was the culprit. You can either leave it disabled or — if you need it — reconfigure it inside the service's settings to allow new processes.

Expected outcome: After disabling the service, the job object won't be created, and your program should run normally.

What to check if it still fails

If you've tried all three methods and the error won't budge, here's what to look at next:

• Check the Event Viewer. Press Win+R, type eventvwr.msc, and go to Windows Logs > System. Look for events with source Kernel-Windows or Job around the time of the error. They often point to the job object's name.
• Look for scheduled tasks. Open Task Scheduler and browse the library for tasks that run your program. Right-click and Disable it temporarily to test.
• Check group policy. If you're on a corporate machine, your IT team may have set policies that enforce job objects for all user processes. You can't override those without admin help.
• Run a clean boot. Disable all non-Microsoft services and startup programs. If the error disappears, turn things back on one by one to find the troublemaker. The exact steps for clean boot are documented on Microsoft's support page.

One last thing: if this happens with a specific application — say, a game or a development tool — check that application's forums. Some programs intentionally use job objects to prevent multiple instances running. The fix might be a config file switch or a command-line flag. For example, Minecraft servers sometimes need -nojline to avoid job-related crashes.

You're not stuck. This error is annoying but fixable. Start with Method 1, work your way through, and you'll have it sorted.