|
|
|
|
|
|
by ntauthority
1273 days ago
|
|
|
This mentality is a common one I see when people comment on Windows: people setting an override that isn't actually the intended override to 'fix' an issue without root cause analysis by disabling a component, then complaining about the 'intended override' getting reverted with a system upgrade. (and 'impossible using normal GUI/CLI tooling' seems unlikely, for one as regedit is still 'normal tooling' as well, and secondly because I've yet to come across a service that can't be disabled with the 'sc' command line utility, discounting Windows Defender though that is rather a special case due to the chance of malware itself disabling it, so it has a very specific series of steps to first disable the tamper protection in a trusted way and only then disable the service) In this case it seems like an environment-specific issue, as if everyone would have this specific thing be broken, it'd probably long be noticed and fixed. In fact, one could probably easily find out what is wrong using a profiling session with WPR/WPA as the main symptom here is 'uses 100% of a CPU core', a methodology recently most famously spread by Google's Bruce Dawson. (similarly, I wonder if these same people would 'complain' a Linux distro upgrade would affect their edits to /lib/systemd/system/*.service files - I would somewhat presume that to not be the case, in fact) |
|
|
Well, meet WinHttpAutoProxySvc...
And yes, before you dial the condescension up to 11 again, I'm aware of the need to do this from an elevated command prompt, as demonstrated by the fact that it works fine for other services, e.g. Windows Update: (And, for the record, I was not complaining about anything, merely pointing out my environmentally specific experiences with the topic of an article, IMHO also clearly pointing out that my choice of solution is a gross hack and that I should look more closely into the issue one of these days when my copious spare time allows...)