This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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.
Afraid not in my case. I applied updates today and am up to date. Seeing your post, I turned hardware acceleration back on and relaunched chrome. Immediate google maps defect with placenames. Turned hardware acceleration back off, relaunched chrome, google maps works.
I was able to get a case number and just within the last 2-3 days (Oct 9 2023), the Google maps vs MS Surface Pro somehow, miraculously resolved itself. I made sure that "Hardware Acelleration" was ON and everything appeared normal. I suspect the Knomes of MS were at work here to fix this anomaly. My nephew's Surface Pro did not have this anomaly so I suspect that some people didn't have Automatic Updates and may have dodged this issue.
The MS Surface Pro is still an excellent PC/Tablet and I speak with experience going back to 1977 w/ MS Dos 2.1. With all the PC's I've owned, the Surface Pro is still a very remarkable PC .
(I'm not being compensated by anyone for this commentary).
Does anyone yet know if MS is looking into this issue or not? From previous posts it seems like google support is useless, but at least with MS you could talk to someone. Needs to be fixed ASAP, because turning off hardware acceleration just simply isn't an option!
Windows Mobile and Windows RT were MS attempt to produce OS which is more power efficient for mobile devices. They were both failures. I am hoping MS will continue to invest in this platform and make it a success, rather then following Windows Mobile and Windows RT path. I personally don't like Apple but this is one area it out performs MS.
I think ARM based Windows OS is going to be another MS orphan product, where low volumes will mean support will be poor and long term development is not assured.
The lesson is don't buy new products from MS unless you know it's going to be successful (Catch 22).
I dunno that I agree with that line of thought anymore. Yeah Windows RT (32bit ARM version of Windows 8) had a lot of limitations, and ultimately didn't work out well. However Windows 10 on ARM has been a huge improvement over RT, and now Windows 11 is a significant improvement over 10, so it seems to me they've made consistent progress for the ARM platform. Sure there are still things that don't work, but that list has gotten smaller over the last few years. But I guess time will tell.
Again, I don't consider this issue a problem with ARM itself since it used to work fine.
