UserOOBEBroker.exe

Windows ProcessMicrosoft Corporation

Also called useroobebroker, oobe broker, out of box experience

WindowsSystem Component

User Out-Of-Box Experience broker. It runs first-sign-in and post-upgrade setup pages, not the everyday desktop.

What you need to know

This is first-run setup. It should not sit in Task Manager weeks after you finished OOBE.

UserOOBEBroker.exe lives under System32\oobe. Microsoft uses it for user OOBE and some post-upgrade experiences. A copy that never exits after you already use the desktop is stuck setup.

Safe?: Yes, during setup pages
Should it stay forever?: No. After OOBE it should go away
Should I end it mid-setup?: You can strand first-run

Feex says

If I am still clicking through "let's finish setting up," this broker is expected. If I have been on the desktop a month, I would not leave OOBE running on purpose.

What is UserOOBEBroker.exe?

UserOOBEBroker.exe is the user OOBE broker. OOBE is Out-Of-Box Experience, the first-sign-in wizard.

What does it do?

It hosts setup pages after a new user or a feature update. It is not LockApp.exe and it is not Settings.

Why is it running?

Windows is finishing device or user setup. A silent broker after you closed every wizard may be a leftover Get Started page.

Is it safe?

Usually safe during setup

System32\oobe\UserOOBEBroker.exe signed by Microsoft is first-run setup. An OOBE exe in Downloads is not that broker.

A legitimate copy normally runs from:

C:\Windows\System32\oobe\UserOOBEBroker.exe

First-run / post-upgrade
Should exit after setup
Not everyday Explorer

Can I end it?

Not during the wizard

Ending it mid-OOBE can skip privacy or account pages and leave a half-configured user. After the desktop is normal, a stuck copy can be ended.

Can I remove it?

Do not delete the System32\oobe folder. The next new user and some post-upgrade pages will fail without this broker.

Should it start with Windows?

Setup starts it. It should not be a permanent Startup app.

Normal resource behavior

These are contextual labels, not universal averages.

CPU: Moderate on setup pages
Network: Account and license pages
Memory: Moderate
Disk: Low

File information

UserOOBEBroker.exe file information
Executable name	UserOOBEBroker.exe
Common legitimate path	C:\Windows\System32\oobe\UserOOBEBroker.exe
Publisher	Microsoft Corporation
Signature expectation	Signed by Microsoft Windows

Common problems

OOBE after every boot

A provisioning package or a broken user profile can retrigger it. That is setup state, not malware named OOBE by itself.

People end it to skip ads

Finish or dismiss Get Started in Settings. Killing the broker mid-page loses the rest of setup too.

Troubleshooting

Diagnose before you change anything destructive.

Finish the pages or sign out and back in

Then see if the broker exits.

Do not replace oobe files

In-box setup binaries.

Technical details

UserOOBEBroker.exe technical details
Image name	UserOOBEBroker.exe
Role	User OOBE broker

Sources and verification

Reviewed by Feex editorial. Last verified August 2026 Status: Feex Reviewed. How we research.

Microsoft Learn: OOBE · Out-of-box experience
Microsoft Support: Windows · Public support naming
Foxhole process map · First-party samples on Windows PCs. Not a lab benchmark.

Was this article useful?

A yes or no is enough. Pick a reason if you want, or add a short note.