[MCPE-93371] Minecraft not supported on Surface Pro X

Received the message "this device is no longer supported" on my surface pro x

Linked issues

is duplicated by 1

MCPE-93474 Minecraft says "no longer supported" on Surface Pro X?! Resolved

relates to 2

MCPE-92884 Minecraft say that cellphones with less than 768MB of ram will not ever be updated but... Resolved

MCPE-92963 Says will no longer receive updates and unable to update to 1.16.100 Resolved

Attachments

Important News Regarding Minecraft Mobile _ Minecraft - Mozilla Firefox 10_20_2020 11_03_05 PM.png

Comments 26

Justerfrog 2020-07-25T02:12:53Z

https://www.minecraft.net/en-us/article/important-news-regarding-minecraft-mobile

Michael Burch 2020-07-25T02:32:17Z

I've read that but I don't see how it applies. This is a Surface Pro X running Windows 10 Pro, not Windows Mobile. The device supports DirectX 12 (not 10 or below).

IonicEcko 2020-07-26T06:25:38Z

Thanks for the report Michael, I agree that the Pro X doesn't seem to meet the criteria... it doesn't really come close.

We've raised this one with Mojang to take a look.

Dom Cote 2020-07-28T10:55:24Z

One more comment, we at Microsoft are launching an entire new fleet of Snapdragon 850 and 7c based education devices worldwide. I somehow suspect they'll have the same issue with MCEE, correct? I'd ask to get this bug's status changed from "postponed" back to "open" and actually expedite it. There will be literally zillions of panicked support requests from educators pouring in otherwise... thanks!

Chris 2020-07-28T14:26:59Z

@Dom Cote While I believe there may be a slight exaggeration in your above comment, the status has been set to "Community Consensus" which means it is confirmed and has been escalated enough that they are thinking about it and how to go about fixing the potential issue. Have a good day.

16 more comments

John Higgins 2020-08-01T10:22:59Z

My 10 year old daughter came to me, distraught, with this screen showing on her Surface Pro X this morning. We've only had it for a couple of months and it was purchased for school work and to support the ONLY game she plays, minecraft. I'm hoping this is an oversight and not an actual windrawal of support for what is a current product platform.

Solaris Server 2020-08-12T13:47:27Z

How about mine? It says that my computer might no be available for multiplayer, Below is my System Hardware

[media]

Mike DeSimone 2020-09-11T00:12:41Z

I am also seeing this message on my ARM64 Windows laptop, so it looks like the issue is not limited to the Surface Pro X. Is there any plan for an ARM64 specific build?

[media]

James Grant 2020-09-11T08:31:53Z

Is anyone willing to let us know the turn around on this Bug? its a pretty serious issue locking out a lot of users from actually playing the game. I recently tried to play Minecraft on my ARM64 laptop only to be locked out by constant crashes and unsupported device messages. This used to work, and this device clearly supports the latest DirectX build.

[media]

Dom Cote 2020-09-11T14:00:16Z

@James, Minecraft stopped working on ARM64 a few weeks ago. Looks like xbox accounts trigger the crash. When you reinstall/reset the app and DON'T log in to xbox, it runs fine.

There is another bug open here: [MCPE-97724] Minecraft stopped working on Surface Pro X (and other Snapdragons, too?) - Jira (mojang.com) Feel free to vote for that bug, too!

Jamali Phillips 2020-09-19T22:42:11Z

Same issue on Samsung Galaxy Book S which has an ARM CPU. Microsoft login crashes game.

GoldenHelmet 2020-09-29T20:53:59Z

Solaris Server, Mike DeSimone, James Grant, and Jamali Phillips: This ticket is specifically for the Surface Pro X. For the "no longer supported" message on other computers, see MCPE-92963. Do note that the screenshots you have shared that show "DirectX 12" only show the installed driver version, not the feature level of the device.

Michael Burch 2020-09-29T21:26:59Z

updated my screenshot to show the correct tab. Also, this continues to occur in 1.16.40

[media]

rory cameron 2020-09-29T21:43:31Z

this looks like it could be a xbox networking issue. see this message:

[MCPE-97724] Minecraft stopped working on Surface Pro X (and other Snapdragons, too?) - Jira (mojang.com)

