Windows Phone error confuses itself with a desktop

While we’ve all seen error messages, BSODs, PSODs and RSODs, they are becoming less and less common and frequent. And among the hundreds that you may have seen, there is always one or two that will stand out for their irrelevance or down right absurdity.

That’s exactly what has happened with Windows Phone 8. A tweet posted by F-Secure CRO Mikko Hypponen shows exactly what could easily be classed as a “WTF is going on?!” moment.

Showing what looks to be a standard Windows desktop boot error, the phone asked Hypponen the following:

Insert your Windows installation disc and restart your computer.

Em, okay. Where? How?!

But let’s not be naïve here, this could easily be fake, a photo taken with the phone’s camera and the image displayed on screen. But WMPoweruser decided to do a bit of investigating and found that Pocket PC forum member dantist’s Lumia 920 suffered the same fate!

Dantist, real name Johnny Ruokokoski, posted this image on Wednesday and after a push by another Twitter user, Windows Phone Support got involved. You can see their tweets below.

It just goes to show the pitfalls of tinkering with your phone. While Windows Phone Support cannot provide any support to Ruokokoski, we’re sure the community will be able to help him get past this issue. And to echo The Next Web, it’s good to be able to see and prove that Windows Phone 8 runs on the NT kernel.

Source: Twitter via The Next Web | Image courtesy of The Next Web

Report a problem with article
Previous Story

Windows Live Mesh users, it's time to migrate to SkyDrive

Next Story

The pursuit of 'appyness: Which apps do Windows 8 + Windows Phone 8 need most?

52 Comments

Commenting is disabled on this article.

While Windows Phone Support cannot provide any support to Ruokokoski, we're sure the community will be able to help him get past this issue.

Not cannot, Won't.

so put it simply, if window phone has all the necessary input connection, it will be like a really really mini computer in there.

With that being said, all the apps from window 8 can be used interchangeably. In a word "NICE!!!"

It is an interesting piece of news but nothing to get so anxious about folks. Calm down Microsoft haters and just enjoy your non-Microsoft stuff. You don't need to hit the kneecaps of everyone around you like they are your opponents just because they don't use the smartphone you choose to use.

Ideas Man said,
Do you see the ellipses or grab handles that would be visible if he was viewing a picture?

Depends if he is using the default image viewer, anyway looking at the picture it's impossible he took a photo of a computer screen

Edited by PmRd, Jan 15 2013, 12:57pm :

I wonder if Windows RT shares the same error screens hah!

I know for a fact that the Android and iOS trolls are now gonna feed off of this article now and feel like they're a part of a team quick to ridicule. Why take it up the bum?

Hollywood's Karo said,
I wonder if Windows RT shares the same error screens hah!

I know for a fact that the Android and iOS trolls are now gonna feed off of this article now and feel like they're a part of a team quick to ridicule. Why take it up the bum?

They are already among us. Read the posts above yours. And yes Windows RT has the same error screen.

Hollywood's Karo said,
I wonder if Windows RT shares the same error screens hah!

I know for a fact that the Android and iOS trolls are now gonna feed off of this article now and feel like they're a part of a team quick to ridicule. Why take it up the bum?

Same code, same kernel. WP8, Windows RT, Windows 8, Windows Server 2012, and Windows 8 embedded are essentially identical and would have the same set of error screens.

Try hacking Windows RT, bypassing the UEFI and flashing the boot media incorrectly and you will find the same message. Just as you would on all versions of Windows.


(People don't really get that the WP8 running on NT and Windows RT and Windows 8 is really running the same set of code, no matter what platform or version. NT's object manager pulls registry information to identify what version it is on boot. Even Windows 8 x64 shares the same compiled binaries with Windows Server 2012.)

Uplift said,
Awesome.. can't wait to get the Blue Screen of Death on my phone... not.

You won't unless you're flashing it. Any phone will display messages that the normal user will never see if they're flashing it and mess something up.

yowanvista said,
Hmmm.. Never had a kernel panic on Android..

Ya, and I also bet...
you never had the Android become sluggish and unresponsive
you never had an App FC on Android
you never had Android get starved for memory and randomly close essential services.

I hope you were 'trying' to be funny.

thenetavenger said,

Ya, and I also bet...
you never had the Android become sluggish and unresponsive
you never had an App FC on Android
you never had Android get starved for memory and randomly close essential services.

I hope you were 'trying' to be funny.


How cute, could be but nothing much like such a dreaded problem. Never had such things with stock Android.

yowanvista said,

How cute, could be but nothing much like such a dreaded problem. Never had such things with stock Android.

I just had Android grasping for memories as it runs out of it. Just. Now. On stock.

FarCry3r said,

I just had Android grasping for memories as it runs out of it. Just. Now. On stock.

Can't blame Android if you're using a device with insufficient RAM or a dated version of the os itself.

yowanvista said,

Yes I did

Well you failed at understanding that the error above will never be seen by normal users, so your comment of never having kernel panic on android is pretty off topic and reminiscent of a huge android-loving troll. Just to remind you, the guy was trying to flash his phone and failed.

yowanvista said,

Can't blame Android if you're using a device with insufficient RAM or a dated version of the os itself.

Oh yes you can absolutely blame Android, because Google are giving it for free and not enforcing strict hardware guidelines for good performance. Is your head really that far up the green robot's ass?

yowanvista said,

