dencorso

Ah! Well. So it's all as it should. Well..., in any case, I'll hid it on my 7 systems, as soon as I boot each (probably next week, if not later on).

You definitely oughtn't to receive KB3065987 for a Win8.x system. It's intended for the 7 codebase. That is really odd!

Yes. Provided you boot from a clean medium (like a Windows PE) and restore the clean backup from there. If you boot from the infected system, then whatever you do may be already compromised.

*** OK. After NoelC chimes in, in case he also agrees, I'll move the posts. *** Now, my quite pessimistic be it this: just after RTM, the numbers of XP, Vista and Win 8.0 will be about unchanged. Those on 8.0 already refused 8.1+ so it's reasonable to suppose they'll keep on 8.0. Now, most of the 7 and almost all the 8.1+ become 10. But I can concoct a more optimistic view, albeit less optmistic than yours: while keeping the numbers of XP, Vista and Win 8.0 about unchanged, let's admit reservation for 7 and 8.1+ was purely random (which surely is not true, but let's suspend disbelief)... if so, half the 7 and half the 8.1+ become 10... that, using the numbers from my original post about this, means, at the very least, 37% Win 10 overnight, which is much more than 8.1+ and 8.0 ever reached, even if considered together! I remain appalled at the sheer crooked brilliancy of it! In summary: "when you cannot seduce 'em anymore, well... simply con 'em!"

**** I can move there some of the posts, say... from my previous one up to here. I thought after I had posted it that there'd be better, but then, I had already posted it, so I waited for y'all's (lol!) reaction, before doing anything. **** Now, both of you're missing my point: it's already done, can't y'all see it? People have accepted a reservation for 10, already. But most peolple are on automatic updates. All MS has to do is just push 10 onto everyone who is on automatic updates and reserved 10. Afterwards, if push comes to shove they can always say: "Oops! Sorry! We regret we misunderstood what you really wanted. But... so deeply sorry yet again: it's irreversible! And your current licence doesn't allow for downgrading either... Oh, well!

Intel PRO/Wireless 2200 driver for Windows98

Consider this: I'm begining to think MS market chief strategist must be Dr. Fu Manchu himself (or Professor Moriarty, or both). You see: 8.x took forever to painstakingly overtake XP. Now 10, which is hands-down more limitating than 8.x will inherit almost all the 8.x *and* *the 7* percentage, overnight, *all at once*, the day 10 goes RTM! And may the die-hards fend for themselves! I can't help but admit: it's brilliant (in a quite crooked way, of course)! And most of the user-base will be foolled into it, no matter what we (who can see it) do, nor how hard we may blow the whistle. 10 is bound to launch capturing ca. 75% of the maketshare at the launch-moment!

After the official launch, the first time one signs out will also be the last: there's a new technology, to be included from the RTM onwards, that, upon sign-out, will cause a local pico-black-hole to briefly form, suck in the miscreant's machine, including monitors, mouse, kbd and any connected external storage, and then dispell subsequently, leaving just a very small puff of crimson smoke and a briefly-lasting strong stink of brimstone. Of course, when asked directly about this, MS denies any knowledge of it, attributing it instead to malicious conspiracy theorists...

The OP, possibly?

@jaclaz: "Just one! A unique handmade piece!"

I've looked at the KB page for KB3065988, it's really another WU update. So, in line with your previous actions, you should accept it. Just, please, dont do it on my say-so, of course. Wuwebv.dll seems to be the Vista+ equivalent of wuweb.dll, which is paramount for the correct working of WU. Most of the occasions when WU ceased to work, in the past, the problem was solved by updating (well... sometimes by downgrading instead) the wuweb.dll. These musings are the best I can offer, right now. Let's wait other 8.1 users chime in, to decide what to do. Maybe someone can offer better insight about it.

Well, you can always check-out at the Hotel California (of course, you won't be able to leave, obviously, however). But, from the MS account, not even that!

They're not alone, however...

+1 Used OCZ Vertex3 do rock, all right! I've got two used 120 GB OCZ Vertex3 in use in my machines!

I thought it'd become a must for every die-hard Dick Tracy fan...

That's a fact I've seen happen, too: not all of them are necessarily offered to every system. It seems that, by hiding some of 'em, other(s) are not even offered. And, of course, at this point in time we have no way, AFAIK, of proactively hiding an update before it's offered. One more reason we must keep eyes wide open.

With all due respect, NoelC, IMO, in order to be consistent, you should also avoid KB3046480 on your Win 7 machine. Is there any reason to hide it just on the 8.1 systems? @Radish: You're welcome! Rest assured I do intend to keep this thread up-to-date.

Probably the mechanical switch is bad. I'm used to see that happen with the left, but it sure depends on which button is used more intensively (I mean: which of the switches gets bad first). The best solution is to replace the offending switch. Altenatively, a debouncer app may help for a time... then again, the only one I know works only for the left button... Anyway, this other thread has all I know about it. Good luck!

This may work: 1.) Get DIMouseHz. 2.) Create a link to it somewhere you can start it easily using the keyboard. 3.) After booting to safe mode, start DIMouseHz. The mouse should start responding. 4.) Click on "OK", to terminate DIMouseHz. The mouse should keep working.

Well... It sure is a reasonably common MS platitude. The words used often vary but, then again, not that much... Here's another variation of it: MS10-036. Please do consider there's about 7 years separating this quote from the one in the post above. Once again, scroll down to the "Frequently Asked Questions"... Yet another one: MS15-005. But, this time, do search for "re-architecture", not "rearchitecture".

Create one full disk backup image using the -z9 -ir coomand line options. After that, create partition backups, preferably monthly, or as needed. -ir produces a blind, byte-by-byte dd-like image, and can only be used for full-disk images. -z9 causes the image to take longer to acquire, but results in the best compression. You may perhaps also want to use also -split=1024 to have the image split in smaller parts. Of course 1024 is just an example, you may select the size you find more appropriate for your case.

Deltron 3030 - 3030 (instrumental version)

That's sure a wise decision, IMO.

Sure! Gimme a list of post #s, and I'll do it gladly.

How can one be sure F-Secure would never take one's first born child or one's most beloved pet, when, in fact, one has agreed for eternity to hand over the same once one signed up for the free WiFi?