Author Topic: "Prevx blames Microsoft for black hawk screen down"  (Read 3097 times)

0 Members and 1 Guest are viewing this topic.

Hermite15

  • Guest
"Prevx blames Microsoft for black hawk screen down"
« on: December 01, 2009, 01:49:44 PM »
http://www.theregister.co.uk/2009/11/30/prevx_microsoft_black_screen/
http://www.prevx.com/blog/140/Black-Screen-woes-could-affect-millions-on-Windows--Vista-and-XP.html

my system hasn't been affected...so far.

edit: just one thing, about PrevX... when sometimes googling for a file (stuff found in Windows and more info needed), PrevX belong to those sites telling you something like "wanna know more about the *.exe or *.dll error  ;D ..." do a scan, buy PrevX. Too bad as this company is otherwise reputed for its products, but I just hate those practices, that's properly disgusting. That don't say clearly if the file is malware or not sometimes, they're just after your money, while attempting to make you doubt about the status of the file.
« Last Edit: December 01, 2009, 01:56:23 PM by Logos »


fredvries

  • Guest
Re: "Prevx blames Microsoft for black hawk screen down"
« Reply #2 on: December 02, 2009, 12:44:37 PM »
And the fix only addresses the following Reg Code:

Quote
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
“Shell”=”explorer.exe”

See here.

Like Ramesh Kumar says: it's a bit of a non-issue.

In case you should quickly need the fix, I've added it under 'Cool fixes' in my List of Av and As Uninstallers.
« Last Edit: December 02, 2009, 04:03:09 PM by fredvries »

Hermite15

  • Guest
Re: "Prevx blames Microsoft for black hawk screen down"
« Reply #3 on: December 02, 2009, 12:48:16 PM »
And the fix only addresses the following Reg Code:

Quote
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
“Shell”=”explorer.exe”

See here.

Like Ramesh Kumar says: it's a bit of a non-issue.

thanks for these precisions, I'm gonna read this now...

Hermite15

  • Guest
Re: "Prevx blames Microsoft for black hawk screen down"
« Reply #4 on: December 02, 2009, 12:54:01 PM »
yeah, now this makes more sense, as I just couldn't see how those patches could be responsible at all:
Quote
Having narrowed down a specific trigger for this condition we've done quite a bit of testing and re-testing on the recent Windows patches including KB976098 and KB915597 as referred to in our previous blog. Since more specifically narrowing down the cause we have been able to exonerate these patches from being a contributory factor.