Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Microsoft Security Windows

Microsoft Releases Replacement Patch With Two Known Bugs 140

snydeq writes Microsoft has re-released its botched MS14-045/KB 2982791 'Blue Screen 0x50' patch, only to introduce more problems, InfoWorld's Woody Leonhard reports. "Even by Microsoft standards, this month's botched Black Tuesday Windows 7/8/8.1 MS14-045 patch hit a new low. The original patch (KB 2982791) is now officially 'expired' and a completely different patch (KB 2993651) offered in its stead; there are barely documented revelations of new problems with old patches; patches that have disappeared; a 'strong' recommendation to manually uninstall a patch that went out via Automatic Update for several days; and an infuriating official explanation that raises serious doubts about Microsoft's ability to support Windows 9's expected rapid update pace."
This discussion has been archived. No new comments can be posted.

Microsoft Releases Replacement Patch With Two Known Bugs

Comments Filter:
  • by wbr1 ( 2538558 ) on Friday August 29, 2014 @08:31AM (#47783459)
    Yesterday in my repair shop I started getting a 0x80246002 error when checking for updates. Only on Win 7, (8 and vista were unaffected). This first occurred on a customer box that had a malware infection. The KB for this error simply states:

    This problem may occur if Windows Update or Microsoft Update determines there is a file hash mismatch when you try to search for available updates from the Windows Update Web site or from the Microsoft Update Web site.

    I spent a couple hours down the rabbit hole, thinking malware had broken updates on this box. Not unusual, and normally fixable by one of several means. When all attempts failed, and then another box presented the same error, I checked, every single windows 7 box would not check for updates.

    I found that it was not something strange in our router or firewall, and it even occurred on other building tenants computers using a separate internet connection. Everyone in the building is on Comcast. Even more interesting, if I connected a computer to another ISP (tethering on my phone in this instance), the update check would succeed. You could then reconnect to comcast and download and install the updates.

    Further all of these computers were running Windows Update Agent 7.6.7600.320, which is a recent (KB less and not able to be skipped) update to Windows update, that you cannot roll back easily. However, by going to a restore point prior to this update, checking for updates magically worked again, until this Agent updated itself and it was broken again.

    So somehow, for whatever reason, the way Windows Update on Win 7 with this version of the agent checks for updates was being blocked by Comcast (Business class). Try explaining that to a comcast support rep. Fortunately today it seems to be working again.

  • No Patch Info (Score:5, Informative)

    by MrL0G1C ( 867445 ) on Friday August 29, 2014 @08:35AM (#47783475) Journal

    What pigs me off is that when you use Windows Update and look at a patch it gives you no info, so you click the patch and still no info', you click the link given but that pretty much just says it's a patch and you should install it, finally after following another link, scrolling down and expanding a section of page you get to find out whether or not the patch is actually relevant to your installation and not just a fix for something you will never use.

    I don't use and don't need patches for One-Note, IE, Windows Media Centre, SQL Server. Privilege escalation bugs don't bother me, if you've been compromised that far then you're probably f**ked anyway.

    The only bugs that look half-dangerous this month are MS14-046 and MS14-047 because they can lead to you being rooted when joined with browser etc bugs

    For future use: []

  • by MrL0G1C ( 867445 ) on Friday August 29, 2014 @08:38AM (#47783487) Journal

    You beat me to it, this page is what we need: []

    But of course that info should be right there on the windows update window.

  • by Anonymous Coward on Friday August 29, 2014 @09:00AM (#47783593)

    Had the same problem yesterday on a newly patched Windows 7 laptop and then today on a Windows Server 2008 R2 server.

    Problems with Windows Update Agent 7.6.7600.320 and DNS [] seems to be where this is headed.

    But I'm holding off on KB 2993651 [] and Windows Update Agent 7.6.7600.320 [] until this one gets resolved too.

  • Re:Oh microsoft (Score:2, Informative)

    by Anonymous Coward on Friday August 29, 2014 @11:48AM (#47784853)

    The free software desktop's problems are a lack of polish. Microsoft's problems are outright neglect.

  • Re:Oh microsoft (Score:5, Informative)

    by phantomfive ( 622387 ) on Friday August 29, 2014 @02:21PM (#47786059) Journal
    I've written enterprise software, used by large banks and other corporations. Our software was so bad, I couldn't understand how it would help anyone, I'm sure the people who used it were slowed down by the process.

    Finally I realized they did get one thing from it: accountability. If you've never been there, it's hard to understand how corporations are shaped by SOX compliance, and general accounting problems. If a $2000 purchase disappears at a startup, it's a minor problem. But at a large company, accountants will be looking for weeks to find what happened to it.

    Those are the kinds of issues large companies deal with, and removing the accountability of the decision making process (of figuring out what software to use) and giving it to Microsoft is a real service for them. This is the same reason people use RedHat, even though RedHat gives their software away for free. It is one of those things that makes no sense to you until you've worked in that kind of environment.

Genius is ten percent inspiration and fifty percent capital gains.