Thanks for the heads up!

Great Info Thx Doc...

Got it fixed.

Thanks for the tip, as always.  For what it's worth my Whitehat Aviator running at stock settings passed fine.  I like the way he did the test, the guy has a sense of humor. 

Thanks for the warning, Doc. I almost stepped in some. All kidding aside, my preferred browser failed as did FF Portable. Chrome portable passed. On my 7 rig, that is as far as I care to go. IE11 with Chrome Portable for a fallback browser.

From these results, I can gather several conclusions.

1: Malware creators love IE, it's the default browser of millions of Windows users. (who know damn little about what's inside that box, tablet, phone, etc.)

2:FartFox is still the failing, memory leaking piece of crap that it was/is, I avoid it like it was ebola.  

3:Scare tactics do drive public opinion. The flock is easily herded

3:The devs at Google either really know their shit or are behind half of this crap. It's a tossup there.

4: I have spent more time responding to your post than most people will. You scared most of them away with that getting technical warning.

5: Lather rinse repeat.

and screw that pooch, I'm a cat person.

 he's just a dog, and he's French

 Not that I hold anything against the French

andiaintgonnauncheckadoggonething

Okay, helping hand needed here.  I use IE and I show as vulernable.  I ran the MS fix it link to disable, do I also run the other link they show to restore or will that just make me vulernable again?

you might want to "restore" when ms comes up with a patch... not sure if win update undo hotfixes before they patch in fixes or not... sometimes hotfixes messes up later winupdates (i think)

but who remembers to unfix stuff, ever?

@ Philly: Just run 51024 which will be the fix for IE. Don't run 51025 which will reverse 51024 and make you vulnerable. The patch, when and if it comes will take care of that for you, because no one ever remembers to 'unfix'.

@ Wiz: After you test and do the fix, clear the browser cache and retest. Or, retest here: https://www.ssllabs.com/ssltest/viewMyClient.html

WC'ers don't scare that easily. 

We could protect ourselves from poodle attacks merely by having pics of cute cats on our desktop?  

@dr  - not convinced that the patching always undo hotfixes 1st... my previous win7 installation (bit corrupted by dying hdd...) had problems with some patches... one of which was caused by a hotfix.. and eventually went through after i tracked it down and undo the hotfix... though this one should be fairly harmless.. just basically the same as unticking the ssl 3 box in ie options, isn't it?

(that said.. ie options is used by plenty of stuff - eg.. steam, chrome..... still.. harmless.. the fix, not the bug )

I don't see why it wouldn't depending on the patch, of course.

Generally, if you're concerned about the question you can get a good deal of info from the technet blog regarding the contents of each patch tuesday or other patches issued off that schedule.

You can do that at this url: https://technet.microsoft.com/security/bulletin or in the blog: http://blogs.technet.com/b/msrc/

You can get advanced notification (if you wish) at this MS site: http://technet.microsoft.com/en-us/security/dd252948.aspx

It informs you of the date of the next release (11/11/2014 for this month) and you can check there (a few days before) if a patch is coming to deal with the issue. If there is, then you can (usually a day or later) undo the fix before dl'ng and installing the patch...

For some reason, the fix for Chrome worked fine on 2 of my Win7 rigs but failed to work on the third.  Even after clearing the cache multiple times and rebooting, still shows as vulnerable.  Odd.

You're sure you typed it in correctly? Maybe opening properties as Admin?