I wanted to use it yesterday on a Win10 machine because DISM was bombing out in a way I've never encountered before, and research suggested to me that something currently running might be messing with it, but because the machine was in a bit of a bad state to begin (a failed WU update apparently caused the machine to not boot and not recover automatically, and only came back online after two system restore attempts) with I didn't want to devote a lot of troubleshooting time to a machine I thought ought to have the nuclear option. a slow-starting computer with a tonne of icons near the clock, with definite crapware giveaways such as "inbox toolbar" or "weatherfox", I'd start by going into CP > Programs & Features, and start uninstalling useless crap after checking it with the customer. I only use msconfig maybe only a few times of year in my line of work, because most home users' computers I encounter act up in ways that I find easier to spot or they just look very typical, e.g. Or a user could use it to steadily re-enable third-party services and apps to try and narrow down the problem, without needing to note down whether a service was set to manual/auto (triggered)/etc to begin with, and also in services.msc there are a lot of services that might never start on a given user's computer. No notes need to be made of what was disabled. So the user hasn't been instructed to do anything potentially destructive, and the process is reversible within as many clicks (maybe 7 at most?).
With msconfig, a techie could guide a user within a few minutes to tell the computer to do a normal Windows boot, but to disable everything that isn't a core Windows service (so more than what safe mode offers, but not starting loads of third party services and apps). Let's say that none of those are causing the problem. With Task Manager, one could disable all of the items in the startup tab, one by one. But most of us know that sometimes there are programs listed there whose startup impact is "high" when that program doesn't actually cause any noticeable impact on startup performance, also it sometimes says "not measured", and also how would one determine "startup impact" exactly? The most obvious metric would be "does it use a lot of processor cycles", however a program could cause a significant startup impact by using a lot of memory but not a lot else, or it could make regular but not not-stop storage requests, or a tonne of other ways that a poorly-written program could cause a machine a lot of grief without necessarily being easy to spot using the 'processes' tab or some other performance monitoring program. Many performance problems exhibit themselves most prominently during the startup routine, so looking at Task Manager's "startup" tab could come in handy (where it tells you the startup impact of that program). So, one might start by looking at Task Manager. Let's say it's a performance problem on a computer that is pretty low spec: It takes a long time to cold boot and settle down. Here's a scenario I might consider using msconfig:Ī computer is doing something doing that one does not regard as a typical problem. At least two other people have pointed out that apps in the startup routine can be disabled in TM, which one could have used msconfig for, but IMHO it's not really msconfig's main purpose. Click to expand.You could try reading the posts above yours, or of course you can make disparaging comments that add nothing of substance to the thread.
0 kommentar(er)
