dencorso

I agree. I see no reason either KB2999226 or KB3118401 should be relevant for the WU Process at all.

I bet Adobe Flash Player 20 can be edited to work on sp2. And when one can run Office 2000, why lose time and get irritated trying to run any later version?

@Yzöwl: I've generated a difference list between my avoided updates and yours... of relevance it seems you've missed skipping KB3050265. If so, do remove it and see whether it causes any different behaviour. Attached is the diff list, for your reference. Compare.pdf

I've updated my Win 7 SP1 Ultimate x64 about two hours ago, and after the usual c. 50 min wait, it found and installed 12 updates. I have avoided all those updates mentioned in my thread about resisting Win 10, plus some I don't list but are on the Aegis list, so basically the same as you have been avoiding, Yzöwl... I'm on IE10, however, if that's relevant.

Flash Player 21.0.0.240 has been released today (ActiveX, NPAPI and PPAPI).

You do rock! And welcome to MSFN! BTW, one can even let the Flash Plugin on "Always Activate", too. It works just the same! Here's the other HTML5 tests - video site: all video types now work!

All you need is the no-install GUI version of the Bulk Rename Utility. You'll do it in a few seconds.

Absolutely... and happily!

Ditto!

That´s not quite true. In fact, all chipsets later than Z68 and X79 have USB 3.0, and Intel never released USB 3.0 drivers for XP or Vista, so support for those chipsets is incomplete.

Since yesterday, it's happening for me, too... In fact, I just got an error 500, while trying to post this very message.

Well, it seems they've previewed it already as a "trash existing Windows 7 update" that's been wreaking havok on Asus motherboards...

May I ask you why?

The Register says: "Official: MS's 'Get Windows 10' nagware to vanish from PCs in July"... Seems almost too good to be true... Should we believe it? Soon we'll know.

What about the updated definitions are exactly the same as for Windows 7? Seems to me to be the likelier reason, if I had to guess...

Well, that's what MSFN is best at: catalysing people at having ideas / finding solutions / improving at found solutions / etc. There sure is some creative synergy in threads like this one, in which almost every post contributes something... it's a kind of colletive brainstorming, which spawns good fruits. And, for sure, this one was a pleasure to participate in. Thank you for starting it!

@mo832: Way to go! Now, just to keep things as together as possible (and also to try to prevent them from falling into the memory hole), I quote here the workaround mentioned by mo832, above:

Worse: it's Apple iBall!

Are you aware that those questions are unanswerable? You see: those in the know (MS employees) won't talk about it, and all others have to use a crystal ball to answer those questions. I cannot, at the moment, because I'm recharging my crystal ball... your previous questions took all the juice it still had in.

Keep on FF 35.1 and call it a day?

Those were general links, for those who know how to use the Wayback Machine... here is the spoonfeeding version (one gets the correct file on the 1st click), instead: 32-bit and 64-bit installers for MSE 4.4.304 from 2014... They are available via the Internet Archive Wayback Machine, just pick the date you want: 32-bit: https://web.archive.org/web/20140114090032/http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/ENUS/x86/MSEInstall.exe 64-bit: https://web.archive.org/web/20140105010501/http://download.microsoft.com/download/A/3/8/A38FFBF2-1122-48B4-AF60-E44F6DC28BD8/ENUS/amd64/MSEInstall.exe

After 7/14/2015 MSE went EoS on XP, which itself was already EoS. Yet, the continued availability of Virus Definitions since then allows one to suppose it'll remain usable, at least until Win 7 SP1 goes EoS. And, even after that, it may be possible to continue using it, since the Virus Definitions for Windows Defender can probably be adapted for MSE. But all this exercise in clarivoyance may be moot, because the future only becomes fixed when it becomes the past, so that we'll all have to wait and see...

Of course he does, because he wants to avoid any dependency on .NET at all, obviously.

You should be able to remove it from Control Panel -> Add or Remove Programs. MSE is quite well behaved in what regards removal, in my experience. After the removal finishes, however, it's a good idea to reboot, before inastalling the older version. Moreover you should set your MS updates to manual, or else it'll update it to version 4.5 or latter via aotomatic updates.