LockApp.exe
Catalog search terms lockapp, lock app, windows lock screen
Windows default lock screen app. E dey show lock image, time, and status while PC dey locked. LogonUI.exe still get di credential tiles.
Wetin you need know
Dis one dey draw di lock wallpaper. LogonUI.exe still be di PIN box.
LockApp.exe na di Lock App package. Windows Spotlight and lock-screen status dey run here. If you end am, lock image fit turn blank. E no dey unlock di PC.
- E safe?
- Check the running file path, signature, and publisher. Name alone no fit confirm say e safe.
- Same tin wit LogonUI?
- No. LogonUI na di sign-in tiles
- High CPU on lock?
- Spotlight or big album fit cause am
Wetin be LockApp.exe?
LockApp.exe na Microsoft.LockApp, di default lock-screen experience.
Wetin e dey do?
E dey show time, detailed status, and Windows Spotlight images. Na LogonUI.exe still dey collect credentials for secure desktop.
Wetin make am dey run?
Di session dey locked, or Windows pre-start di lock package. You no suppose see busy LockApp after you don stay desktop for hours, unless preview dey cached.
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 'LockApp.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 LockApp SystemApps package na Microsoft. LockApp.exe inside "theme" zip no be di lock screen.
Compare the recorded location with the actual file. A familiar folder alone no fit establish identity. (pcm)
C:\Windows\SystemApps\Microsoft.LockApp_*\LockApp.exe
- Lock wallpaper and status
- Credentials: LogonUI.exe
- Spotlight dey use network
I fit end am?
Lock image fit disappear
To end LockApp.exe fit leave blank lock background until e start again. You still dey locked.
I fit comot am?
No
No delete LockApp.exe. Change di lock picture or Spotlight inside Settings > Personalization. LogonUI.exe still get di PIN tiles.
E suppose start with Windows?
To lock di session dey start am. No be 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 | LockApp.exe |
|---|---|
| Recorded installation path | C:\Windows\SystemApps\Microsoft.LockApp_*\LockApp.exe |
| Publisher | Microsoft Corporation |
| Signature check | Inspect the actual file; this entry no dey certify its certificate identity. (pcm) |
Common wahala dem
High CPU while locked
Switch Spotlight off make you take test am. OneDrive album wey dey as lock background fit still cause wahala.
Black lock screen
Restart LockApp, den check di GPU. LogonUI issues na different host.
How to troubleshoot
Diagnose before you change anything wey fit scatter things.
Settings > Personalization > Lock screen
Picture versus Spotlight na di first choice.
No replace LockApp from web
Re-register di package only as repair.
Technical details
Technical details
| Image name | LockApp.exe |
|---|---|
| Role | Default lock screen app |
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 Support: lock screen · Lock App surfaces
- Microsoft Learn: Windows · Primary Windows documentation
- 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.