Service Disabled After M$ Critical Updates

  igk 16:52 19 Apr 05

Now I don't know if M$ are trying to be devious here but last Friday I
visited M$ updates and found 5 criticals,I knew these were recent as I check
once a week,so I downloaded & installed them,yesterday I checked M$ again
(call me pedantic/paranoid if you must) and got an error that a required
service was disabled it gave several options that it could be,after looking
in "Services.msc" I found that "Automatic updates service" had been
disabled,after resetting it to "automatic" and revisiting M$ the scan for
updates worked as it should.Now I know that I had not disabled this and on
checking my "error logs" in management I noted that this had started to
happen (error starting DCOM service) just after the critical updates
mentioned at the start of this posting (last Friday)!! Just posting this
in case anyone has the same problem and are wondering what's happened and
also the fix for it.

This thread is now locked and can not be replied to.

Surface Pro (2017) vs Surface Pro 4

20 groundbreaking 3D animation technologies coming to Siggraph 2017

iPad Pro 12.9 vs Surface Pro 5