Windows 10 October 2018 Update rollout now paused
-
![]()
Thank you
[FONT="]@[/FONT]Fredrik - now I understand.
The confusion arose because the Event 10016 to which I was referring (and to which the link I posted refers) are of this sort:
Source: Microsoft-Windows-DistributedCOM
Event ID: 10016
Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
THOSE are the ones that the link says do
not matter - I and many other people get those seemingly at random on
1803...I do NOT get the ones you're discussing even through Security Centre delays on startup. So there are 10016 Events and there are 10016 Events!
Maybe you have filtered out the security center events which I have seen been suggested in other foras?
Anyway, the one about Runtime Broker as you mention above may be harmless but it's very annoying with red errors in the event viewer. It certainly doesn't harm to add access for 'Local Service' and 'Users' to RuntimeBroker (D63B10C5-BB46-4990-A94F-E40B9D520160).
[EDIT]: I just realized that the RuntimeBroker has changed reg keys in 1809. It's now called:
CLSID: 2593F8B9-4EAF-457C-B68A-50F6B8EA6B54
APPID: 15C20B67-12E7-4BB6-92BB-7AFF07997402
If you use Google Chrome I advise to allow Local Activation for 'Users' since Chrome execute in a User role sandbox and otherwise triggers an error every time it is started.
-
-
Maybe you have filtered out the security center events which I have seen been suggested in other foras?
Anyway, the one about Runtime Broker as you mention above may be harmless but it's very annoying with red errors in the event viewer. It certainly doesn't harm to add access for 'Local Service' and 'Users' to RuntimeBroker (D63B10C5-BB46-4990-A94F-E40B9D520160).
Actually, I was wrong! I do get the Events to which you allude, but only one of each at Startup time, after which, they stop, for reasons you've already explained! (The 2 minute delay)
I get loads of the others, hence my interest.
So my question to you now is, do the events that I mentioned cease with 1809? If they do, I'll wait until I update (I'm not an Insider), for now, with 1803, I shall continue to ignore them, as the thread suggested.
My apologies for the confusion! 
-
![]()
Actually, I was wrong! I
do get the Events to which you allude, but
only one of each at Startup time, after which, they stop, for reasons you've already explained! (The 2 minute delay)
I get loads of the others, hence my interest.
So my question to you now is, do the events that I mentioned cease with 1809? If they do, I'll wait until I update (I'm not an Insider), for now, with 1803, I shall continue to ignore them, as the thread suggested.
My apologies for the confusion!
Hi again, no these errors persist in 1809. MS restored the 120 sec delay of SecurityCenter start when I upgraded and the errors appeared again. I thought MS had fixed this already ... I discovered this already back in March when I was a test pilot for 1803 and I have reported and suggested the solution in the Feedback Hub several times. It's common sense to NOT delay the SecurityCenter service when at least 3 classes depend on it...
About the other 10016 events, mostly RuntimeBroker and Immersive Shell I don't think MS will correct since it's normally non-Microsoft applications (like Google Chrome) that triggers them.
-
Hi again, no these errors persist in 1809. MS restored the 120 sec delay of SecurityCenter start when I upgraded and the errors appeared again. I thought MS had fixed this already ... I discovered this already back in March when I was a test pilot for 1803 and I have reported and suggested the solution in the Feedback Hub several times. It's common sense to NOT delay the SecurityCenter service when at least 3 classes depend on it...
Thanks again.
I agree with that. I would personally set the Service to Automatic rather than change it via the Registry but tbh just 3 known errors at Startup don't bother me too much.
However, as MS is aware of the others, it's a pity they haven't fixed them instead of officially telling us to ignore or filter them: https://support.microsoft.com/en-us/...windows-server
-
-
Thanks again.
I agree with that. I would personally set the Service to Automatic rather than change it via the Registry but tbh just 3 known errors at Startup don't bother me too much.
However, as MS is aware of the others, it's a pity they haven't fixed them instead of
officially telling us to ignore or filter them:
https://support.microsoft.com/en-us/...windows-server
There might be some obscure security argument that you should not allow Local Activation of the RuntimeBroker for 'Local Service' and 'Users' but I take the risk...
About the SecurityCenter Service - normally you change services from the app of course (services.msc) but this one is not allowed to change from there unless you start services.msc with SYSTEM or TrustedInstaller priviliges. That is why I suggest changing it in the registry instead when it's so easy.
-
I'm not quite sure which drivers you mean? I simply did a total reset, and reinstalled my other software.
When I installed the 1809 update over 1803 I noticed an immediate increase in computer performance on my newer Acer desktop. Since I was planning to completely clean off my hard drive anyways, I hit reset and wiped everything for 1809. Now it runs really good. I still have to wait and see if 1809 changes the performance of my other two computers.
My Dell i5 4 core has always been a nice highway cruiser, until I put 1803 on it. I don't know what it is, I'm not trying to bash 1803, it just doesn't seem to let my computers breath and move like they normally should. As I have already said, my newer Acer duel core is back up to speed now with 1809.
The best thing to do would be to go to Dell's Support site and put the computer's model number in to see what drivers are available.
-
There might be some obscure security argument that you should not allow Local Activation of the RuntimeBroker for 'Local Service' and 'Users' but I take the risk...
About the SecurityCenter Service - normally you change services from the app of course (services.msc) but this one is not allowed to change from there unless you start services.msc with SYSTEM or TrustedInstaller priviliges. That is why I suggest changing it in the registry instead when it's so easy.
Well, well, so you can't! You learn something every day! 
-
The Windows permission settings are a mess. Not even the built in Administrator has acces to pretty much anything, anywhere. Everything is owned by Trusted Installer in the registry and it's a pain to modify something.
What's the point of having a built in Administrator account if he can't do squat when needed?
-
The Windows permission settings are a mess. Not even the built in Administrator has acces to pretty much anything, anywhere. Everything is owned by Trusted Installer in the registry and it's a pain to modify something.
What's the point of having a built in Administrator account if he can't do squat when needed?
Good question! I'd like to know that, too.
-
-
Good question! I'd like to know that, too.
In Linux you just switch or SUDO to ROOT and you can do anything, everywhere. When done, just log off ROOT and switch back to mortal mode. Job done!
