Prev: False Positives?
Next: Dreaded KB977165 Patch - Stalker Alert
From: David Kaye on 14 Feb 2010 02:50
Now Microsof's gone and done it. They've put out a patch that now causes
computers to boot over and over, showing brief BSODs. It all began on
February 10 with patch KB977165. So far I have 2 customers and a housemate
who have been infected by this patch. Yet I have two of my own computers with
the patch and they're fine.

Problem is that you can't boot into Safe Mode. You have to go in via a
Windows set up disk or something like BART-PE and uninstall the patch. I've
done this twice now.

But the big problem is that my housemate has a netbook with no CD drive. I
created a bootable flash drive, stuck it in and the setup program loads fine,
but it cannot find the hard drive! Probably some weird configuration that
netbooks go through when starting up.

So, I can't even fix my housemate's machine. I'm loathe to go out and buy a
USB CD just to fix his computer.

Way to go Microsoft. You've made a patch that you didn't thoroughly test out
and spewed it across the world.

From: Peter Foldes on 14 Feb 2010 08:49
David

The 'problem' turned out to be infected/infested machines.

If your machine is not infested/infected, in particular with:

Win32/Alureon.A
http://www.microsoft.com/security/portal/Threat/Encyclopedia/Entry.aspx?Name=Virus%3AWin32%2FAlureon.A

More information on the ongoing investigation can be read here:
http://blogs.technet.com/msrc/archive/2010/02/12/update-restart-issues-after-installing-ms10-015.aspx

If the machine is not infected as with the above then the install will work
flawlessly and If it is infected then you have the issue

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"David Kaye" <sfdavidkaye2(a)yahoo.com> wrote in message
news:hl8a0f$8pi$1(a)news.eternal-september.org...
> Now Microsof's gone and done it. They've put out a patch that now causes
> computers to boot over and over, showing brief BSODs. It all began on
> February 10 with patch KB977165. So far I have 2 customers and a housemate
> who have been infected by this patch. Yet I have two of my own computers with
> the patch and they're fine.
>
> Problem is that you can't boot into Safe Mode. You have to go in via a
> Windows set up disk or something like BART-PE and uninstall the patch. I've
> done this twice now.
>
> But the big problem is that my housemate has a netbook with no CD drive. I
> created a bootable flash drive, stuck it in and the setup program loads fine,
> but it cannot find the hard drive! Probably some weird configuration that
> netbooks go through when starting up.
>
> So, I can't even fix my housemate's machine. I'm loathe to go out and buy a
> USB CD just to fix his computer.
>
> Way to go Microsoft. You've made a patch that you didn't thoroughly test out
> and spewed it across the world.
>

From: David Kaye on 14 Feb 2010 14:46
"Peter Foldes" <bounce(a)bounce> wrote:

>The 'problem' turned out to be infected/infested machines.
>

One of the machines turned out to not be infected at all. I ran Malware
Bytes, Avast, and RootKit Revealer on it. Nada.

The other one had remnants of Antivirus 2009 or its kin, but was not
triggerable.

From: David Kaye on 14 Feb 2010 14:47
"Peter Foldes" <bounce(a)bounce> wrote:

>
>The 'problem' turned out to be infected/infested machines.

WHOA WHOA WHOA!!! So then Microsoft admits that the Malicious Removal Tool
they send and deploy each month is not detecting or removing malware?

From: Peter Foldes on 14 Feb 2010 15:20
the Malicious Removal Tool removes only some types of malware and not all. Rootkits
are not touched by the Malicious Removal Tool the same as any AV or malware tools.
Rootkits have to be or should I say need to be treated differently

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"David Kaye" <sfdavidkaye2(a)yahoo.com> wrote in message
news:hl9k1c$l1q$4(a)news.eternal-september.org...
> "Peter Foldes" <bounce(a)bounce> wrote:
>
>>
>>The 'problem' turned out to be infected/infested machines.
>
> WHOA WHOA WHOA!!! So then Microsoft admits that the Malicious Removal Tool
> they send and deploy each month is not detecting or removing malware?
>

 |  Next  |  Last
Pages: 1 2 3 4 5 6 7
Prev: False Positives?
Next: Dreaded KB977165 Patch - Stalker Alert