Windows 10 October 2018 Update rollout now paused

Fredrik · 20 Oct 2018

CarlSD said:

Yep, looks like it has been fixed. Windows Defender loads almost immediately in 1809 here as well. No 'scrolling dots' while it takes it's time figuring out what to do like in it does in 1803.

Just need to find a way to disable the annoying 'popup' from the side which keeps reminding me I have it temporarily disabled (I always temporarily disable Defender when I'm installing new programs or doing a Macrium image, etc.).

I finally took myself the time to actually upgrade to version 1809. Exactly the same problem for me with SecurityCenter as in 1803. I changed the key DelayedAutoStart to zero as I did back in March for 1803 and the problem is gone.

Windows 10 October 2018 Update rollout now paused-event10016.png

f14tomcat · 20 Oct 2018

Fredrik said:

I finally took myself the time to actually upgrade to version 1809. Exactly the same problem for me with SecurityCenter as in 1803. I changed the key DelayedAutoStart to zero as I did back in March for 1803 and the problem is gone.

Curiosity, only. When did you upgrade to 1809 and how did you do it? Thanks.

Dirk Gently · 20 Oct 2018

Fredrik said:

I finally took myself the time to actually upgrade to version 1809. Exactly the same problem for me with SecurityCenter as in 1803. I changed the key DelayedAutoStart to zero as I did back in March for 1803 and the problem is gone.

I've never had this on 1803, but for the few days i spent on 1809 it was common. I also had a torrent of Profile errors under Application on 1809. Other people reported that one too. Event ID 1534:

User Profile Service Event 1534

Anybody here had that one on 1809?

VBF · 20 Oct 2018

Fredrik said:

I finally took myself the time to actually upgrade to version 1809. Exactly the same problem for me with SecurityCenter as in 1803. I changed the key DelayedAutoStart to zero as I did back in March for 1803 and the problem is gone.

I'm not quite sure if you're saying that Event 10016 has gone in 1809. I don't think it's related it to the Security Centre delayed start issue because these Events can appear long after the PC is up and running.
Either way this might be of interest:
Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums

Fredrik · 20 Oct 2018

VBF said:

I'm not quite sure if you're saying that Event 10016 has gone in 1809, but either way this might be of interest:
Why Certain DCOM 10016 Events Don't Matter - Windows 10 Forums

This particular event do matter. It doesn't cause any serious side effects since the services will auto instantiate after 2 minutes but you will see these unnecessary errors in the event log.

Fredrik · 20 Oct 2018

f14tomcat said:

Curiosity, only. When did you upgrade to 1809 and how did you do it? Thanks.

This was an upgrade from 17134 which was clean installed like 2 months ago.

VBF · 20 Oct 2018

Fredrik said:

This particular event do matter. It doesn't cause any serious side effects since the services will auto instantiate after 2 minutes but you will see these unnecessary errors in the event log.

We cross-posted - see my addition "these Events can appear long after the PC is up and running."
I'm interested to understand how you related them to the Security Centre?

f14tomcat · 20 Oct 2018

Fredrik said:

This was an upgrade from 17134 which was clean installed like 2 months ago.

Thanks. I wasn't clear on my question. The 1809....when did you upgrade to it and how? It was released on 10/02 and pulled on 10/05. Did you upgrade between 10/02-10/05 before it was pulled, or some time after, and if so, with what? That's what I was asking. Just trying to get your time-frame clear in my mind.

Fredrik · 20 Oct 2018

VBF said:

We cross-posted - see my addition "these Events can appear long after the PC is up and running."
I'm interested to understand how you related them to the Security Centre?

The classes WscBrokerManager, WscCloudBackupProvider and WscDataProtection depend on service SecurityCenter. They all three try to start early while SecurityCenter is delayed 120 secs. That is why you get a timeout error after exactly 120 secs (give or take a few seconds of grace period).

slicendice · 20 Oct 2018

I hate these Focus Assist Automatic rules. If I set to automatically shut up notifications for games, it also shuts up if I fire up Edge. Edge is not a game.