duguk writes "Microsoft has confirmed that it is investigating a problem described as the 'black screen of death,' which affects Windows 7 — and reports suggest it affects Vista and XP, too. The firm said it was looking into reports that suggest its latest security update, released on Tuesday 25 November, caused the problem. The error means that users of Windows 7 and earlier operating systems see a totally black screen after logging on to the system."Update: 12/01 22:35 GMT by KD: Microsoft now says that its November Windows updates are not causing the BlackSOD: "The company has found those reports to be inaccurate and our comprehensive investigation has shown that none of the recently released updates are related to the behavior described in the reports."
Had a secretary at my first job with a similar problem. Reasons for "The computer is broken!": 1.) forgot to turn monitor on. 2.) didn't press power button on desktop 3.) kicked monitor plug near the power strip pulling it out of back of monitor. 4.) stepping on power strip rocker switch. 5.) somehow put the entire OS in dutch.
At least you kept warm.. In my day the temperature never got above -10 Kelvin.
My home town nearly went to zero Kevins back in 1978.
It was a particularly cold winter, and we were already down to 3 Kevins (due to their low popularity at the time).
Kevin Thomas had flown out to be with his son's family for a wedding and got stuck in Boston for a whole week due to the weather. 2 Kevins left.
Kevin Lemmer was rushed to the hospital during my shift. I still remember the call from the EMTs as the ambulance was rushing toward us. "It's Lemmer. He's in bad shape. Drove right into the fucking ditch." We called the time of death at 6:15 PM.
At 6:16, all eyes turned to room 2217. Kevin Spencer was 82 and on his death bed with leukemia. His family being Catholic, he had already been given his last rights. If he couldn't hold out until Kevin Thomas returned, we would be at zero Kevins. Sure, we had 4 perfectly healthy Calvins, but they're just not the same.
It was 7:15 when Carla Brooks and her husband James burst through the main entrance. "She's not due for 2 weeks!", James exclaimed. As the staff bustled around getting the Brookses settled, they exchanged darting glances with each other. This was their first child, and they wanted to keep the baby's sex a secret. Of course, in a small town, secrets don't get kept. Nearly all of the hospital staff new that the child about to rip open Mrs. Brooks was indeed a boy.
The delivery was routine, and Kevin Brooks was born healthy, if a tad underweight, at 10:52 PM. Kevin Spencer was pronounced dead at 10:54.
It was, as they say, a close one. Kevin Thomas arrived two days later, the weather having finally cleared up. To this day, we still rib him about it.
Last I tried it (don't know if it's improved) it would tell you about an infection in a file, but wouldn't offer any way to clean the file. To clean infections you had to manually run a full scan. IIRC, this was AVG 7, though it sounds like the behaviour of a v0.7 virus scanner to me.
When I found out that Avast Home (aka free) would not only allow me to clean infected files when they were found, but would go as far as scanning incoming HTTP replies and cutting connections if it saw an incoming infection attempt, before the data got to the browser, I switched and haven't looked back.
Not much use when there is a huge amount of software that has to run as Administrator is it? It takes a lot more than something that is a slightly different way of doing things than the user+group model to get "light years beyond" it - let alone every other feature on the different platforms. Personally I see the ability of people to grant their own permissions to others without authorisation as a major security hole in the entire way it is implemented on the MS platform so consider it a step backwards. Yo
This is the one thing I wish linux had... Windows style file/directory permissions.
The 3 bit file permissions of RWX is so... 20 years ago
Not all the permissions in Windows are useful but here are a couple that I would love to see in *NIX systems
-List directory contents
-Create new files/folders
-Delete
Sorry but after reading that, I have to conclude you are not very knowledgable about Unix and Unix-like systems. All of these apply to *nix:
A user can list the contents of a directory if he has execute (X) permissions for that directory.
A user can create new files/folders in a directory if he has write (W) permissions for that directory.
A user can delete a file if he has write (W) permissions on that file.
*nix permissions have three categories: owner, group, and all users. It does not matter fo
A user can list the contents of a directory if he has execute (X) permissions for that directory.
A user can create new files/folders in a directory if he has write (W) permissions for that directory.
A user can delete a file if he has write (W) permissions on that file.
You actually only got 1 out of 3 correct.
A user can list the contents of a directory if he has R permissions on that directory. The X bit controls whether that directory can be an element of a pathname which is being accessed. In other
Cue the characteristic Slashdot flavor of older-than-you elitism! Oh wait, I'm too late...
But seriously, completely irrelevant age differences aside: There's a reason why Microsoft catches flak for security holes, and also a very good reason for why they so adamantly encourage people to update their OS as often as possible. Microsoft (and certainly your full comprehension of the vulnerability of the OS) are far from infallible; their software is extremely complicated and will always present new bugs and des
I don't want to argue with you, but I have got a windows box up, running, connected (OK by a severely restricted connection) to th'interweb, I use it daily, it genuinely hasn't been updated by mickeysoft since it was installed (It's not a knock-off copy, it was a shrink-wrap) & runs continuously, 24 hours a day.
Your machine, by contrast, is probably as stable as a two legged cow. However it's most likely fully patched
Let me just start by saying... You are soooo cool. You're running an Operating System from 2003. I hope you're not in IT. I can imagine you telling your management, "we're running Solaris 8/9 and have never applied any patches." I also hope you're not a developer that has made updates/fixes to your products so you can say to your customers, "How come you've never applied any of my updates? I've slaved over this code for the past seven years!"
And since this is/., where everyone brags about their personal machine in their basement, I hope you've never run apt-get update and still run firefox 1.x/2.x (or whatever version was around in 2003).
Or do you think that all fixes in linux/firefox are better than even service packs in winXP...
I also hope you've never fixed your car or a leaky faucet..
Lookeee here, guys! Someone who claims to be a senior IT security "technician" who has never heard of defense in depth!
He even thinks server-side virus-scan can catch as much malware as the client-side stuff does. Guess he's never heard of behavior-based virus detection, either? And his grand security architecture posture is simply "don't use much of the internet." There's sophistication for you.
But then, he's extrapolated his advice based on a single poorly-measured datapoint. Who are we to question him?
I believe the change was implemented in order to prevent phosphor burn-in on older CRT monitors.
Actually, blue was chosen deliberately because zinc sulfide silver (blue phosphor in CRTs) is more resistant to burnout than the other phosphors, thus ensuring more even color rendition over time. It was a feature, not a bug:-). With no burnout problems in LCD panels, they went with black.
Microsoft felt guilty about not allowing you to change the desktop picture in Windows Starter Edition, so they realeased this variation of the BSoD to everyone, to make up for it.
Interesting that Shrike82 is never accurate, at least according to wikipedia: from http://en.wikipedia.org/wiki/Ford_Model_T [wikipedia.org]
"Colors
By 1918, half of all cars in America were Model Ts. However, it was a monolithic bloc; as Ford wrote in his autobiography, "Any customer can have a car painted any color that he wants so long as it is black".[17] Model Ts in different colors were produced from 1908 to 1914, and then again from 1926 to 1927."
by Anonymous Coward writes:
on Tuesday December 01, @12:44PM (#30285528)
Had this the other day (Win7 Ultmate, Q6600 8GB RAM) it sat for a couple of minutes (there was some disk activity). Afterwards everything was fine; I chalked it up to an update and looks as though I was right.
The headline should read "Microsoft finds way to make an Operating System 100% secure".
Once the Black (screen of) Death Security Pack is installed, the computer locks up after login, meaning the user will not be able to surf to dangerous pages, will not be the victim of even the most clever social engineering hacks, and best of all won't see any spam any more, ever.
Users protected by the BsoDSP can feel free to emerge from their basements and experience RealWorld 1.0. It's like a MMORPG, but with real sex.
From link above:
1) Restart your PC
2) Logon and wait for the black screen to appear
3) Make sure your PC should be able to connect to the internet (black screen does not appear to affect this)
4) Press the CTRL, ALT and DEL keys simultaneously
5) When prompted, Click Start Task Manager
6) In Task Manager Click on the Application Tab
7) Next Click New Task
8) Now enter the command:
"C:\Program Files\Internet Explorer\iexplore.exe" "http://info.prevx.com/download.asp?GRAB=BLACKSCREENFIX"
And this my friends, is exactly why Windows is not ready for the desktop in 2009. I mean, you have to type in random junk into the command line to fix a buggy Microsoft patch - Can we expect grandma to be able to do this? More must be done to make Windows user friendly to all!
by Anonymous Coward writes:
on Tuesday December 01, @01:37PM (#30286426)
that's actually the really dumb way of doing it. Turns out, you can just run explorer, and continue as if you had booted normally.
So: 1) Boot 2) Login 3) Get Task Manager (Ctrl+Alt+Del) 4) File -> New Task (Run...) 5) Type "explorer" (no quotes) - Windows should now be running normally 6) Click on ericthughes's link above 7) Download and run the file they have linked there
It's even simpler if you just understand that the screen is blank because explorer (desktop process, should always be running) didn't start.
Or at least, that's how I've experienced the problem. It's not so much a BSoD as a "this process forgot to start."
Honestly, the only part that scares me is that I have to run their exe. I can function without this fix, and will wait for the official fix next week.
On my MSI Wind netbook running Windows 7, I once woke the system from sleep and got a black screen. The machine was still working, the mouse cursor was on screen and moved with the touchpad, there was disk activity, it connected to the wireless network, caps lock/num lock were still responsive, but nothing else appeared on the screen and nothing I did made it work. I had to manually power the system off. I was able to wake the system from sleep many times before and after without any problems.
I didn't notice any updates that the problem could have been correlated with.
I had this happen a year or so ago on a Server 2003 box and never could find the actual cause. I don't know if the fix is the same in this case, but in my case it was simple:
Check out [HKEY_USERS\.DEFAULT\Control Panel\Colors] - if everything is set to [0 0 0], modify those values to something other than black. The easiest thing to do, actually, is to export that key from another box that's good, then import on the box that's got the problem.
11/24 my windows machine is working perfectly,. Been up for over a month and fully activated (I bought the $30 Win 7 prof. EDU discount). Turn off my computer the same night (vacation).
11/28 come back from vacation turn my computer on and it updates itself with the 11/25 patches. As soon as they are installed all of a sudden my copy is no longer genuine and I get all the warnings.
Spend 2 hours with Microsoft last night. product key is valid. They tell me that windows updater is corrupted and I need to reinstall the entire OS. I was told it is an "issue" when doing a custom upgrade from Vista.
Now this article is out I am wondering if their patches tried to tighten some DRM and broke a lot more then being reported.
11/24 my windows machine is working perfectly,....11/28 come back from vacation turn my computer on and it updates itself with the 11/25 patches. As soon as they are installed all of a sudden my copy is no longer genuine and I get all the warnings....Spend 2 hours with Microsoft last night. product key is valid. They tell me that windows updater is corrupted and I need to reinstall the entire OS. I was told it is an "issue" when doing a custom upgrade from Vista.
Best argument for mac, linux, freebsd (insert your favorite non-DRMed OS here) ever.
It angers me to NO END that tech supports answer to all computer problems is "re-format and re-install". It is somewhat understandable since it can be very hard to figure out what kind of mess a machine is in on the end of a phone... but all consumer OSes should be able to boot into a live CD version of the OS that gives tech support access to the machine so they can diagnose the actual problem.
Excuse me, but... I thought that pretty much everyone with some technical experience knows that you never, ever use the upgrade option with Windows. Always use the clean install if possible.
It's something video related, I've seen this bug in the two machines (Win7, can't speak for Vista) I own and for some reason the monitor get "reset" to 59 Hz instead of 60 Hz and I get the black screen. The funny thing is that is the LCD lamp is not turned on but the screen does, so if you put some light in front of the screen you'll still be able to see something in the screen. This one and a USB bug that prevents the mouse getting detected was sufficient to go back to XP.
I can't believe how these bugs pass QC. And sorry for my possibly bad english.
Carlos
first was while playing a game online, and I though it was the game that crashed. Black screen, nothing worked, but the background music from the game kept playing. I waited longer than 5 minutes to see if the game would exit. When it did not I got suspicios since protected memory in 7 should not have allowed the gamr to crash the kernel. NOTHIGN was in the error logs related to it (other than the obligitory "you did not shut down properly" errors after I hit the reset button on the tower.
Next day, I had just turned it on about 20 minutes earlier, and the only thing running was Opera. Same deal, complete lock up.
7 has been running great on this machine since the day it hit my MAPS dowload queue and I installed it. Not one crash prior except an issue installing HP's printer system first time around (second try, it worked flawlessly).
It's no bug, it's a feature. Windows saves power by reducing the monitor contrast and brightness to 0. Furthermore, it turns off the Video Card and unplugs the monitor from the power socket. Then blinds you. ...I just had a chat with Steve, he said "you're lucky we didn't implement the population control routine; we couldn't figure out whether we should use inherent OS radiation or the hammer summoning algorythm on your testicles".
Problem Solved! (Score:5, Funny)
Re:Problem Solved! (Score:5, Funny)
I just put a painting in front of the monitor, and then take it away before my kids come over. They think it is so cool I'm into computers.
Parent
Re: (Score:3, Funny)
Re:Problem Solved! (Score:5, Funny)
Parent
Re:Problem Solved! (Score:4, Funny)
Parent
Re:Problem Solved! (Score:4, Funny)
Yay! I'm still young!
Parent
Re:Problem Solved! (Score:5, Funny)
Had a secretary at my first job with a similar problem. Reasons for "The computer is broken!":
1.) forgot to turn monitor on.
2.) didn't press power button on desktop
3.) kicked monitor plug near the power strip pulling it out of back of monitor.
4.) stepping on power strip rocker switch.
5.) somehow put the entire OS in dutch.
Parent
Re:Problem Solved! (Score:5, Funny)
Perfect leesbaar, toch ?
Parent
Re: (Score:3, Funny)
We had to settle for volcanic plains.
At least you kept warm.. In my day the temperature never got above -10 Kelvin.
Re:Problem Solved! (Score:5, Funny)
At least you kept warm.. In my day the temperature never got above -10 Kelvin.
My home town nearly went to zero Kevins back in 1978.
It was a particularly cold winter, and we were already down to 3 Kevins (due to their low popularity at the time).
Kevin Thomas had flown out to be with his son's family for a wedding and got stuck in Boston for a whole week due to the weather. 2 Kevins left.
Kevin Lemmer was rushed to the hospital during my shift. I still remember the call from the EMTs as the ambulance was rushing toward us. "It's Lemmer. He's in bad shape. Drove right into the fucking ditch." We called the time of death at 6:15 PM.
At 6:16, all eyes turned to room 2217. Kevin Spencer was 82 and on his death bed with leukemia. His family being Catholic, he had already been given his last rights. If he couldn't hold out until Kevin Thomas returned, we would be at zero Kevins. Sure, we had 4 perfectly healthy Calvins, but they're just not the same.
It was 7:15 when Carla Brooks and her husband James burst through the main entrance. "She's not due for 2 weeks!", James exclaimed. As the staff bustled around getting the Brookses settled, they exchanged darting glances with each other. This was their first child, and they wanted to keep the baby's sex a secret. Of course, in a small town, secrets don't get kept. Nearly all of the hospital staff new that the child about to rip open Mrs. Brooks was indeed a boy.
The delivery was routine, and Kevin Brooks was born healthy, if a tad underweight, at 10:52 PM. Kevin Spencer was pronounced dead at 10:54.
It was, as they say, a close one. Kevin Thomas arrived two days later, the weather having finally cleared up. To this day, we still rib him about it.
Cedar Falls is currently at 5 Kevins.
Parent
BSOD (Score:4, Funny)
Re:BSOD (Score:4, Insightful)
Microsoft heard all the buzz about 'skinning' apps and figured they'd one up them and skin an integral part of windoze
Parent
Can confirm the issue from personal experience (Score:4, Informative)
in that instance another forced reboot brought the system back as normal - I have no explanation
Parent
Re:Can confirm the issue from personal experience (Score:4, Informative)
Or at the very least, just don't use AVG Free.
Last I tried it (don't know if it's improved) it would tell you about an infection in a file, but wouldn't offer any way to clean the file. To clean infections you had to manually run a full scan. IIRC, this was AVG 7, though it sounds like the behaviour of a v0.7 virus scanner to me.
When I found out that Avast Home (aka free) would not only allow me to clean infected files when they were found, but would go as far as scanning incoming HTTP replies and cutting connections if it saw an incoming infection attempt, before the data got to the browser, I switched and haven't looked back.
Parent
Re: (Score:3, Insightful)
It takes a lot more than something that is a slightly different way of doing things than the user+group model to get "light years beyond" it - let alone every other feature on the different platforms. Personally I see the ability of people to grant their own permissions to others without authorisation as a major security hole in the entire way it is implemented on the MS platform so consider it a step backwards. Yo
Re: (Score:3, Informative)
This is the one thing I wish linux had... Windows style file/directory permissions.
The 3 bit file permissions of RWX is so... 20 years ago
Not all the permissions in Windows are useful but here are a couple that I would love to see in *NIX systems -List directory contents -Create new files/folders -Delete
Sorry but after reading that, I have to conclude you are not very knowledgable about Unix and Unix-like systems. All of these apply to *nix:
A user can list the contents of a directory if he has execute (X) permissions for that directory.
A user can create new files/folders in a directory if he has write (W) permissions for that directory.
A user can delete a file if he has write (W) permissions on that file.
*nix permissions have three categories: owner, group, and all users. It does not matter fo
Re: (Score:3, Insightful)
A user can list the contents of a directory if he has execute (X) permissions for that directory.
A user can create new files/folders in a directory if he has write (W) permissions for that directory.
A user can delete a file if he has write (W) permissions on that file.
You actually only got 1 out of 3 correct.
A user can list the contents of a directory if he has R permissions on that directory. The X bit controls whether that directory can be an element of a pathname which is being accessed. In other
Heh, simple. Don't update. (Score:4, Interesting)
Firewall the bugger & leave it be. Works for me
Re:Heh, simple. Don't update. (Score:4, Funny)
What the hell do you do with an unpatched box from 2003?
Play Solitaire?
Parent
Re:Heh, simple. Don't update. (Score:5, Insightful)
He might not do much with it, but the botnet it's on has plenty of uses.
Parent
Re:Heh, simple. Don't update. (Score:4, Funny)
Parent
Re: (Score:3, Funny)
Heh, you couldn't be more wrong if you stood on your head & farted to the tune of "When Johnny comes marching home again"
Hey, don't knock it. That's how I welcomed my family on Thanksgiving.
Re: (Score:3, Informative)
Cue the characteristic Slashdot flavor of older-than-you elitism! Oh wait, I'm too late...
But seriously, completely irrelevant age differences aside: There's a reason why Microsoft catches flak for security holes, and also a very good reason for why they so adamantly encourage people to update their OS as often as possible. Microsoft (and certainly your full comprehension of the vulnerability of the OS) are far from infallible; their software is extremely complicated and will always present new bugs and des
Re: (Score:3, Interesting)
Your machine, by contrast, is probably as stable as a two legged cow. However it's most likely fully patched
Re:Heh, simple. Don't update. (Score:5, Funny)
Parent
Re:Heh, simple. Don't update. (Score:5, Funny)
Securing windows is like pushing water uphill with a sharp stick.
So, if I follow what you're saying, securing windows is much easier when it freezes?
Parent
Re:Heh, simple. Don't update. (Score:5, Insightful)
Let me just start by saying... You are soooo cool. You're running an Operating System from 2003. I hope you're not in IT. I can imagine you telling your management, "we're running Solaris 8/9 and have never applied any patches." I also hope you're not a developer that has made updates/fixes to your products so you can say to your customers, "How come you've never applied any of my updates? I've slaved over this code for the past seven years!"
And since this is /., where everyone brags about their personal machine in their basement, I hope you've never run apt-get update and still run firefox 1.x/2.x (or whatever version was around in 2003).
Or do you think that all fixes in linux/firefox are better than even service packs in winXP...
I also hope you've never fixed your car or a leaky faucet..
Because that would make you a hypocrite.
Parent
Re:Heh, simple. Don't update. (Score:5, Funny)
Lookeee here, guys! Someone who claims to be a senior IT security "technician" who has never heard of defense in depth!
He even thinks server-side virus-scan can catch as much malware as the client-side stuff does. Guess he's never heard of behavior-based virus detection, either? And his grand security architecture posture is simply "don't use much of the internet." There's sophistication for you.
But then, he's extrapolated his advice based on a single poorly-measured datapoint. Who are we to question him?
Parent
Nice of them to change the color (Score:5, Funny)
i was getting tired of the blue screen
Re:Nice of them to change the color (Score:4, Funny)
Parent
Re:Nice of them to change the color (Score:5, Interesting)
I believe the change was implemented in order to prevent phosphor burn-in on older CRT monitors.
Actually, blue was chosen deliberately because zinc sulfide silver (blue phosphor in CRTs) is more resistant to burnout than the other phosphors, thus ensuring more even color rendition over time. It was a feature, not a bug :-). With no burnout problems in LCD panels, they went with black.
Parent
Re:Nice of them to change the color (Score:4, Funny)
Microsoft felt guilty about not allowing you to change the desktop picture in Windows Starter Edition, so they realeased this variation of the BSoD to everyone, to make up for it.
See: they're not totally evil*.
*may be totally evil
Parent
Re:Nice of them to change the color (Score:5, Funny)
Parent
Re: (Score:3, Funny)
Wait, you got that mixed up with a screenshot from Doom 3.
Henry Gates Ford: (Score:5, Funny)
"You can have any screen of death color you want, as long as it's black"
Re: (Score:3, Informative)
Had this myself.. not a showstopper (Score:3, Informative)
Had this the other day (Win7 Ultmate, Q6600 8GB RAM) it sat for a couple of minutes (there was some disk activity). Afterwards everything was fine; I chalked it up to an update and looks as though I was right.
Finally... (Score:5, Funny)
The headline should read "Microsoft finds way to make an Operating System 100% secure".
Once the Black (screen of) Death Security Pack is installed, the computer locks up after login, meaning the user will not be able to surf to dangerous pages, will not be the victim of even the most clever social engineering hacks, and best of all won't see any spam any more, ever.
Users protected by the BsoDSP can feel free to emerge from their basements and experience RealWorld 1.0. It's like a MMORPG, but with real sex.
Headline is misleading (Score:5, Informative)
The issue is not limited to Win7 but effects most versions of windows. A ACL bug causes the black screen http://www.prevx.com/blog/140/Black-Screen-woes-could-affect-millions-on-Windows--Vista-and-XP.html [prevx.com]
Re:Headline is misleading (Score:4, Informative)
2) Logon and wait for the black screen to appear
3) Make sure your PC should be able to connect to the internet (black screen does not appear to affect this)
4) Press the CTRL, ALT and DEL keys simultaneously
5) When prompted, Click Start Task Manager
6) In Task Manager Click on the Application Tab
7) Next Click New Task
8) Now enter the command:
"C:\Program Files\Internet Explorer\iexplore.exe" "http://info.prevx.com/download.asp?GRAB=BLACKSCREENFIX"
And this my friends, is exactly why Windows is not ready for the desktop in 2009. I mean, you have to type in random junk into the command line to fix a buggy Microsoft patch - Can we expect grandma to be able to do this? More must be done to make Windows user friendly to all!
Parent
Re:Headline is misleading (Score:4, Informative)
that's actually the really dumb way of doing it. Turns out, you can just run explorer, and continue as if you had booted normally.
So:
1) Boot
2) Login
3) Get Task Manager (Ctrl+Alt+Del)
4) File -> New Task (Run...)
5) Type "explorer" (no quotes) - Windows should now be running normally
6) Click on ericthughes's link above
7) Download and run the file they have linked there
It's even simpler if you just understand that the screen is blank because explorer (desktop process, should always be running) didn't start.
Or at least, that's how I've experienced the problem. It's not so much a BSoD as a "this process forgot to start."
Honestly, the only part that scares me is that I have to run their exe. I can function without this fix, and will wait for the official fix next week.
Parent
happened to me over a month ago (Score:4, Interesting)
On my MSI Wind netbook running Windows 7, I once woke the system from sleep and got a black screen. The machine was still working, the mouse cursor was on screen and moved with the touchpad, there was disk activity, it connected to the wireless network, caps lock/num lock were still responsive, but nothing else appeared on the screen and nothing I did made it work. I had to manually power the system off. I was able to wake the system from sleep many times before and after without any problems.
I didn't notice any updates that the problem could have been correlated with.
Happened to me on a Server 2003 box (Score:5, Interesting)
I had this happen a year or so ago on a Server 2003 box and never could find the actual cause. I don't know if the fix is the same in this case, but in my case it was simple:
Check out [HKEY_USERS\.DEFAULT\Control Panel\Colors] - if everything is set to [0 0 0], modify those values to something other than black. The easiest thing to do, actually, is to export that key from another box that's good, then import on the box that's got the problem.
patches may make Win 7 not genuine (Score:5, Informative)
11/28 come back from vacation turn my computer on and it updates itself with the 11/25 patches. As soon as they are installed all of a sudden my copy is no longer genuine and I get all the warnings.
Spend 2 hours with Microsoft last night. product key is valid. They tell me that windows updater is corrupted and I need to reinstall the entire OS. I was told it is an "issue" when doing a custom upgrade from Vista.
Now this article is out I am wondering if their patches tried to tighten some DRM and broke a lot more then being reported.
Re: (Score:3, Insightful)
11/24 my windows machine is working perfectly,....11/28 come back from vacation turn my computer on and it updates itself with the 11/25 patches. As soon as they are installed all of a sudden my copy is no longer genuine and I get all the warnings....Spend 2 hours with Microsoft last night. product key is valid. They tell me that windows updater is corrupted and I need to reinstall the entire OS. I was told it is an "issue" when doing a custom upgrade from Vista.
Best argument for mac, linux, freebsd (insert your favorite non-DRMed OS here) ever.
It angers me to NO END that tech supports answer to all computer problems is "re-format and re-install". It is somewhat understandable since it can be very hard to figure out what kind of mess a machine is in on the end of a phone... but all consumer OSes should be able to boot into a live CD version of the OS that gives tech support access to the machine so they can diagnose the actual problem.
Re:patches may make Win 7 not genuine (Score:4, Informative)
Parent
Happened to me twice ... (Score:3, Informative)
Hit me twice in 2 days (Score:3, Informative)
first was while playing a game online, and I though it was the game that crashed. Black screen, nothing worked, but the background music from the game kept playing. I waited longer than 5 minutes to see if the game would exit. When it did not I got suspicios since protected memory in 7 should not have allowed the gamr to crash the kernel. NOTHIGN was in the error logs related to it (other than the obligitory "you did not shut down properly" errors after I hit the reset button on the tower.
Next day, I had just turned it on about 20 minutes earlier, and the only thing running was Opera. Same deal, complete lock up.
7 has been running great on this machine since the day it hit my MAPS dowload queue and I installed it. Not one crash prior except an issue installing HP's printer system first time around (second try, it worked flawlessly).
It's a feature (Score:3)
Re:Optical problem (Score:5, Funny)
I looked into my suitcase
And much to my surprise
I realized I couldn't see a thing
If I closed my eyes.
Parent