Windows XP patch fiasco gets even crazier, Microsoft now scrambling for solutions

If you ever needed a reason to go Linux, here you go. The noise surrounding this patently obscure Windows XP bug / patch fiasco has just reached a fever pitch, and now we’ve got engineers within Redmond scratching their heads, too. As the story goes, Microsoft recently patched a security hole that took care of an antediluvian DOS vulnerability, and in doing so, some users began to see BSODs and endless reboots. Today, we’ve learned that the patch has been yanked, and Microsoft is suggesting that malware is to blame. But here’s the skinny — the patch simply disturbed the malware, which called a specific kernel code that directs your PC to keel over; in other words, any application that calls that same code could theoretically leave your machine in dire straits. And that, friends, probably explains the software giant’s following quote:

“In our continuing investigation in to the restart issues related to MS10-015 that a limited number of customers are experiencing, we have determined that malware on the system can cause the behavior. We are not yet ruling out other potential causes at this time and are still investigating.

Rock, meet hard place.

Windows XP patch fiasco gets even crazier, Microsoft now scrambling for solutions originally appeared on Engadget on Sat, 13 Feb 2010 00:33:00 EST. Please see our terms for use of feeds.

Permalink Yahoo! Tech  |  sourceTechNet  | Email this | Comments

Patch for ancient DOS bug in latest Windows XP update causing blue screen errors

Looks like Patch Tuesday turned into BSOD Tuesday for some Windows XP users — Microsoft’s latest security updates for the venerable OS are causing blue screens and endless reboots for people. That’s the word according to a growing support thread on Microsoft’s site — and making matters just slightly worse / funnier, it’s apparently the patch for that 17-year-old DOS vulnerability that’s causing all the trouble. You win some, you lose some, right? Microsoft’s identified a fix for those with access to an XP install disc and an optical drive, but that leaves most netbook users out in the cold — and considering netbooks are where most of the recent XP action’s been going down lately, we’re hoping a better solution comes down the pike soon.

P.S.- That’s the BSOD tattoo guy in the photo — remember him?

[Thanks, HyperSl4ck3r]

Patch for ancient DOS bug in latest Windows XP update causing blue screen errors originally appeared on Engadget on Thu, 11 Feb 2010 19:58:00 EST. Please see our terms for use of feeds.

Permalink Computerworld  |  sourceMicrosoft Answers  | Email this | Comments

Ancient DOS bug gets squashed

Noble DOS's last bug gets squashed

What can we say about you, DOS? You’ve rocked the personal computer world and changed the way we all feel about white on black console screens. Your retirement is a well deserved one and… wait, you’re getting a patch? Amazingly, Microsoft is fixing a bug that has existed in the Windows Virtual DOS Machine (VDM) subsystem since it was added to Windows NT way back in the simple days of 1993, when flannels were everywhere and 32 bits were more than we knew what to do with. Google engineer Tavis Ormandy found the exploit a few weeks ago, which grants an attacker the ability to run code in kernel mode, and a critical update has been issued to fix this most aged of vulnerabilities. Perhaps now, DOS, your work is finally done.

Ancient DOS bug gets squashed originally appeared on Engadget on Fri, 05 Feb 2010 07:46:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceBBC  | Email this | Comments

AT&T fixes bug that logged users into random Facebook accounts

Okay, so we were under the impression that Facebook login credentials were a locally-managed affair, but it looks like almost anything can break when AT&T’s involved — according to CNET, the carrier just fixed “several problems” that had users logging into the wrong Facebook account from their phones. The issue was apparently related to subscriber identification numbers being mistranslated into bad URL session IDs, and AT&T says it’s taken some security measures to prevent it from happening again, while Facebook’s just shut off the automatic login feature that used the ID number entirely. Excellent work all around. Unfortunately, there’s also a pesky incident in Atlanta where someone was able to login to another Facebook account from an AT&T phone due to a bad cookie, but AT&T says that was an “isolated” case and that it’s “unclear how this cookie was set on the phone.” How very reassuring. Back to Friendster!

AT&T fixes bug that logged users into random Facebook accounts originally appeared on Engadget on Mon, 18 Jan 2010 23:04:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceCNET, Yahoo  | Email this | Comments

Nokia’s Maemo Ovi Store looking rickety, ‘beta’ label well-deserved

Bugs are to be expected in brand-new apps and platforms — particularly when they’re clearly marked with a “beta” sign — but it starts to get a little hairier when there’s money involved. One of the early crowd favorites in Nokia’s Ovi Store for Maemo appears to be the game Angry Birds, which is available with a €3 level pack — problem is, plenty of folks have discovered a way around actually paying the cash, which becomes a big problem for the developer very, very quickly. The level pack has since been removed, probably the best move until Nokia can figure out what’s going on here and issue a patch. In the meantime, looks like it’s back to the ol’ repositories.

Nokia’s Maemo Ovi Store looking rickety, ‘beta’ label well-deserved originally appeared on Engadget on Wed, 13 Jan 2010 20:05:00 EST. Please see our terms for use of feeds.

Permalink The Nokia Blog  |  sourceMaemo Talk  | Email this | Comments

Droid security flaw makes lock screen a mere inconvenience for evil-doers

You might recall Apple having a hard time keeping its lock screen locked at one point, and it looks like we’ve got a common theme brewing here now that Android’s suffering from the same drama. Turns out that Android 2.0.1 — the build currently deployed on the Droid — suffers from a flaw whereby you can back out to a locked phone’s home screen simply by pressing the Back button after accepting an incoming call. Of course, you’d either have to know a phone’s number or wait for a call to actually take advantage of this, but we’d argue that it’s a pretty low barrier of entry. The bright side of the story, we suppose, is that the phone goes back to being locked as soon as the call ends, but then again it doesn’t take much time to peep your juicy emails. Google’s aware of the issue, so we’re thinking this’ll make it into the Droid’s next software update; we don’t have a launch window for that just yet, so in the meantime… you know, just make sure no one ever calls you and you should be good to go.

