Windows 10 Insider builds will now feature a Green Screen of Death (GSOD) instead of the classic Blue Screen of Death (BSOD) error page we have all become accustomed to.
The change was teased on Twitter by Matthijs Hoekstra, Senior Program Manager for Windows Enterprise Developer Platform, and spotted by a user that goes by the nickname of Chris123NT.
According to Hoekstra, only Windows 10 Insider builds will feature the green error screen, while stable Windows 10 versions will continue to use the classic blue-themed error page.
Hoekstra didn't elaborate on the reasons behind the color change. One reason may be that Microsoft is trying to help support staff, who'd have a much simpler task differentiating from errors in stable Windows 10 versions and Insider builds, which are in-dev versions, meant only for testing, and prone to more problems.
Color-coding the error screens would allow support staff to triage bugs and prioritize customers.
GSOD added in leaked Windows 10 build
The current Green Screen of Death is active with the Windows 10 Insider Build 14997 that leaked online this week.
This same build also introduced a blue light filter, a gaming mode for Windows 10, default blocking of Flash in Edge, and a "pause" option for Windows update operations.
Since everybody loves epic fails and BSOD screens are some of the funniest ones, here's a giant BSOD captured during a projection of the latest Star Wars film, Rogue One. If you're interested in more BSOD fails, check out the PBSOD Reddit thread and keep an eye out for a similar thread for GSOD screens.
My friend @martysimpson went to see #RogueOne. His theater got the "blue screen of death" and that sucks but I'm sorry this is hilarious. pic.twitter.com/rlCJirlEqL
— Brian Linder (@brianonthescene) December 27, 2016
Comments
JohnC_21 - 7 years ago
Perhaps Microsoft should spend less time on changing colors and more time on determining why Windows 10 has so many Wifi connection problems.
woody188 - 7 years ago
It's because their IPv6 implementation doesn't revert back to IPv4 properly when IPv6 isn't supported or fails. Disable IPv6 in your network adapter and nearly every NIC issue disappears.
wgianopoulos - 7 years ago
This is completely lame. Goes against the normal Green is good, Red is bad paradigm, which I believe is required in Germany.
wgianopoulos - 7 years ago
If I recall correctly, a Green is good Red is bad thing in Germany is why the led color for hard disk activity was changed from red to green way back in the day.
zuf - 7 years ago
different color, same problems
Captain_Chicken - 7 years ago
Wow. Whatever Microsoft can do to distract from real issues, they will do.
Viper_Security - 7 years ago
I dont use Microscum's W1nD0z3. but they should REALLY work on fixing the issues that cause the error. and changing it to green?....... what the actual F***. green means go /good. red means stop/bad. blue means yield/ be careful.
So why ON EARTH would They change it to green?. no one gives a damn about the colors, just fix the issue.
I still think Microscum jumpedthe gun on releasing w1nd0z3 10
woody188 - 7 years ago
Probably going for their Green Business certification.
HolyCowz - 7 years ago
I think they may be changing it as may of the default colours are blue and the same blue as the bsod blue but why green I can only assume it is because green means its ok ie they don't want you to panic every time it happens lol. I still don't get how Microsoft gets away with windows 7 and vista update shenanigans when it is so obvious they are doing it to push people to 10. Lets be honest Bill and his crew don't care they own half the worlds recourse's it's all a laugh to them now.
rarson - 7 years ago
I've been on the Insider Fast Ring since the Technical Preview and I've never gotten a single blue screen. Ironically, it's the everyday user of regular Windows 10, my customers, that get them frequently. A lot of it comes down to how you use the computer, but there are just too many common issues for average users caused by the way Microsoft is handling Windows 10. Average users are now beta testers, too, but they're not capable of actually beta testing software.