Topoactive Europe map download impossible

I do have a different issue but similar. I got the 965 few days ago - after the firmware was upgraded to 3.58 the pre-installed map did not work for me (the map did not show any details of my location). The map manager told me there is an update available, so I connected the 965 to my Mac and and synced the map with Garmin Express. However, I think the map install was successful but the map manager of the watch is still saying there an update available (TopoActive Europe 2022.11). Weird!

In addition, after disconnecting the watch from the Mac - the watch did not recognise that the USB cable was disconnect and remained in USB charging mode for a while. 

Exactly same problem as Zipfll here (I mean the problem with pending map update despite updating it via USB cable).

It is also not clear to me - is the watch telling me the version, which is installed (2022.11) or which update is available? (version is showing when I press the Start button under "Update available"). It is also not clear when using Garmin Express because no version is shown of the installed map

That's strange. Looks like the latest map version was installed but still has the "update" flag. Let me remove the map and re-install it.

No change after removing and re-installing the map - the map manager is still saying there is an update. File structure looks the same

So last night I managed to install the Topoactive Europe 2022.11 map using Garmin Express and my pc (before it would fail at 50%).

Now I have the same problem as others with the 'Update available' prompt in MAP settings, however in the map configuration settings it shows 2022.10 installed. This issue I believe is already a known bug, at least on the 955, but I guess also on the 965 too... 

https://forums.garmin.com/sports-fitness/running-multisport/f/forerunner-955-series/311253/maps-manager-bug#pifragment-1279=2

I didn't get down to the bottom of my original garmin express issue, or the impossibility to download from the watch directly via Wi-Fi. Anyway despite the bug it seems to be working correctly now. 

Yes, I did