Surface Pro X, Issues with Google Maps

Anonymous
2023-07-15T20:54:04+00:00

I am using:

Device name *******

Processor Microsoft SQ1 @ 3.0 GHz 3.00 GHz

Installed RAM 8.00 GB (7.54 GB usable)

System type 64-bit operating system, ARM-based processor

Pen and touch Pen and touch support with 10 touch points

Recently, after an update, when using Google maps, the names of the locations disappear.

Initially the maps shows all the detail

But few seconds later when everything is loaded, the town names disappear:

I thought this was a Chrome issue, thus cleared the cache etc. but this not fixed the issue.

I then tried different browsers MS Edge and Firefox. They all have the same issue.

I contacted Google and provided the above info, but they believe this is o/s issue and suggested I contact MS.

Is anyone able suggest how I can fixed this problem?

EDIT: Removed personally identifiable information (PII) from post.

Surface | Surface Pro | Install and update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

82 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-09-21T05:42:40+00:00

    Have you tried contacting Google. Hopeless.

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

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-09-21T05:39:02+00:00

    Yes, this work.

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-09-20T16:11:20+00:00

    Turning hardware acceleration off on chrome resolves the problem with google maps. However, that will cause other issues. If you use backgrounds on conference calls, they won't work without hardware acceleration turned on. So, you need to do without, or switch the setting back and forth.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-09-20T15:29:21+00:00

    I still have a hard time believing Google that this is solely Microsoft's fault, if it's their fault at all. It's Google's app after all; I'd bug the heck out of them. Seems ultimately they're the ones that should be fixing it. Of course, they still haven't bothered to release a native ARM version of Chrome (windows or linux) except for ChromeOS.

    But what's curious is the issue doesn't seem to happen when running Firefox via Ubuntu WSL (windows subsystem for linux) on my Surface Pro X (more specifically "Mozilla Firefox Snap for Ubuntu"). Not sure if any of you would want to dive into the linux world, but it is an option now that gui apps running in WSL is possible.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2023-09-13T12:31:24+00:00

    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.

    Was this answer helpful?

    0 comments