How to check what is causing `explorer.exe` to run inside a Job Object

First, disable all additional background applications, especially hardware vendor tools, gaming utilities, optimizers, antivirus software, and process-management tools.

This does NOT mean that one of these applications is definitely causing the issue. The goal is to test them one by one and see whether the error disappears.

## 1. First, disable applications like these

If you have any of the applications below, fully close them from the system tray near the clock and preferably disable them temporarily from startup.

### MSI

* MSI Center
* MSI Dragon Center
* MSI Afterburner
* MSI Companion
* MSI SDK
* MSI Center SDK
* MSI Gaming Intelligence
* MSI Mystic Light

### ASUS

* Armoury Crate
* ASUS AI Suite
* ASUS GPU Tweak
* ASUS Aura
* Aura Sync
* MyASUS
* ROG Gaming Center

### Gigabyte / AORUS

* Gigabyte Control Center
* APP Center
* EasyTune
* RGB Fusion
* AORUS Engine
* System Information Viewer

### ASRock

* ASRock Motherboard Utility
* A-Tuning
* Polychrome RGB
* Phantom Gaming Tuning

### Acer

* PredatorSense
* NitroSense
* Acer Care Center

### Lenovo

* Lenovo Vantage
* Legion Space
* Legion Toolkit

### Dell / Alienware

* Alienware Command Center
* Dell Optimizer
* Dell SupportAssist
* Dell Power Manager

### HP

* OMEN Gaming Hub
* HP Support Assistant
* HP Wolf Security
* HP System Event Utility

### Razer

* Razer Synapse
* Razer Cortex
* Razer Central

### Corsair

* Corsair iCUE

### Logitech

* Logitech G HUB
* Logitech Options
* Logitech Options+

### SteelSeries

* SteelSeries GG
* SteelSeries Engine

### NZXT

* NZXT CAM

### Cooler Master

* MasterPlus+

### Thermaltake

* TT RGB Plus

### Process management / optimization tools

Pay special attention to:

* Process Lasso
* ParkControl
* Bitsum Process Governor
* System Explorer
* Process Hacker / System Informer
* CPU Limiter
* RAM Limiter
* Intelligent Standby List Cleaner
* Mem Reduct
* Wise Care 365
* Advanced SystemCare
* CCleaner Performance Optimizer
* Glary Utilities
* AVG TuneUp
* Avast Cleanup
* Razer Cortex

### Sandbox / application isolation software

This category is especially important:

* Sandboxie
* Sandboxie Plus
* Comodo Sandbox
* Application Guard
* Shadow Defender
* ReHIPS
* other application isolation tools

### Antivirus / Endpoint Security

For testing purposes, also check third-party security software, especially if both affected PCs use the same product:

* ESET
* Kaspersky
* Bitdefender
* Avast
* AVG
* Norton
* McAfee
* Malwarebytes
* Sophos
* CrowdStrike
* SentinelOne
* Cortex XDR
* FortiClient
* Cisco Secure Endpoint
* Trend Micro
* Webroot
* Comodo
* F-Secure

Do not uninstall them immediately.

First, check whether additional protection modules can be temporarily disabled or whether the application can be fully exited.

On company-managed computers, do not disable security software without administrator approval.

### Parental control / monitoring software

Also check:

* Microsoft Family Safety
* Qustodio
* Norton Family
* Kaspersky Safe Kids
* Family Zone
* Net Nanny
* Bark
* Mobicip

## 2. After disabling the applications

Restart the PC.

After the restart, do not manually start:


* MSI Center
* Armoury Crate
* iCUE
* Razer Synapse
* Process Lasso
* Overwolf
* additional launchers
* optimization tools

Start G1R Multiplayer immediately.

If the error disappears, one of the disabled applications is very likely involved.

Then start the applications one at a time and test the launcher after each one.

---

# Advanced troubleshooting

If simply closing the applications does not help, follow the steps below.

## 3. Check Startup Apps

Press:

`Ctrl + Shift + Esc`

Open:

**Task Manager → Startup apps**

Temporarily disable everything that is not required for Windows itself.

Pay special attention to:

* MSI
* ASUS
* Gigabyte
* Razer
* Corsair
* Logitech
* SteelSeries
* NZXT
* Overwolf
* third-party antivirus software
* optimization tools
* process-management software

Restart the PC and test the launcher again.

---

## 4. Perform a Clean Boot

If the problem still occurs:

Press:

`Win + R`

type:

`msconfig`

and press Enter.

Open the:

**Services**

tab.

VERY IMPORTANT:

Enable:

**Hide all Microsoft services**

Only after that, click:

**Disable all**

Do NOT disable Microsoft services without first enabling that checkbox.

Then go to:

**Startup**

and open Task Manager.

Disable all additional startup applications.

Restart the PC.

After Windows starts, test G1R Multiplayer immediately.

---

## 5. If the launcher works after a Clean Boot

If the launcher starts working correctly, then the cause is very likely a third-party application or service running in the background.

Now re-enable services in small groups.

Example:

Enable 5 services.

Restart.

Test the launcher.

If it still works, enable the next 5.

If the problem comes back, the cause is likely somewhere in the last group you enabled.

Then test those services individually.

This method allows you to identify the exact service or application responsible.

---

## 6. Use Process Explorer

Download the official Microsoft Process Explorer from Sysinternals.

Run it as Administrator.

Find:

`explorer.exe`

Double-click it and inspect its properties.

Pay attention to:

* Parent Process
* Job
* Handles
* Security
* loaded DLLs
* parent/child process relationships

If Explorer is inside a Job Object, Process Explorer may confirm that fact, but it may not always show which application originally created the Job Object.

Windows Job Objects do not contain a simple field like:

`Created by: MSI Center`

That is why Clean Boot testing is often more effective.

---

## 7. If the issue happens on two different PCs

Compare which applications are installed on both systems.

The most interesting applications are the ones both users have in common.

For example, if both users have:

`MSI Center`

or:

`Process Lasso`

or:

`Razer Cortex`

or the same antivirus,

that application should be one of the first things to test.

This does not mean the application is definitely responsible.

It simply means that a shared application on both affected PCs is more suspicious than an application installed on only one of them.

---

## 8. Final test

If nothing helps:

1. Perform a full Windows restart.
2. Do not manually open any applications.
3. Test the launcher immediately.
4. If the error is already present, perform a Clean Boot.
5. If the error disappears after a Clean Boot, identify the service using the elimination method described above.

If `explorer.exe` is still detected inside a Job Object even after a full Clean Boot, then the next things to investigate are:

* Windows system components
* Group Policy
* device management policies
* drivers
* security software running at a very low system level
* corporate endpoint protection

## Most important rules

Do not randomly delete Windows services.

Do not disable Microsoft services.

Do not uninstall everything at once.

Always test in this order:

**disable → restart → test**

Only after you find the specific application or service whose removal or disabling makes the problem disappear should you investigate that component further.