RE: Terrible performance, how to figure out what's causing it?
@rejzor said in Terrible performance, how to figure out what's causing it?:
@blackbird71 And how is telemetry going to tell them that my entire laptop runs like crap? It's not crashing, not having lockups, errors or freezes, it's just horrendously slow for no logical reason. I don't even know who to contact at Microsoft to get it fixed...
The Windows telemetry runs in the background, more or less in bursts all the time; moreover, it uses multiple IP addresses that you will find very difficult to block via a firewall, hosts file, etc. Depending on certain settings options, various kinds and details of data are phoned home. As to many of the specific details, Microsoft has been less than forthcoming. This, in turn, has been the source of many privacy questions and criticisms from users ever since Win10 first emerged.
Moreover, regarding telemetry, Microsoft couldn't care less about your particular system... they're collating data from millions of users looking for various pattern failures that they can then fix before they ship the updates to their more lucrative (and stability-demanding) Enterprise users. Home and Pro users may be able to delay the forced updates for varying amounts of time, but they can't pick and choose among them nearly as easily as in previous Windows versions - hence they can't avoid the early-adopters' problematic ones as easily as in the past. It's more than likely Microsoft's telemetry indeed has data indicating the slowdown on your system after whichever update was involved, but that merely represents a single occurrence to Microsoft. Only if they see enough similar field problems will anything be done to fix/re-build the update for later users, none of which will do your system any good unless the problem is sufficiently widespread.
Microsoft's object in doing this is to use the "free" field testing by users as a substitute for more costly in-house QA testing... but that goal does not include helping a specific user fix a problem caused by one of their updates. Since the 1709 "Fall Update" first emerged last autumn, there have been literally multiple dozens of updates issued (clustered in groups), of which perhaps 10-20 have caused multiple users a wide variety of issues. One of the most common causes have been update conflicts with various hardware drivers on certain systems.
I wish things were otherwise, but sadly they're not. Unless a user is something of a Windows guru, about all they can do is to install the basic Win10 OS and block the Windows update service from functioning. Then the user manually downloads each Win10 update one-at-a-time and checks operation after each to try to find the problematic update. If he finds one, he can "hide" it from the auto-updater's view (for a time period not clearly defined by Microsoft) if he wants to resume allowing the Windows updater to function. It's messy and labor-intensive; but for some users, it's about all they can do unless they know somebody who is skilled and experienced in Windows update problems.