Share via

Runtime Broker Error.

Anonymous
2018-06-14T13:35:31+00:00

Windows 10 version 1803 Build 17134.112

I updated PC with 2018-06 CU KB4284835 and now I am getting RunTime Broker.exe error:  The Group or resource is not in the correct state to perform the requested operationwhen I try to open settings (*).  Any suggestions would be greatly appreciated.

Jeff

Windows for home | Windows 10 | Settings

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

13 answers

Sort by: Most helpful
  1. Anonymous
    2018-06-14T14:18:21+00:00

    Hi, Jeffrey57

    This article will help you with your problem

    https://www.tomshardware.co.uk/how-to-fix-runti...

    Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-06-14T20:00:32+00:00

    I booted up PC this afternoon and was able to open start without a runtime broker.exe error. I need to open start and boom runtime broker.exe error. Click OK and it goes away and allows me select setting. More of an annoyance than anything else for me. Wish Microsoft would address this issue.

    Jeff

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2018-06-14T19:19:42+00:00

    Ive had some partial success, bare in mind this is working with fresh clean install off a USB disk 1803  created today so is the latest version.  Fresh install with all drivers only from MS and all updates error still occurred.  Ive managed to get the HP laptop to boot and if you wait about 5 seconds from desktop you wont get the error opening 'settings', if you open it immediately on desktop you will still get it.

    I removed 'skype' app from apps and features.

    I disabled 'Onedrive' from running at startup.

    I also disabled 'tips and notifications' from system (this had no effect on its own)

    I trimmed down 'msconfig' 'services' (hide microsoft) to bare minimum, also disabled notifications from defender and stopped onedrive here also.

    The first two made the difference, the laptop boots so much quicker but this error does occur if you try access settings immediately after booting, not if you give it a few secs.  The operation of the laptop is now so much better but the problem is not rectified fully.

    From what i read 'runtimebroker.exe' had a revamp in version 1803, it now runs separate instances for every app rather just one instance, the overheads always appear to come from 'system services' when viewing 'performance'.

    I cannot believe there are hardly any other posts about this, ive been looking for weeks since 1803 was released and this problem surfaced, i guess its a case of either being patient or hoping for the update fix.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2018-06-14T16:12:56+00:00

    Mark,

    I agree with you. This issue started to appear after my upgrade to 1803. It disappeared until today after Microsoft pushed out there 2018-6 CU. I cringe every time Microsoft pushes out an update because i know that something will get screwed up.

    -Jeff

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2018-06-14T15:21:52+00:00

    This isn't really a valid fix, the error does not occur in version 1709, ive installed 1803 on over 100 pc's and I would say 80% of them have this error after a clean install.  Its a major step backwards in my opinion and not really fit to be put out to market place.

    As a reseller this will cause no end of support problems for me so I refuse to use it until its fixed. 

    The problem sometimes goes away after windows updates, but not on the majority of PC's, this is on brand new model laptops namely the HP 255 G6 range which is new model with AMD A6 CPU. 

    If the fix is that simple why does Microsoft not disable these features from boot and give the choice to enable?

    Was this answer helpful?

    0 comments No comments