How cute, could be but nothing much like such a dreaded problem. Never had such things with stock Android.

I don't think anyone truly believes this. Either you are lying or your just forgot. Android is just an unstable OS. I'm forced to use it because I want a massive screen and the largest WP8 I can get is the Lumia 920 at 4.5".

ChuckFinley said,
Its hardly the NT Kernel anymore is it ;-)

Uh?

The NT kernel code has been changed very little since 1992, and this includes the SAME CODE running on WP8. The lowest level of the kernel saw very little changes until Windows 7, and in comparison are fairly tiny change overall.

I think you need to look up more information on the NT kernel and technologies.

It's not that surprising really. Yes, a lack of polish, but then again, it's not an error you normally see. It's just sharing kernel, that's all. iOS is sharing kernel with OS X too (Darwin).

Northgrove said,
It's not that surprising really. Yes, a lack of polish, but then again, it's not an error you normally see. It's just sharing kernel, that's all. iOS is sharing kernel with OS X too (Darwin).

Just to be clear, the NT kernel on WP8 and Windows 8 and Windows Server 2012 are the same, the only variance is a few platform specific changes in the kernel code and the different HALs.

OS X and iOS are NOT the same kernel. iOS pretends to expose some of the same APIs as OS X, but not all are handled the same way and are only an approximation of the original exposed APIs. iOS is a smaller 'mobile' kernel derived from Darwin and OS X is a more advanced kernel derived from Darwin. iOS is not derived from OS X even though Apple wants end users to think it is the same.

WP8 has more than just the NT kernel, the entire Windows Platform and set of frameworks are essentially all there, only the WinRT subset are exposed. For example the Win32 API is there, DirectX is there, etc.

thenetavenger said,

OS X and iOS are NOT the same kernel. iOS pretends to expose some of the same APIs as OS X, but not all are handled the same way and are only an approximation of the original exposed APIs. iOS is a smaller 'mobile' kernel derived from Darwin and OS X is a more advanced kernel derived from Darwin. iOS is not derived from OS X even though Apple wants end users to think it is the same.

That's simply not the truth. An error report from iOS6 plainly states: "Kernel Version: Darwin Kernel Version." iOS is actually running the latest version of the Darwin kernel!

Northgrove said,
It's not that surprising really. Yes, a lack of polish, but then again, it's not an error you normally see. It's just sharing kernel, that's all. iOS is sharing kernel with OS X too (Darwin).
iAnything would probably fall flat on its face if it had to run the OS X kernel..

Shadowzz said,
What, iOS shares nothing with OSX (or well they starting to mix them up now)
and OSX runs on XNU.

Darwin is an open source OS made by Apple.

LOL, I love how people just say things. OS X and iOS use the same kernel, always have. Then again, that statment means very little as I suspect 90% of the people here can't explain what the kernel is exactly.

Now give us the rest of Windows RT! I really really want WP9 to include Windows RT. Connect to an external monitor, bluetooth keyboard and mouse... and you're set. Allow execution of unsigned code and the sky is the limit.

rfirth said,
Now give us the rest of Windows RT! I really really want WP9 to include Windows RT. Connect to an external monitor, bluetooth keyboard and mouse... and you're set. Allow execution of unsigned code and the sky is the limit.
That would be a cool idea, but I see it as a niche area. Motorola did it a while ago with Android and the Atrix, I don't remember whether it was a financially successful endeavour or not. If I am not mistaken Lenovo also showed something similar too.

They have already done the hard work. I imagine the only problem is the significant extra storage space that would be required.

georgevella said,
That would be a cool idea, but I see it as a niche area. Motorola did it a while ago with Android and the Atrix, I don't remember whether it was a financially successful endeavour or not. If I am not mistaken Lenovo also showed something similar too.

Yeah, I don't think it was successful as no subsequent hardware came out. It was a very promising idea though.

rfirth said,
They have already done the hard work. I imagine the only problem is the significant extra storage space that would be required.

Agreed, the storage is a big issue. But more than that. When you have to carry a monitor around (Or hope to chance upon one wherever you arrive), you might as well bring a laptop... I like the idea, but it's much more complex than bringing a keyboard.

I didn't for once second doubt that it wasn't the NT kernel but its pretty cool to see some hardcoded stuff in there that still references the windows 8 error environment! Also excellent work from windows phone support as usual!

Yes it should. As the support said, this will not be happening for regular customers. This is a standard message from the kernel that it cannot find the source medium. Most likely from an external flash/install.

x-byte said,
Yes it should. As the support said, this will not be happening for regular customers. This is a standard message from the kernel that it cannot find the source medium. Most likely from an external flash/install.

Exactly. Let's not ignore that he was flashing his phone to produce this error... It isn't something someone is going to just see when playing a video or anything. LOL

Ok then , go ahead and insert a windows installation disc if you manage to do it i will accept your trolling as the real thing...

DaveBG said,
Ok then , go ahead and insert a windows installation disc if you manage to do it i will accept your trolling as the real thing...

What the hell? Is there something wrong with you? I don't know who that reply was intented to but in any case the only trolling is being done by you by completely not knowing what the **** you are talking about.

x-byte said,
Yes it should. As the support said, this will not be happening for regular customers. This is a standard message from the kernel that it cannot find the source medium. Most likely from an external flash/install.

Actually no it isn't.

It's asking you to insert your Windows medium to repair the issue, it's not the actual issue.