Clean Boot with msconfig

[jjlandstrom]

And or >> stop all non-MS services that are automatic or manual.

[doug]

Jason – I have to admit that I’m somewhat shocked that you find yourself having to do a selective startup “often” or even just “sometimes” to get Windows Updates to install. I don’t find that to be normal or expected for most environments, and my immediate reaction is what third-party apps are you guys running? (you don’t have to answer that) Seems like maybe there is one app, in particular, that could be the source of most of these types of problems for you. That’s just a guess.

In any case, we will consider options for how this might be able to be integrated into BP. Thank you for the suggestion.

-Doug

[jjlandstrom]

It could just be McAfee getting in the way. I will test it further in next week. Instead of taking the shotgun approach of stopping all services I will try to be more selective in my testing.

When I say often I am only talking about 15% of the systems but when I am patching 100s of systems at a time it can be time consuming. It is often for systems that have not been patched in a long time.

I will gather more info and let you know.

[doug]

I agree that it would certainly be most likely to be something like an AV app or some other similar HIPS/security app that has to really embed itself in the OS in order to work properly.

15% of systems is a lot, so I can understand that it would be time consuming. However, just to give you an idea of my perspective on things, I cannot recall a single time in my entire career where I had to use selective startup to get Windows Updates to be successful. And then also from the BP perspective, we have never had a support ticket where the resolution involved that. I make these points only to highlight that what you’re experiencing is by no means expected or normal behavior, as far as I’m concerned.

Good luck with the troubleshooting.

-Doug

[Author]

Posts