-
Posts
117 -
Joined
-
Last visited
About Zardoc
-
Rank
Newbie
Profile Information
-
Gender
Male
-
Location
Canada
-
Interests
Mad Scientist
Recent Profile Visitors
1,646 profile views
-
OK, This is what I noticed; When I upgraded to V17 on build 22631.2506 of Windows, after reboot security center starts right away. Same thing for all updates added after the fact up to 22631.2787. If you are running 22631.2787 and then upgrade to v17 then error 16 and then 19 pop up in the viewer and after that a 2 minute delay is noticed (on my machine) before Security Center kicks in on every boot. What I did notice when I upgraded to V17 on build 22631.2506 was that Event error 19 showed up right away but did not cause delays with Security Center. It started right after boot. So there's something funky in V17.
-
@pete12, sometimes we don’t understand the implications of coding, especially with security software. You can’t always say, let’s add a comma to the line and it’s fixed. MS has stringent settings for security and also updates their code on the OS. So, what Joseph explained is that he sees the problem and is trying to see where the code doesn’t align with the Security Center and they will try to fix the problem on their end (if it is their problem). Pushing people to fix something fast is never good. It frustrates everyone and is a waste of time. It’s like making a soufflé. “The hardest part of making a soufflé is when you incorporate the beaten egg white with yolks, and the rest of the batter. You have to be very careful to fold the egg whites slowly, so that they don’t melt.” 😜 When people take their time to fix something, the chances of success are better. Getting an explanation acknowledging the issue and trying to find a fix tells us at least someone knows about it and they will try to fix it as soon as it is possible.