userinit.exe
Catalog search terms userinit, userinit logon application
Userinit Logon Application. After you sign in, winlogon dey start this file make e fit launch the shell, wey usually be explorer.exe.
Wetin you need know
This one dey start Explorer after logon, then e suppose commot. Any userinit wey never exit need make you check the path.
userinit.exe na the documented logon helper. winlogon dey launch am. E dey start the Userinit value, normally explorer.exe, then e go exit. Persistence malware like this same Run key name well-well.
- E safe?
- Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
- E suppose continue to run?
- E usually dey exit after shell start
- Malware name?
- Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
Wetin be userinit.exe?
userinit.exe na Userinit Logon Application. Na im be the official next hop after winlogon authenticate you.
Wetin e dey do?
E dey restore network connections and e dey start the shell wey dem list inside Userinit registry value. On healthy PC that shell na explorer.exe and userinit go come exit.
Wetin make am dey run?
You just sign in now-now. Copy wey still dey run one hour later na either custom shell replacement or fake path.
Inspect the running instance
Inside Windows PowerShell, this read-only query show matching process IDs, creation times and executable paths on this PC. (pcm)
Get-CimInstance -ClassName Win32_Process | Where-Object { $_.Name -eq 'userinit.exe' } | Select-Object ProcessId, ParentProcessId, CreationDate, Name, ExecutablePath | Format-List
No result or a path we no fit access is inconclusive. Protected processes fit restrict access, and process IDs fit be reused. Keep personal paths local. (pcm)
Use the file-identity guide to compare signatures and product metadata. A filename alone no fit establish safety. (pcm)
E dey safe?
Check the path and how long e dey run
System32 userinit wey dey exit na Windows. Second userinit inside user folder, or Userinit registry value wey dey point to another thing, na the classic persistence trick.
Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)
C:\Windows\System32\userinit.exe
- winlogon na im start am
- Suppose launch explorer.exe and exit
- Path first, then publisher
I fit end am?
Only fake one wey remain
No end the System32 copy during logon. You fit disrupt the desktop start. Long-lived copy from wrong folder na malware action after you don confirm the path.
I fit comot am?
Only fake copy
No delete System32\userinit.exe. Repair the Userinit registry value if the shell no gree start. That one na advanced repair.
E suppose start with Windows?
Logon dey start am once. E no suppose get im own row for Startup Apps.
Measure resource use
| CPU and memory | Compare several observations for the same PID and workload. This entry get no independently measured universal baseline. (pcm) |
|---|---|
| Disk and network | Attribute activity to the actual process and current task; a filename alone no fit establish expected destinations or transfer volume. (pcm) |
File information
| Executable name | userinit.exe |
|---|---|
| Recorded installation path | C:\Windows\System32\userinit.exe |
| Publisher | Microsoft Corporation |
| Signature check | Inspect the actual file; this entry no dey certify its certificate identity. (pcm) |
Common wahala dem
Desktop no ever appear
If dem rewrite Userinit make e skip explorer.exe, you go get empty shell. That one na registry check, no be missing wallpaper.
Two userinit.exe rows
One inside System32 during logon dey normal. One from Temp wey dey stay no normal at all.
How to troubleshoot
Diagnose before you change anything wey fit scatter things.
Open file location immediately
System32 na the only expected answer for the real helper.
No "fix" Userinit from random .reg
Those files na favorite payload.
Technical details
Technical details
| Image name | userinit.exe |
|---|---|
| Role | Logon shell launcher |
Check the identity of running file
A filename alone no fit establish safety. Verify the actual path, signature and product identity. (pcm)
Sources and verification
Recorded source label: August 2026. Dis label no establish independent verification. How we dey do research.
- Microsoft Learn: Winlogon · userinit after authentication
- Microsoft Learn: Run and RunOnce · Userinit related persistence
- Foxhole process map · First-party samples on top Windows PCs. No be lab benchmark.
- Microsoft Sysinternals: Sigcheck · Dey explain how to check file signatures. Dis reference no establish the identity or safety of any particular running file.
- Microsoft: Get-CimInstance · Read-only local process-query method. (pcm)
- Microsoft: Win32_Process properties · Documents process IDs, executable paths, creation dates and parent-ID reuse. (pcm)
Dis article make sense to you?
Yes or no dey enough. Choose reason if you want, or add short note.
Thank you. Dat one dey help us make dis page better.