Pierwszym problemem który napotkałem przy odpaleniu launchera - Były zabezpieczenia windows. Inteligentne zarządzanie aplikacjami (o ile dobrze z pamięci to napisałem)
> Wyłączyłem te inteligentne zarządzanie,
> Aplikacja się odpaliła,
> Próbuję wejść - "Błąd"
> Wyłączam wszystkie aplikacje
> Błąd.
> Resetuję komputer
> Błąd.
Także pomysłów mam już brak. Dodam że korzystam z launchera Windows x64 launcher. BUILD29
ENG
The first problem I encountered when launching the launcher was Windows security—specifically, "Smart App Control" (or whatever that feature is actually called).
> I disabled Smart App Control,
> The application launched,
> I tried to log in—"Error,"
> I closed all other applications,
> Error.
> I restarted the computer,
> Error.
I’m out of ideas now. I should add that I’m using the Windows x64 launcher (BUILD29).
08-29-2026, 05:56 PM (This post was last modified: 08-29-2026, 06:11 PM by QCherry.)
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
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.