Droid security flaw makes lock screen a mere inconvenience for evil-doers originally appeared on Engadget on Mon, 11 Jan 2010 15:49:00 EST. Please see our terms for use of feeds.

Permalink PhoneArena  |  sourceTheAssurer  | Email this | Comments

Windows Mobile Bug Dates Messages from 2016

windows-mobile-phone

Windows Mobile users are facing an unexpected New Year’s surprise. A software bug has struck smartphones running the Microsoft operating system so all messages received starting January 1 are dated 2016.

Phones running versions 6.1 or 6.5 of Windows Mobile are reportedly affected. Microsoft and the handset makers haven’t responded yet with a fix for the bug. We are still waiting for a comment from the company.

The Windows Mobile bug is similar to the once-feared Y2K problem where computer programs had to be rewritten to ensure they interpreted the “00″ date tag as year 2000, instead of 1900. Windows Mobile had 11 percent share of the global smartphone market in the third quarter of 2008. But it has been losing ground to competitors such as Apple with the iPhone OS and the Google-designed Android operating system. In the fourth quarter, Windows Mobile’s market share declined to 7.9 percent.

The latest Win Mobile bug is an annoyance to its users. Because messages are incorrectly dated, they get lost in the inbox and conversation threads don’t show up appropriately. Outgoing messages, though, are dated correctly.

There is a temporary solution. An unofficial patch tries to use the phone’s clock rather than the one used by the SMS gateway to date the  messages correctly.  Meanwhile, users of Windows Mobile based smartphones on T-Mobile’s network say they haven’t faced the problem.

See Also:

Photo: (Tim Dorr/Flickr)


Windows 7 Black Screen of Death? (It’s not as bad as it sounds)

Well, maybe it’s not as bad as it sounds, but it’s still not so good. As you’re probably aware, over the last week or so Windows users of all stripes (not just Windows 7 users, as it turns out) have been complaining of a plain black screen that appears upon login — at which point the systems lock up, and… that’s it. Aside from some users getting an additional My Computer window (lucky devils) the system grinds to a halt. According to a Microsoft email that’s making the rounds, the company is “investigating reports that its latest release of security updates is resulting in system issues for some customers.” Until that time, what’s a poor PC user to do? Prevx, a UK developer of anti-malware software, has surmised that a recent Windows security patch changed Access Control List (ACL) entries in the registry, preventing some software from running properly and prompting Engadget to whip up a Bergman-inspired graphic. If your machine should find itself afflicted, Prevx has put together a fix that it claims will do the trick. Keep in mind that we don’t know these guys, so don’t blame us if it blows up your computer — or gives you the Bubonic plague. We’ll let you know when we hear back from Microsoft on this one. Good luck!

Update: Microsoft says this isn’t its fault, and that it’s likely some nasty malware to blame.

Windows 7 Black Screen of Death? (It’s not as bad as it sounds) originally appeared on Engadget on Tue, 01 Dec 2009 11:31:00 EST. Please see our terms for use of feeds.

Permalink BBC  |  sourcePrevx  | Email this | Comments

Sony Ericsson Satio sales suspended after bugs discovered

Adding insult to Sony Ericsson’s injurious bottom line, Carphone Warehouse and Phones 4U shops (the UK’s largest mobile phone retailers) have halted sales of the SE’s Symbian-powered Satio handset after a high number of customer returns and complaints. A “software glitch” reportedly causes Sony Ericsson’s flagship device to power down when users try to access certain applications — unfortunately, the issue can’t be patched via an over-the-air update. A little digging into CPW discussion forums reveals multiple complaints of freezes, crashes, under-performing batteries, and bizarre interface behavior. Both the Carphone Warehouse and Phones4U will offer “new phones” to customers fed up with their Satio. Richard Dorman, senior marketing manager at Sony Ericsson, concedes the issue and assures us that it should be sorted by Christmas. Until then, you can still purchase the handset directly from Vodafone, Orange and T-Mobile… but really, why would you? The Satio’s not the only dubiously-spec’d 12 megapixel cameraphone on the market.

[Thanks, ugotamesij]

Sony Ericsson Satio sales suspended after bugs discovered originally appeared on Engadget on Tue, 24 Nov 2009 06:02:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceTimes Online  | Email this | Comments

Core i7 iMacs showing up DOA — including ours

Apple’s new Core i7-based iMac might be a performance monster, but it looks like the whole family’s having some problems getting out of the gate: in addition to the previously-noted performance issues with the Core 2 Duo models, a quick glance across Apple’s support forums and on other Mac boards around the web reveals that some machines are showing up DOA and / or with cracked screens. We’re a little more familiar with the DOA issue, since the new i7 we just bought doesn’t boot at all, but the cracked screen issue seems to be equally common and mostly affecting the bottom left corner, from what we can tell. Now, our review Core 2 Duo 27-inch iMac is perfectly fine, and Chris Ziegler’s new Core i7 machine doesn’t have any problems either, so these obviously aren’t universal issues, but if you’re about to stick one of these under the tree for someone it might be wise to do some surreptitious testing first.

Core i7 iMacs showing up DOA — including ours originally appeared on Engadget on Tue, 24 Nov 2009 01:38:00 EST. Please see our terms for use of feeds.

Permalink   |  sourceDOA discussion, Cracked screen discussion  | Email this | Comments