Beta

×

Welcome to the Slashdot Beta site -- learn more here. Use the link in the footer or click here to return to the Classic version of Slashdot.

Thank you!

Before you choose to head back to the Classic look of the site, we'd appreciate it if you share your thoughts on the Beta; your feedback is what drives our ongoing development.

Beta is different and we value you taking the time to try it out. Please take a look at the changes we've made in Beta and  learn more about it. Thanks for reading, and for making the site better!

Microsoft Telling Users To Uninstall Bad Patch

Soulskill posted about a year ago | from the but-thanks-for-testing-it dept.

Microsoft 154

msm1267 writes "Microsoft announced last night that it has stopped pushing a security update originally released on Patch Tuesday because the fix is causing some PCs to blue-screen. Microsoft recommends users uninstall the patch, which is also causing compatibility issues with some endpoint security software. MS13-036 was part of this week's Patch Tuesday update. It addressed three vulnerabilities in the Windows Kernel-Mode Driver, which if exploited could allow an attacker to elevate their privileges on a compromised machine. Users began reporting issues earlier this week with some systems failing to recover from restarts, or applications failing to load, after the patch was installed."

cancel ×

154 comments

Sorry! There are no comments related to the filter you selected.

Points at Microsoft (0, Funny)

Anonymous Coward | about a year ago | (#43432745)

Hideki!

Re:Points at Microsoft (1, Funny)

Chris Mattern (191822) | about a year ago | (#43432857)

Hideki!

Chi!

Re:Points at Microsoft (0)

flimflammer (956759) | about a year ago | (#43433451)

Well that's a new one.

Re:Points at Microsoft (0)

Anonymous Coward | about a year ago | (#43434275)

There's so few people that will understand the significance...
So funny though ;-)

Here's how to uninstall it.. (5, Informative)

americamatrix (658742) | about a year ago | (#43432769)

Just incase your having the problem, here is the easiest way to uninstall the update.

Open an elevated Command Prompt and type "wusa.exe /uninstall /kb:2823324 /quiet /norestart" without the quotes.

You should be good to go now :)


-americamatrix

Re:Here's how to uninstall it.. (5, Funny)

Anonymous Coward | about a year ago | (#43432909)

I thought it was:

  • 0) unlock secure boot
  • 1) reboot to FreeDOS
  • 2) format C: /q
  • 3) install another OS

Windows 8 itself is the "patch" no?

Re:Here's how to uninstall it.. (1)

Anonymous Coward | about a year ago | (#43433177)

That's definitely not the easiest, that's what you do when you're too fucking stupid to fix the problem by uninstalling the patch.

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433219)

Are you sure it's not a driver problem? Most Windows bluescreens are driver problems.

Re:Here's how to uninstall it.. (5, Funny)

Anonymous Coward | about a year ago | (#43433249)

Have you tried turning it off and then on again?

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433331)

It's probably a hardware fault.

Re:Here's how to uninstall it.. (2)

