|
"Processes": see Task Manager "Processes", "show all processes", and right down the bottom was all that MS reporting stuff, working frantically as soon as I fired up.
Re Dreamweaver: Hardly a bug in the OS: just some of the call routines thought to be redundant, no doubt, legacy stuff no modern software uses, including the one Dreamweaver 4 of fond memory used. Naturally MS can't cater for all obsolete software; I don't expect it to. But the system is opaque. There can be, and are, unintended consequences. There is never an explanation for what the updates do. And of course coming immediately after the reporting implants hassle, it certainly pushed all my cynicism buttons.
In some umpty years of constant PC use, since Windows 3.1, I have never been hacked. I use good third party protection. I have only once had a virus, and it was a minor one, not stopped by MS but by my third party protection.
Not all Windows updates were for my benefit, as I said. I can see no benefit to me whatsoever in the suite of reporting modules that were added to my system without me knowing until I investigated incredibly slow startups, and intensive uncommanded hard drive and internet activity, when I was doing nothing at all. I was lucky there were people around on the internet who not only knew about it but knew how to kill it too.
Whether the reporting to MS was good or bad was irrelevant to me. The reporting process itself meant that it slowed down my PC disastrously on startup, just when I wanted to get some work done. (I do not and never have left my PC running overnight.) Once I killed off that reporting process, startup returned to normal.
I now check "Processes", "show all processes", regularly, and the reporting module has not returned. I believe, however, it is because I have blocked updates on XP. The first time I went though the lengthy process of eliminating it, which including among many other measures uninstalling a cluster of update numbers, the very next update re-installed the whole lot. The update process, it seems, scans for "missing" update numbers and re-installs them...
Happily, I have Dreamweaver 4 on an ancient XP laptop which hasn't been connected to the internet for many years, and it still works perfectly there. I just have to shift my website stuff over to my working machine by sneaker net whenever I need to monkey around with the frames. No biggie.
|