100% CPU utilization. /system32/svchost.exe -k dcomlaunch -p. (Windows 11)

jason w butterfield 0 Reputation points
2026-10-09T16:32:14.1066667+00:00

This occurs most frequently while my computer sleeps, I wake it up to 100% CPU utilization. If I kill the process, blue screen. What might cause this issue? How can I nail down the source?

User's image

Windows for home | Windows 11 | Performance and system failures
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Thomas4-N 22,395 Reputation points Microsoft External Staff Moderator
    2026-10-11T08:12:16.2533333+00:00

    Hello jason w butterfield,

    Sorry about the 100% CPU after waking up. The svchost.exe -k DcomLaunch -p process is a shared host. In your screenshot it runs several core Windows services (BrokerInfrastructure, DcomLaunch, Power, PlugPlay and SystemEventsBroker). Windows can't run without those, so the blue screen when you end it is expected. Please don't end it manually.

    This usually points to a driver, a third-party app, or something that wakes the PC, so these are the safest things to try:

    • Install pending Windows updates, then check your PC maker's site for BIOS/UEFI, chipset, Wi-Fi and graphics driver updates.
    • Open an admin Terminal and run powercfg /lastwake. It shows what woke the PC last time. You can also check Event Viewer > Windows Logs > System and filter for the source Power-Troubleshooter.
    • Try a clean boot to rule out third-party software: https://support.microsoft.com/en-us/topic/how-to-perform-a-clean-boot-in-windows-da2f9573-6eec-00ad-2f8a-a97a1807f3dd
    • Check whether it still happens after a full shutdown and start, instead of sleep, to see if it's tied to the resume itself.

    I'd avoid deleting DCOM permission values in the registry or splitting services with sc config. They can break other things and I couldn't find a source that links them to this symptom.

    To narrow it down, could you share:

    • Your Windows version and build (Settings > System > About).
    • Whether it's a desktop or a laptop.
    • What powercfg /a lists (Standby S3 or S0 Low Power Idle).
    • Whether the CPU stays high until you restart, or settles after a few minutes.

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-09T16:32:31.9533333+00:00

    svchost.exe -k DcomLaunch -p is a host process for core Windows services. In the screenshot, it includes BrokerInfrastructure, DcomLaunch, Power, PlugPlay, and SystemEventsBroker. Killing it can cause a bugcheck because it is hosting critical system services.

    To narrow down the source of the 100% CPU after sleep, use this sequence:

    1. Confirm which hosted service is involved
      • Open Task Manager and sort by CPU.
      • If the high-CPU process is svchost.exe, note its PID.
      • Use Process Explorer as administrator.
      • Open the svchost.exe process properties, go to Threads, select the thread consuming high CPU, and select Stack.
      • This shows which functions are active inside that service host.
    2. Capture the problem while it is happening
      • Collect a Windows Performance Recorder (WPR) trace while CPU is high.
      • Keep the recording short because the file grows quickly; a few minutes is enough.
      • Also collect a performance monitor log with a 1-second to 5-second snapshot interval.
    3. Analyze the trace in Windows Performance Analyzer (WPA)
      • Add CPU Usage (Precise).
      • Zoom to the affected time range after resume.
      • Apply Utilization by Process, Thread.
      • Make ReadyThreadStack and CPU Usage (ms) visible.
      • Expand the target process and sort by CPU Usage (ms), Ready (us) [Sum], and Waits (us) [Sum].
      • Expand the relevant NewThreadId and inspect ReadyThreadStack to see whether the thread is running, waiting on I/O, waiting on a timer, or being readied by another thread.
    4. Check whether one service inside the shared host is the trigger
      • If the issue repeats and the offending process is a shared svchost, break out each service into its own svchost temporarily:
         sc config <service name> type= own
      • Restart that service.
      • Run tasklist /svc to verify it is now in its own svchost.
      • Repeat until the high-CPU service is isolated.
      • Important: after testing, revert the change:
         sc config <service name> type= share
      Then restart the service.
    5. Check for a DCOM permission issue if svchost.exe remains the offender
      • In some cases, high CPU for svchost.exe is caused by DCOM permissions.
      • Resetting the DCOM permission stack can help by removing these registry values:
        1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole:"DefaultAccessPermission"
        2. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole:"DefaultLaunchPermission"
        3. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole:"MachineAccessRestriction"
        4. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole:"MachineLaunchRestriction"
      • Warning: incorrect registry changes can cause serious system problems and may require reinstalling Windows.
    6. Use basic CPU triage first
      • In Task Manager, sort by CPU.
      • In Resource Monitor, open the CPU tab and sort by Average CPU.
      • Focus first on the top consumers around the time the system wakes.

    The most direct path is: capture a WPR trace during the post-sleep spike, inspect the hot thread in Process Explorer, then isolate the hosted service if needed by splitting shared svchost services temporarily.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.