Molochi (555357) | about a year ago | (#43433393)

Remember, you need to restart the machine three times.

Re:Here's how to uninstall it.. (1)

GigaBurglar (2465952) | about a year ago | (#43433335)

cleer ur cashey

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433515)

I must be dumb.

How do you uninstall the patch at a bluescreen?

Re:Here's how to uninstall it.. (1)

HybridST (894157) | about a year ago | (#43433721)

I use an eight-pound sledge myself. YMMV.

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433879)

You're referring to the typical freetard M$ hater. Which is all we have on this site.

Re:Here's how to uninstall it.. (2)

GigaBurglar (2465952) | about a year ago | (#43433333)

It's actually easier to take a leaf out of the book of the majority and forgo updating at all; indefinitely.

Re:Here's how to uninstall it.. (5, Funny)

Anonymous Coward | about a year ago | (#43432921)

How is that easier than navigating through four dozen menus and dialogs of advanced options? I really don't understand you command-line people.

Re:Here's how to uninstall it.. (-1)

Anonymous Coward | about a year ago | (#43433075)

It's one step. Navigating through four dozen menus and dialogs is four dozen steps.

Re:Here's how to uninstall it.. (5, Funny)

Anonymous Coward | about a year ago | (#43433101)

You missed the whoosh step.

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433685)

What happens when the Russians remove this patch?

Re:Here's how to uninstall it.. (1)

synapse7 (1075571) | about a year ago | (#43433429)

Then sifting through the list(is it even sortable) of installed updates for the proper kb to be removed.

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433641)

As a certified MCSE, I would like to know where to click.

Terminals are for *nix fanbois.

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433747)

Please include screenshots.

And, blur out your private LAN IP address so the hackers don't get you!

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43432955)

I typed "wusa.exe /uninstall /kb:2823324 /quiet /norestart" without the quotes.

And windows said 'The filename, directory name, or volume label syntax is incorrect.' - without the single quotes.

Geesh, I should just stay with Linux - it's so much easier!

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433701)

>

Geesh, I should just stay with Linux - it's so much easier!

Did you try rebooting?

Re:Here's how to uninstall it.. (5, Insightful)

Toreo asesino (951231) | about a year ago | (#43433143)

Kudos for providing some actual useful info for an MS product on Slashdot. Unfortunately it's a rarity around these parts.

Re:Here's how to uninstall it.. (-1)

Anonymous Coward | about a year ago | (#43433273)

Well, Microsoft chose to saturate Slashdot discussions with marketing people. What did you expect?

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433969)

Well, Microsoft chose to saturate Slashdot discussions with marketing people. What did you expect?

FWIW, as a former employee -- posting in any social media anything related to your job or the company is a fireable offense if you do so without regularly disclosing that you work for Microsoft.

There is *precisely* 0% chance there's any Microsoft marketing people in discussions here, commenting on anything related to Microsoft, without disclosing that. People are regularly fired for it.

Re:Here's how to uninstall it.. (1)

Anonymous Coward | about a year ago | (#43434187)

And killing people is a capital offense, yet the government has people whose job it is to kill. I bet MS has professional trolls who are exempt from your rule.

Re:Here's how to uninstall it.. (1)

rot26 (240034) | about a year ago | (#43434189)

How could anyone be fired for doing something that 0% of them do?

Re:Here's how to uninstall it.. (1)

hawkinspeter (831501) | about a year ago | (#43434399)

That's why they outsource it to a different company. They're not employed directly by Microsoft, so they don't have to disclose anything.

Re:Here's how to uninstall it.. (2)

hairyfeet (841228) | about a year ago | (#43433539)

What is useful? Another posted his CLI doesn't work, and for another neither he nor MSFT said WHAT HARDWARE CAUSES THE FAULT which frankly without THAT knowledge is worth fuck and all because I've applied the patch to a couple dozen bog standard desktops and laptops and? I got nothing. Its gotta either be a funky driver or a piece of funky hardware that is causing this because if its anything bog standard I usually run into it but so far AMD, Intel and Nvidia graphics, Realtek and Sigmatel sound, AMD and Intel chipsets (don't have any Nvidia chipsets on hand ATM) and I haven't seen squat, just been another patch Tues round here.

Oh I did have to reboot my old nettop a couple of times but considering the fact the hard drive already has some bad sectors and the entire system is older than dirt and I'm just waiting on the hardware to finally die because i REALLY don't want to deal with one of my own machines on top of all the other machines I got to deal with? I honestly can't say it was the patch, might have just tried to write to a failing sector. Its an old XP box and XP never was great at dealing with failing sectors...meh its working fine now, left it on for 3 days and its still going when I came in so who cares.

So if anybody knows what actual hardware or software actually causes the thing it would be nice to know, then I'd at least know if any of these systems are at risk, because right now they seem to be running fine and the 2 that got picked up I haven't heard squat from the owners so I'm guessing they are running fine as well.

Re:Here's how to uninstall it.. (2)

TheRealMindChild (743925) | about a year ago | (#43433733)

Well, they may not be able to single out exact hardware, just some examples which fail. This patch was to win32k.sys which, among other things, provides the hardware abstraction layer to the NT/Win32 API. It could have made assumptions that turned out not true on corner-case hardware, could have been a problem with actual buggy hardware that didn't follow published specs (not uncommon), or any number of crazy things.

Re:Here's how to uninstall it.. (1)

Tharkkun (2605613) | about a year ago | (#43433903)

What is useful? Another posted his CLI doesn't work, and for another neither he nor MSFT said WHAT HARDWARE CAUSES THE FAULT which frankly without THAT knowledge is worth fuck and all because I've applied the patch to a couple dozen bog standard desktops and laptops and? I got nothing. Its gotta either be a funky driver or a piece of funky hardware that is causing this because if its anything bog standard I usually run into it but so far AMD, Intel and Nvidia graphics, Realtek and Sigmatel sound, AMD and Intel chipsets (don't have any Nvidia chipsets on hand ATM) and I haven't seen squat, just been another patch Tues round here.

Oh I did have to reboot my old nettop a couple of times but considering the fact the hard drive already has some bad sectors and the entire system is older than dirt and I'm just waiting on the hardware to finally die because i REALLY don't want to deal with one of my own machines on top of all the other machines I got to deal with? I honestly can't say it was the patch, might have just tried to write to a failing sector. Its an old XP box and XP never was great at dealing with failing sectors...meh its working fine now, left it on for 3 days and its still going when I came in so who cares.

So if anybody knows what actual hardware or software actually causes the thing it would be nice to know, then I'd at least know if any of these systems are at risk, because right now they seem to be running fine and the 2 that got picked up I haven't heard squat from the owners so I'm guessing they are running fine as well.

The article says it's conflicting with certain endpoint security software. That would be antivirus or encryption and I know from using McAfee EPE modifying a kernel driver can cause your machine to blue screen. So it makes perfect sense. Then again if you have an Endpoint Encryption suite running and you aren't testing your Windows updates prior to pushing them you should be asking yourself if you're qualified to do your job.

Re:Here's how to uninstall it.. (5, Informative)

Anonymous Coward | about a year ago | (#43433297)

The command in americamatrix’s post is intended for use after you’ve install the windows update(s), but before you’ve rebooted your system to fully apply them. It may also work after rebooting if the update doesn’t prevent a successful reboot, but does cause other problems (e.g. causing Kapersky to lose its license). It’s basically the same thing as using the Programs Control Panel “View Install Updates” feature to uninstall it.

Also, I’d recommend leaving off the “/quiet” flag so that you get some comforting feedback that it has actually worked. So: “wusa /uninstall /kb:2823324 /norestart” (no need for “.exe” either, of course).

If you’ve already rebooted your system and now cannot get into it because of the update (symptoms may include a false indication of file system corruption on a hard drive [Event ID 55], STOP: c000021a {Fatal System Error} status 0xC000003a, or “Windows failed to start Status: 0xc000000e”), there are other ways to remove it, involving either using System Restore or Boot to Command Prompt and issuing a command.

Full details at: http://support.microsoft.com/kb/2839011 [microsoft.com]

Note that this update is apparently only applied to systems running Windows 7 pre-SP1 or SP1, Windows Server 2008 R2 pre-SP1 or SP1, or Windows Server 2008 non-R2 SP2 (any edition of any of these). If you’re running Windows XP, Vista, or 8, presumably this won’t be an issue as the update would never even have been offered via Windows Update.

Re:Here's how to uninstall it.. (1)

Thornburg (264444) | about a year ago | (#43433545)

Note that this update is apparently only applied to systems running Windows 7 pre-SP1 or SP1, Windows Server 2008 R2 pre-SP1 or SP1, or Windows Server 2008 non-R2 SP2 (any edition of any of these). If you’re running Windows XP, Vista, or 8, presumably this won’t be an issue as the update would never even have been offered via Windows Update.

If that's the case, then why does the linked bulletin list every version of Windows under the sun (including RT and Server 2012!) as affected?

Re:Here's how to uninstall it.. (1)

toph2223 (887611) | about a year ago | (#43433713)

Nice work man.. Really appreciate that :D

Re:Here's how to uninstall it.. (1)

AnotherAnonymousUser (972204) | about a year ago | (#43433745)

Most helpful comment on Slashdot ever!

Re:Here's how to uninstall it.. (1)

Sponge Bath (413667) | about a year ago | (#43433913)

Why would you want to uninstall this Blue Screen of Defense security patch? Nothing is more secure than a non-functioning system.

Re:Here's how to uninstall it.. (0)

Anonymous Coward | about a year ago | (#43433949)

Just incase your having the problem, here is the easiest way to uninstall the update.

Open an elevated Command Prompt and type "wusa.exe /uninstall /kb:2823324 /quiet /norestart" without the quotes.

You should be good to go now :)

-americamatrix

Here's the MS article on how to remove the patch: http://support.microsoft.com/kb/2839011

One driver eh? (0, Redundant)

BitZtream (692029) | about a year ago | (#43432775)

It addressed three vulnerabilities in the Windows Kernel-Mode Driver

The? When did their become ONE 'driver' for all of windows?

Not that its the editor or submitters fault, its that way in the actual KB article.

Apparently MS has hired the slashdot guys to edit/approve new knowledge base entires.

Re:One driver eh? (2, Insightful)

BitZtream (692029) | about a year ago | (#43432797)

FAIL ... yes, I know, if you're going to edit troll it helps if you can post a properly written post yourself ... I failed :(

Re:One driver eh? (2)

Jaktar (975138) | about a year ago | (#43433425)

The original knowledge base article which is linked to the fix contains the kernel mode drivers. It makes sense in the context of the linked articles, so the fault with the confusion lies with threatpost.com for not providing all the relevant information.

This link is the knowledge base article in question:
https://support.microsoft.com/kb/2829996 [microsoft.com]

The kernel mode drivers are: ntfs.sys and win32k.sys.

I guess that's what happens when you use a summary of a bugfix to write an article.

Re:One driver eh? (0)

Anonymous Coward | about a year ago | (#43433427)

One Driver to rule them all, One Driver to find them,
One Driver to bring them all and in the darkness bind them

Reminds me of another patch . . . (4, Interesting)

smooth wombat (796938) | about a year ago | (#43432815)

Microsoft put out years ago which killed ones network connection.

The solution? Go back to Microsoft's site to get the updated patch.

Erm, yeah. Great idea. You kill my network connection then want me to go back to your site to fix the issue.

So much for the vaunted "best and brightest" following standard project processes such as TESTING.

Re:Reminds me of another patch . . . (5, Funny)

Anonymous Coward | about a year ago | (#43432881)

Hello. My name is Anonymous Coward. You killed my network connection. Prepare to die.

Re:Reminds me of another patch . . . (3, Funny)

Endo13 (1000782) | about a year ago | (#43433059)

STOP SAYING THAT!

Re:Reminds me of another patch . . . (2)

interval1066 (668936) | about a year ago | (#43434387)

I doan thin that word means wat you thin it means.

Re:Reminds me of another patch . . . (1)

Anonymous Coward | about a year ago | (#43433027)

It turned out it killed the network connection /except for the Administrator account/ so downloading the fix was very feasible.

Re:Reminds me of another patch . . . (0)

Anonymous Coward | about a year ago | (#43433837)

Very?

You must not manage many boxes.

Re:Reminds me of another patch . . . (1)

lord_rob the only on (859100) | about a year ago | (#43433607)

If you have problems with your network, contact your company's IT team by email.
(ok stupid joke I know, couldn't resist :)

Re:Reminds me of another patch . . . (1)

green1 (322787) | about a year ago | (#43433857)

If only my company would figure out that this is a joke! They frequently send us emails to notify us that the network is down and not to call support because they are aware of it... Great idea guys, but if I could get to my email I wouldn't be calling support!

Why I never auto-install updates (5, Interesting)

Anonymous Coward | about a year ago | (#43432847)

I set Windows Update to notify and download updates, but never to auto-install them. I also usually hold updates a few days before installing. Use the same policy with my Linux boxes and have never run into problems.

Re:Why I never auto-install updates (3, Insightful)

O('_')O_Bush (1162487) | about a year ago | (#43432879)

That is a good strategy, but, unfortunately, many of us using business computers (issued laptops, etc) don't have that kind of control over the update policy.

Re:Why I never auto-install updates (4, Insightful)

Endo13 (1000782) | about a year ago | (#43433021)

And if your business is worth a shit, their own strategy is even more careful and rigorous than what the GP posted.

Re:Why I never auto-install updates (0)

Anonymous Coward | about a year ago | (#43433079)

You mean they are still using Windows XP?

Re:Why I never auto-install updates (0)

Anonymous Coward | about a year ago | (#43433227)

If you're using 'business computers', got affected by this and feel more than a little peeved, lighten up. You now, at last, have a legitimate reason to bash your sysadmin. Of course legitimately bashing sysadmins is a once-in-a-lifetime experience (for he will smash you right into the concrete with his full plate armoured cherry keyboard), so be sure to make the most out of it.
--
Just to avoid any liability issues:
THIS ADVICE IS PROVIDED BY 'ANONYMOUS COWARD' ''AS IS'' AND ANY EXPRESS OR IMPLIED YADA YADA YADA, ARE DISCLAIMED. IN NO EVENT SHALL 'ANONYMOUS COWARD' BE LIABLE FOR ANY ... THING AT ALL (YOU KNOW THE DRILL) HOWEVER CAUSED, EVEN IF ADVISED OF THE POSSIBILITY OF YEAH, WHATEVER.

Re:Why I never auto-install updates (1)

ultranova (717540) | about a year ago | (#43433283)

But then again, is a problem with an issued computer your problem? Surely you have your own computer and only use the business computer for business matters? Who knows what spyware it might have, after all.

Re:Why I never auto-install updates (1)

Frontier Owner (2616587) | about a year ago | (#43433315)

That is a good strategy, but, unfortunately, many of us using business computers (issued laptops, etc) don't have that kind of control over the update policy.

or better yet, windows update is disabled. We only get updated when out IT department deems it necessary.

Re:Why I never auto-install updates (1)

The Rizz (1319) | about a year ago | (#43433257)

I do the same. Unfortunately, Windows will attempt to install them by default whenever you shut down the computer - you have to choose a special "shut down without installing" option while there are any critical updates waiting for install.

Re:Why I never auto-install updates (0)

Anonymous Coward | about a year ago | (#43433707)

Then you should use one of the other settings that doesn't do that. It's not hard but don't let me interrupt your FUD.

Re:Why I never auto-install updates (1)

datavirtue (1104259) | about a year ago | (#43434371)

Yeah, Windows 8 will straight sneak up and fuck you. On my laptop I've started it up to find that updates where applying-- half a fucking hour until I could use my laptop. What if If I was popping it open top start a [presentation? This has happened several times now without notification of any kind.

Re:Why I never auto-install updates (1)

Brucelet (1857158) | about a year ago | (#43433359)

Exactly! Wait for the first adopters, or "gamma testers", to demonstrate that something is actually safe to use.

Re:Why I never auto-install updates (0)

Anonymous Coward | about a year ago | (#43433759)

How many times your systems have been infiltrated during this time? For some vulnerabilities, the window of protection is less than 45 minutes.

something is causing windows to bluescreen (-1, Redundant)

nimbius (983462) | about a year ago | (#43432889)

...slow day for news on slashdot eh?

Re:something is causing windows to bluescreen (0)

Anonymous Coward | about a year ago | (#43432957)

1999 just called...

Re:something is causing windows to bluescreen (0)

Anonymous Coward | about a year ago | (#43433123)

Re:something is causing windows to bluescreen (1)

Anonymous Coward | about a year ago | (#43433269)

Quick! While you have them on the line, tell them about 9/11, the 2004 Boxing Day Tsunami, the 2010 Haiti Earthquake, 2011 Thoku earthquake / tsunami and Fukushima Daiichi disaster! Oh, and see if you can have them drop a note in the mail to 1999 me that says "12-03-30: 46-23-38-04-02/M23", he'll know what to do with it.

Re:something is causing windows to bluescreen (1)

flimflammer (956759) | about a year ago | (#43433489)

No, fuck that. I don't want the future to change and all humans growing like spider legs or something.

So, based on the linked garb, this only... (1)

gatesstillborg (2633899) | about a year ago | (#43432987)

...affects Vista, 7, /Server? Shoot, perhaps we're already seeing the impact of failing to support XP! :)

Windows versions affected (3, Interesting)

felipou (2748041) | about a year ago | (#43432989)

All versions of Windows since Windows XP are affected! How much code from Windows XP is still used in Windows 8??

Re:Windows versions affected (5, Insightful)

gewalker (57809) | about a year ago | (#43433069)

I don't know that answer, but I would hope that the answer was "quite a lot of it". Old cold is not bad code, it is the code that has generally stood the test of time. Not that it is defect free, but that the defect rates are generally lower than the newly written code. Even such basic steps as recompiling for 64-bit, causes new breakage (old code was defective, but the problem was masked). This appears likely to be one of those old problems that became unmasked with the latest patch.

Re:Windows versions affected (5, Funny)

Dins (2538550) | about a year ago | (#43433113)

How much code from Windows XP is still used in Windows 8??

You know how chimpanzees share something like 98% of their DNA with humans? It's like that...

Re:Windows versions affected (2)

Minwee (522556) | about a year ago | (#43433271)

You know how chimpanzees share something like 98% of their DNA with humans? It's like that...

Has anyone told Prenda Law about this? Those chimpanzees may have to pay a bundle to avoid being sued for all that unauthorized sharing.

Re:Windows versions affected (1)

GigaBurglar (2465952) | about a year ago | (#43433363)

And 50% with a banana - you are what you eat as 'they' say..

Re:Windows versions affected (1)

Anonymous Coward | about a year ago | (#43433195)

It's a kernel mode driver change/error. It would be like God doing a bad update on hydrogen.

Re:Windows versions affected (0)

Anonymous Coward | about a year ago | (#43433433)

Hey, maybe that's where our form of matter came from!

Re:Windows versions affected (1)

mikazo (1028930) | about a year ago | (#43433465)

You'd be surprised to find that some old code from 16-bit Windows is still kicking around in Windows 8... things just get ported to the next OS so that they work. Code is only re-written or developed from scratch if it's for new features or the old code was so broken or impossible to port that it had to be re-written.

Re:Windows versions affected (1)

Ravaldy (2621787) | about a year ago | (#43434109)

I would think that whatever didn't need changing would use the same code. You wouldn't recode the calculator if it worked.

Good Thing (0)

Anonymous Coward | about a year ago | (#43433139)

Nothing critical runs on Windows. Not the NYSE, the NASDAQ, Tokyo, London, Hong Kong, Shanghai, TMX, or NSA. And the backend systems are major banks aren't keeping track of assets and currency with Windows, either... are they!? Is that what happened to the EU?!

Damn it, Microsoft. At least you haven't, "meddled with the primal forces of natures." [youtube.com]

Wait... are they using Windows at CERN?

Bad Patch? (0)

Anonymous Coward | about a year ago | (#43433349)

Is that the code name for Windows 8?
*ba-dum-dump-ching!"

Thank you, thank you, I'll be here all week with material as fresh as the buffet! Please remember to tip your waiters & waitresses!

Running NTFS.SYS version 6.1.7601.18106 (0)

Anonymous Coward | about a year ago | (#43433379)

Just fine here, oddly enough, no problems on reboots etc./et al here @ all, whatsoever, on Windows 7 64-bit...

* Upon manually installing my updates for this past "Patch Tuesday" here, 1 was "rejected" as "does not apply to your operating system version" (something very along those lines was the specific err message/abend)!

(Thus, fact is, I'd wager possibly that THAT was the very one that didn't install here (luckily enough I guess)).

I.E.-> No failure to reboot properly etc. here @ all, whatsoever, with THAT particular NTFS.SYS file version in place...

APK

P.S.=> The article from Microsoft states these facts as to proper version numbers for Windows 7 64-bit near as I am able to tell from reading there cursorily @ this point @ least:

FROM -> http://support.microsoft.com/kb/2823324?wa=wsignin1.0 [microsoft.com]

Ntfs.sys
6.1.7601.18106
1,655,656
02-Mar-2013
06:04
x64

& the NTFS.SYS filesystem driver version reported here by rightclicking on the NTFS.SYS file (under %Windir%\system32\drivers) says the exact same... & just judging by that date, I never got the "updated" (downdated really) version to install, per what I noted above about 1 hotfix NOT installing here!

... apk

Re:Running NTFS.SYS version 6.1.7601.18106 (0)

Anonymous Coward | about a year ago | (#43433615)

I hope you've blacklisted microsoft.com in your HOSTS file, too! Otherwise you might still inadvertently get the update!

Some "FYI" for you trolling noob... apk (0)

Anonymous Coward | about a year ago | (#43433705)

It's IMPOSSIBLE for me to block out MS updates sites in hosts... how/why:

Per my subject-line: Microsoft bypasses hosts:

http://slashdot.org/story/06/04/16/1351217/microsoft-bypasses-hosts-file [slashdot.org]

Albeit (& iirc), for purposes of Windows Update functionality to be accurate, to THEIR servers only @ certain IP addresses (iirc)... e.g.:

---

DomainScreenList:

      windowsupdate.microsoft.com
      windowsupdate.com
      microsoftupdate.com
      download.microsoft.com
      update.microsoft.com

HostsScreenList:

      microsoft.com
      www.microsoft.com
      support.microsoft.com
      wustats.microsoft.com
      microsoftupdate.microsoft.com
      office.microsoft.com
      msdn.microsoft.com
      go.microsoft.com
      msn.com
      www.msn.com
      msdn.com
      www.msdn.com

---

Thus?

Well - YOU FAIL, as always, troll... lol!

APK

P.S.=> "No small wonder" you attempt to 'troll me' by your ac posts though - you ALWAYS "blow it", and you know it, on the technicals involved, every single time!

Additionally: Yes, I know it's YOU, Jeremiah Cornelius that's doing it (since you slipped up & posted your 100's of trolls by AC regarding myself, here -> http://slashdot.org/comments.pl?sid=3581857&cid=43276741 [slashdot.org] BUT, that time you submitted it as your registered 'luser' name, Jeremiah Cornelius, giving away you're nothing but a TROLLING scum on /.)...

... apk

Re:Some "FYI" for you trolling noob... apk (0)

Anonymous Coward | about a year ago | (#43433833)

You're correct. It was Jeremiah Cornelius. Everyone's downmodding him as a troll in all of his posts now for spamming us continually last month, and so now he's complaining about it here http://slashdot.org/comments.pl?sid=3636015&cid=43426361 [slashdot.org] that's ironic.

That idiot Jeremiah Cornelius spammed this forums in every news article accepted noting you in it, as his trolling 1st post spam posts, and yes, he did give away he was doing it all through March 2013 when he submitted it under his registered username here http://slashdot.org/comments.pl?sid=3581857&cid=43276741 [slashdot.org] instead of by his usual anonymous coward posts by the 100's last month.

He's getting what he deserves and is complaining? How ironic. Seems troll Jeremiah Cornelius can "dish it out" but he can't take it in return!

Re:Running NTFS.SYS version 6.1.7601.18106 (0)

Anonymous Coward | about a year ago | (#43433799)

1 was "rejected" as "does not apply to your operating system version" (something very along those lines was the specific err message/abend)!

Calling an informational message "abend" does not give me confidence in your technical knowledge.

Better than YOUR lack of knowledge (-1)

Anonymous Coward | about a year ago | (#43434011)

Shown here, ac troll -> http://tech.slashdot.org/comments.pl?sid=3642669&cid=43433705 [slashdot.org] where I easily "schooled you" on how hosts work in relation to Windows update (which you blew it on attempting to troll me, albeit as shown there, in vain).

* Then, the "icing on the cake" is below, since you blew it here, yet again... lol!

APK

P.S.=> By the way: IF/WHEN a program doesn't function as intended ( & yet it has error trapping/handling telling you it can't also) YES, it is doing an "abend" (abnormal ending - ala "OLD IBM SPEAK" which I still to this day, can't 'shake' as it's near where I started from in the art & science of computing decades ago on UNIX, VAX, & yes, IBM midrange/mainframe stuff in Academia + professionally) -> "abend (Noun) Termination of a process prior to completion." FROM -> http://www.definitions.net/definition/abend [definitions.net]

So, thus:

By NOT installing what it should have/failing to complete it's intended task-duties? IT IS AN "ABEND", period!

(Thank goodness it didn't & I am running JUST FINE because of it too!)

So, in closing - How STUPID do you feel after both of your failed 'trolling' ac attempts in BOTH links above, Jeremiah Cornelius, you noob ac troll fool?

... apk

hmmm looky there what was lurking in my updates... (1)

Greg01851 (720452) | about a year ago | (#43433449)

Good thing I saw this article, THEN looked at my pending updates... I had just set up my new computer with Win7 64bit yesterday... and of course had tons of updates to do... Wonder why it stayed in the list even after I refreshed if there's such an issue with it?

Windows - Destroying hardware and helping sales! (1)

oxidus60659 (2854533) | about a year ago | (#43433467)

Windows update has fried at least two pieces of my hardware in the last year. First it torched my videocard immediately after restarting for a windows update. Next, the PCI express slot wouldn't register on my motherboard, good thing I had another one!

Re:Windows - Destroying hardware and helping sales (0)

Anonymous Coward | about a year ago | (#43433853)

You are a beautiful unique snowflake.

Re:Windows - Destroying hardware and helping sales (2)

Tharkkun (2605613) | about a year ago | (#43434009)

Windows update has fried at least two pieces of my hardware in the last year. First it torched my videocard immediately after restarting for a windows update. Next, the PCI express slot wouldn't register on my motherboard, good thing I had another one!

That's very similar to my laptop which tries to kill me during the Winter months. I try very hard to sneak up on it by wearing socks on a soft carpet but it always seems to hear me coming and zaps me the moment I touch it.

Re:Windows - Destroying hardware and helping sales (0)

Anonymous Coward | about a year ago | (#43434395)

I updated my windows boxen one evening. The following morning, I forgot my laptop at home. I returned 40 minutes after leaving and found my wife taking it in all 3 holes.

Fucking Micro$oft. Wrecking homes.

i got blue screens for other reasons (0)

Anonymous Coward | about a year ago | (#43433483)

slightly off topic but -

i got a blue error screen related to my video card a few times with Windows XP. I know, i should upgrade. lol I think i saw a blue screen related to a USB device hard drive or some other driver, but I couldn't tell. the error message didn't list the device that caused the error. at least Windows XP is more stable than Windows 95 or Windows 3.1.

i'm glad that Microsoft was able to acknowledge the issue with the new patch quickly. hopefully they will release a new patch that doesn't generate the blue screen error soon.

I used Linux a few times like Suse. I never saw any errors related to device drivers with Suse. if any errors did occur, Suse ran without issue.

guess i'll switch from Windows XP to Linux for sure. Only real reason I still use Windows XP is some MMORPGs don't run too good on Linux with WINE.

GFD microsoft! (1)

AndyKron (937105) | about a year ago | (#43433571)

So they push out updates all the time to the point where I'm ready to throw my computer out the window, and now we get BSOD? God fucking damnit Microsoft!

Re:GFD microsoft! (0)

Anonymous Coward | about a year ago | (#43433875)

So they push out updates all the time to the point where I'm ready to throw my computer out the window

IIRC Patch Tuesday is a result of customer feedback to manage an update schedule. How many less than 12 times a year do you want?

Re:GFD microsoft! (1)

Sponge Bath (413667) | about a year ago | (#43433979)

It certainly seems to happen more often than one a week. The wife of a guy I work with leaves her Window laptop in sleep mode at night and it will wake up on its own at 3AM to update, flooding the bedroom with light from the screen. I suppose that feature is this one http://support.microsoft.com/kb/979878 [microsoft.com] . Fun with Windows.

Bad patch (0)

Anonymous Coward | about a year ago | (#43433991)

I wouldn't call it a patch, but apparently its the 8th patch in a sequence. They call the patch 'Windows 8'. Uninstall, and your computer will no longer crash from the bad bad software anymore.

KB (0)

Anonymous Coward | about a year ago | (#43434327)

The patch was called Windows 8

I suspected as much (1)

Control-Z (321144) | about a year ago | (#43434343)

A lightly-used XP machine blue-screened on me this week for the first time, and wouldn't boot without blue-screening. I put it through memory and hard drive checks which it passed just fine. I suspected it might have been a MS patch. Somehow it finally rebooted after 4 or 5 tries, but I haven't rebooted it since. Now I know what patch did it, I can uninstall it. Sheesh.

Load More Comments
Slashdot Login

Need an Account?

Forgot your password?
or Connect with...

Don't worry, we never post anything without your permission.

Submission Text Formatting Tips

We support a small subset of HTML, namely these tags:

  • b
  • i
  • p
  • br
  • a
  • ol
  • ul
  • li
  • dl
  • dt
  • dd
  • em
  • strong
  • tt
  • blockquote
  • div
  • quote
  • ecode

"ecode" can be used for code snippets, for example:

<ecode>    while(1) { do_something(); } </ecode>