Skip to content

WINDOWS SERVICE

SystemEventsBroker: System Events Broker

Coordinates execution of background work for WinRT applications.

TECHNICAL SUMMARY

Service nameSystemEventsBroker
Display nameSystem Events Broker
Runs fromC:\Windows\System32\svchost.exe
Command linesvchost.exe -k DcomLaunch -p
Runs asLocalSystem
VerdictLeave it alone
Microsoft, Windows Server 2016 guidanceDo not disable (also needed for Task Scheduler and the broker infrastructure service)

Paths, signer and service account observed on Windows 11 build 26300 on 12 November 2026. Run the commands below to check your own PC.

Should you touch it?

Leave it alone

Both of Microsoft's lists rate it Do not disable. Microsoft notes that although its description mentions only WinRT applications, it is also needed for Task Scheduler, the broker infrastructure service and other internal components, and that background work might not be triggered without it. On the PC used for this page it was Automatic and running.

What PC Tweaker does with it

PC Tweaker does not change this service. No control in the catalogue stops it, disables it or edits its start type.

Check it yourself

  1. See its state and start type

    Get-Service SystemEventsBroker | Format-List Name, DisplayName, Status, StartType
    sc qc SystemEventsBroker
    PowerShell

Common questions

What does the SystemEventsBroker service do?

Coordinates execution of background work for WinRT applications. It runs C:\Windows\System32\svchost.exe (svchost.exe -k DcomLaunch -p) as LocalSystem.

Can I disable SystemEventsBroker?

Leave it alone. Both of Microsoft's lists rate it Do not disable. Microsoft notes that although its description mentions only WinRT applications, it is also needed for Task Scheduler, the broker infrastructure service and other internal components, and that background work might not be triggered without it. On the PC used for this page it was Automatic and running.

Which process hosts SystemEventsBroker?

On Windows 11 build 26300 it is registered as svchost.exe -k DcomLaunch -p and loads C:\Windows\System32\SystemEventsBrokerServer.dll, signed by Microsoft Windows. The same svchost.exe process hosted BrokerInfrastructure, DcomLaunch, PlugPlay and Power.

What does it depend on?

On build 26300 it depends on RpcEptMapper and RpcSs, runs as LocalSystem and has a trigger registered. sc qc SystemEventsBroker prints the same on your PC.