LogonUI.exe
Catalog search terms logonui, windows logon user interface, credential ui
Windows Logon User Interface. E dey draw di credential tiles and PIN prompt on top di secure desktop.
Wetin you need know
Dis one dey draw di sign-in tiles. winlogon still get di session.
LogonUI.exe na di credential user interface. E dey show for lock screen and secure desktop. To end am fit freeze di sign-in screen. E no be di session manager.
- E safe?
- Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
- I suppose end am?
- No while you need di lock screen
- Same tin wit winlogon?
- No. Dis one dey draw di tiles
Wetin be LogonUI.exe?
LogonUI.exe na di Windows Logon User Interface Host. E dey render pictures, PIN, password, and Windows Hello prompts on top secure desktop.
Wetin e dey do?
E dey load credential providers. Fingerprint reader from vendor or smart-card package dey plug in here. E no dey start services.exe.
Wetin make am dey run?
Di machine dey locked, dey for Ctrl+Alt+Delete, or dey switch users. You no suppose see busy LogonUI after you don already reach desktop.
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 'LogonUI.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 dis running file
Di real UI host dey inside System32. LogonUI.exe wey dem unpack beside screensaver no be di Windows lock screen.
Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)
C:\Windows\System32\LogonUI.exe
- Expected publisher: Microsoft Corporation
- Dey run on top secure desktop
- winlogon na di parent role
I fit end am?
No
To end LogonUI while PC dey locked fit leave black sign-in screen. E no dey unlock desktop wey hang.
I fit comot am?
No
No delete LogonUI.exe. You go lose di supported way to type password.
E suppose start with Windows?
winlogon dey start LogonUI when credential prompt dey needed. E no be Startup Apps toggle.
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 | LogonUI.exe |
|---|---|
| Recorded installation path | C:\Windows\System32\LogonUI.exe |
| Publisher | Microsoft Corporation |
| Signature check | Inspect the actual file; this entry no dey certify its certificate identity. (pcm) |
Common wahala dem
Black lock screen
Lock-screen image wey break, third-party credential provider, or GPU reset fit make LogonUI blank. Safe Mode na test, no be wipe.
Dey stay after unlock
LogonUI wey remain after desktop appear fit mean say unlock fail. To restart Explorer no go replace dis process.
How to troubleshoot
Diagnose before you change anything wey fit scatter things.
Unload extra credential providers as test
Fingerprint or SSO package fit hang di tiles. Windows password provider suppose still dey work.
Check di lock-screen slideshow
Big OneDrive album as lock background fit make LogonUI look like say e busy. Na di pictures, no be malware wey dem call LogonUI.
Technical details
Technical details
| Image name | LogonUI.exe |
|---|---|
| Role | Credential user interface |
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: Credential providers · Logon UI dey host providers
- Microsoft Support: Windows · Public support naming
- 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.