Surface Pro X, Issues with Google Maps

Yes, I agree. The issue is the entry=ttu at the end.

I have the same issue. It is happening on Chrome and Edge. It happened a few weeks ago and I believe it coincided with an OS update for Surface. Have tried everything suggested and more. There is a bug fix needed on the surface OS.

Further clarification, when first attempting to access:

www.maps.google.com - street names appear and it looks like all is well; however, several seconds later, the URL is appended with: https://www.google.com/maps/@40.927232,-74.022912,14z?entry=ttu - and street names disappear. If you remove the ?entry=ttu - street names reappear, then the ?entry=ttu returns and street names disappear

I have attempted to turn off AND turn on maps access to navigation. I have attempted to turn cellular data off.

Has anyone got this issue resolved?

I got another update today, 2023-09 Cumulative Update for Windows 11 Version 22H2 for arm64-based Systems (KB5030219), and the issues still exists on all browsers, MS Edge, Chrome and Firefox.

I'm not entirely convinced that the google map issue could be from an ARM64 based system. I think it's an inherent conflict with the software updates. Sometime around March 2023 a MS Update disabled my Surface Pro camera. When complaints came pouring in, MS fixed it almost immediately (i.e., at least one week in a "Microsoft Minute".)

There may be some skullduggery involved by the "knomes of Microsoft HQ" in this issue since MS Bing Maps works fine. In fact, MS Bing Maps works in Edge, Chrome and Firefox. If it were an ARM64 processor issue then I think it would affect Bing Maps and other Mapping software as well. As mentioned previously, our Lenovo Laptop w/ Windows 11 works very well.

I would like to remind the MS community that about 35 years ago (1988) MS came out with "Streets and Trips" that had a complete GPS active mapping program. Now google has become a verb in the English language so just "Google it". One can only imagine the enormous amount of money involved in the current wave of mapping software. Could there be legal and commerical forces at work with this issue? Is this issue by design or by accident, that is the question.

I have a Service Request with MS currently and they have promised to make it their top priority since the complaints are now coming in from Surface Pro users around the world.

I agree, and I had started a similar post, but didn't finish it.

The fact that it works when hardware acceleration is disabled to me points more to the video/graphics driver than the cpu. Plus like you said, the fact that it used to work tells me it's not anything inherent to the ARM cpu architecture, and but a software bug. Now who's bug it is the question, Microsoft or Google. But since it broke after a Microsoft update, it seems Microsoft ought to be be able to fix it even if Google's software is doing something it shouldn't that is really the cause.

It's encouraging to hear you're making progress with the Service Request; thanks for sharing that!

It's a crossover device, and I purchased mine because I wanted the builtin in SIM card functionality with unlimited data. But this google maps thing was frustrating because it wasn't a problem until an update in the OS a few months ago. It happened immediately after a MS Patch update, and had been working fine for me for nearly two years.

It kinda works now with hardware acceleration turned off in chrome browser. But I still hope they fix it eventually.

I found this useful. I was not able to turn off acceleration in Windows, but was able to do it on the Chrome - Settings - System - and then turn off "Use hardware acceleration when available". That seems to work.

Very disappointed with Surface Pro X, their ARM architecture, and overall performance. I think for my small business purposes it would be much wiser to go with a high performance Dell laptop. That is what will happen next time. they took zero responsibility for two other incompatibility issues with hardward and software due to their decision to use ARM. Caveat emptor.

Have you tried contacting Google. Hopeless.

The community does not have access to the development team. Go figure!

I have not tried in this case no. But I guess that doesn't surprise me. It's a shame.

Hopefully one of these two companies figures out a fix eventually (if it's even on their radar which I'm not confident about like you suggest), or accidentally fixes it with some future update.