i posted in that thread if you look for "xbox networking" in the surface pro x in settings, that is not found, where as it is found in the same build for intel based systems.

GoldenHelmet 2020-09-29T23:52:36Z

I wonder if the "note" in Michael Burch's screenshot about the driver not being digitally signed is related to this issue?

Dom Cote 2020-09-30T15:27:28Z

@goldenHelmet All Snapdragon Chipsets that support Windows (835, 850, 7c, 8cx, SQ1) have DX12 capable GPUs. So while this ticket is indeed about Surface Pro X, it impacts ALL current and coming Snapdragon devices.

I'm betting this is happening because MC is one of the few native ARM apps for Windows. It runs in native ARM32 code because it was designed as a Universal Windows Platform UWP app that could run on Snapdragon-based Lumia smartphones. However, since Windows Mobile and Lumia are dead, supporting ARM32 code probably doesn't make much sense anymore and Mojang doesn't see a business case for porting to ARM64. Am I right?

Sadly, that ARM32 code is the reason why MC runs so awesomely well on all the Snapdragons I've tested. Even the 835 drives a FHD panel at high GPU setting without breaking a sweat.

btw. I tried MC Education Edition on my SQ1, and it runs as an emulated x86 app. But the performance is truly awful compared to the ARM32 native version. It's one of the few emulated apps that suffer noticeably (like Teams).

At IGNITE, Microsoft announced "App Assure" for ARM64 devices. Microsoft now guarantees 100% app compatibility on ARM64 and will help customers make their apps run on ARM free of charge. Perhaps Mojang could reach out? 😉

App Assure now assists with Windows 10 on ARM64 PCs - Microsoft Tech Community

James Grant 2020-10-01T02:35:39Z

@GoldenHelmet I understand that the screenshots don't show the feature level of the device, however prior to the release of 1.16 the Game ran perfectly fine on my surface pro X with no issues, so its rather bizarre that it doesn't support it anymore. Can this ticket please be prioritized, this has been dragging on and is perfectly easy to reproduce.

Jonathan5733 2020-10-21T06:06:55Z

This may be intended, the blog post was updated to say Windows 10 Desktop ARM devices will stop being updated.

[media]

XxDarkzPlayzxX 2020-10-21T07:34:02Z

Well that might ve a problem since in a twitter post i saw mojang said that minecraft will have these last few days until December 2020 please do not end minecraft ;-;.

Mike DeSimone 2020-10-21T18:57:19Z

When did they update the blog post? Previously, it did to mention Windows on ARM in the list of discontinued platforms.

Michael Burch 2020-10-21T19:11:29Z

I have seen the updated blog post that now clarifies that Windows 10 Desktop ARM devices are no longer supported. That seems to indicate this is not a bug, but a result of Microsoft/Mojang dropping support for Windows 10 ARM devices, including their own Surface Pro X.

If that's the case, it makes sense to close this one.

Dom Cote 2020-10-21T20:09:05Z

Umm, please wait before anyone closes this. Give it a week or two.

James Grant 2020-10-24T09:53:35Z

I have to say it is rather disappointing that the approach to this issue is to rule out Microsoft ARM support entirely rather than actually address it. The codebase clearly compiles for ARM given the Android and iOS versions, and its not an issue with DirectX 12 because the game has been leveraging DirectX 12 on the Surface Pro X. So I would like to understand the reason behind this.

Personally, given the direction of the industry, and the support from both Apple and Microsoft pushing for ARM adoption, I think this is a 5 steps backwards kind of situation.

Dom Cote 2020-10-24T10:42:58Z

Again, please give it a week or two. 😉

Dom Cote 2020-11-14T10:17:41Z

Anyone seen this yet? 👍

[media]

Dom Cote 2020-11-18T12:10:41Z

Awesome team! Just got the 1.16.100 update and I can play again. 👍 Thanks for fixing this. 😃

Strange tho: I only get a small subset of graphics options vs. previously. For example: I can't switch on Anti-Aliasing and the rendering distance is either only 5 or 6. This restricts my visibility noticeably. I used to have these all maxed out and still got excellent performance on my Snapdragons. But I'll open a separate bug for this.