Friday, April 14, 2017

services.msc might not show the effective state if Registry tweaking is in play

A user had written a script to tweak the Registry in a way that changes a service's start type to Manual. When they tried to start it, though, net gave the spiel about it being disabled (or one of its required devices being disabled). The Services MMC snap-in reported the new start type, so it looked like the Registry change did the job.

I did some investigation and found that a once-disabled now-enabled service won't actually start unless it's reconfigured the supported way. services.msc somehow knows about the Registry-tweaked state, but the Service Control Manager isn't fully in on the joke. Since the question author was writing a batch script, sc does the job.

No comments:

Post a Comment