Subject: Feedback and questions about unstable Europe map update via MyDrive Connect
Dear TomTom Support,
I am writing to share some serious concerns about the reliability of the update process for my TomTom and to ask whether there are known issues or recommended workarounds.
Today (7 December 2025) I installed the new Europe map via MyDrive Connect on my Windows desktop. I assume this map has been on your servers for a few days already, as I was away on holiday and only updated on my return.
The experience consisted of two very different “rounds”:
First update attempt – repeated failures
During the first attempt, the download/install process repeatedly froze at various percentages (14%, 36%, 43%, 47%, 52%, 69%, etc.). The only way to get any further progress was to quit MyDrive Connect from the taskbar and restart it. Each restart gave a small “delta” increase in the percentage, but the process was extremely unstable and unpredictable.
At the same time, I kept seeing a pop-up message saying (in Dutch) something like:
“Downloaden van inhoud voor je GO 5000 met ID QR1296K02004
Raadpleeg de netwerkinstellingen.
De URL is als volgt:
”
This “network settings” message is very alarming: it makes it look as if the whole update has failed, even while the main window sometimes still shows progress. It really throws you off your chair, because you don’t know whether to trust the process or not.
At one point, after a failure, my device even showed “No maps available”. That is quite dangerous if someone needs to rely on the device shortly afterwards.
see the famous ''orange band'' error screen
For context:
– My internet connection is a wired fibre connection, tested at about 1.1 Gbps.
– The PC and network were otherwise idle.
– I used the same USB port and TT supplied cable throughout.
Given this, I find it hard to believe that this was a simple network issue on my side. It feels more like a problem in MyDrive Connect’s caching/resume logic or error handling for large (±9 GB) updates.
Second update attempt – suddenly stable..this is the 2nd round-after the 1st hellish round -
Later, using the same PC, same port, same cable and same internet connection, the procedure is repeated . This time the download and install went through much more smoothly, and the second phase (“System is being updated”) completed successfully. No network changes were made between the first and second attempts.
This contrast makes me suspect that something in the first attempt (a corrupted cached chunk, an incomplete package, or a bug in the resume mechanism) caused all the instability, rather than my hardware or connection.
''Device sleep during critical updates'' ::
A further point of concern is that the device tries to go to sleep during the long internal update phase (black screen with “Updating – Do not disconnect your device”). There is no clear “stay awake during updates” mode that I can find. This means a user has to physically monitor the device and wake it up periodically to avoid interruptions. For such a critical firmware/map operation this feels very fragile and user-unfriendly.
What I am asking for
Concretely, I would like to ask:
– Are there any known issues with MyDrive Connect and the latest Europe map update for devices (e.g. problems with partial downloads, cached files, or resume behaviour)?
– Is there an official recommended recovery procedure for situations where MyDrive repeatedly stalls and the device ends up with “No maps available”?
– Can the confusing “network settings / URL” pop-up be improved, so that users are not misled into thinking everything has failed while the main progress bar is still valid?
– Is there any way (now or in a future software update) to prevent the device from going to sleep during a long update, so the process can safely run unattended?
in addition to the symptoms above, I want to explicitly mention the technical behaviour I observed during the failed first attempt, because it appears directly related to how MyDrive Connect handles chunked downloads and integrity checks:
– Each map portion goes through:
Download chunk → Verify chunk (CRC check) → Send to device → Install internally.
– If any chunk fails (bad cached block, internal retry glitch, USB hiccup, or momentary server lag), MyDrive Connect completely freezes, even though the UI does not say the process is corrupted.
– During my first round, this required 5–15 forced restarts of MyDrive Connect before passing certain “barrier percentages.”
– Once I passed ~60%, the update became noticeably more stable.
– Past ~70–80%, the behaviour matched what many users report: the installation suddenly skips smoothly:
80 → 90 → 96 → 100.
– If the percentage stays frozen for more than ~3–4 minutes, I learned that it is already stuck, even if the interface does not admit it.
I also closely monitored the system tray icon behaviour of MyDrive Connect:
– Green icon = stable connection / chunk accepted.
– Orange icon = retrying, chunk rejected, interrupted, or waiting for connection.
During the first round the icon constantly flipped to orange, despite my very stable 1.1 Gbps fibre connection.
This created a situation where I effectively had to:
• “babysit MyDrive”
• “babysit the USB connection”
• “babysit the device” (which also tries to enter sleep mode mid-update)
It should not be necessary for a user to sit beside the PC for over an hour, repeatedly killing the taskbar process to make the update crawl forward.
To summarise the symptoms clearly:
• stuck at repeating fixed percentages (14, 36→44→52→69…)
• progress resumed only after restarting MyDrive Connect
• recurring “Downloaden onderbroken” popup
• device attempting to sleep during critical firmware/map update
• misleading “no maps available” orange error screen
• update failing to resume gracefully
• need to kill MyDrive from taskbar 10+ times
• USB/device babysitting required
• internal retry/integrity logic seems to break silently
• UI gives no indication of corrupted chunks
• psychological damage (to be taken humorously — Murder by Death meme)
All of this is unacceptable for a 9GB critical map update with no contingency mechanism.
I hope this feedback can be forwarded to the appropriate product/engineering team. A more robust and transparent update process would make a big difference for long-time TomTom users like me/US !
Dear TomTom Support,
I am writing to share some serious concerns about the reliability of the update process for my TomTom and to ask whether there are known issues or recommended workarounds.
Today (7 December 2025) I installed the new Europe map via MyDrive Connect on my Windows desktop. I assume this map has been on your servers for a few days already, as I was away on holiday and only updated on my return.
The experience consisted of two very different “rounds”:
First update attempt – repeated failures
During the first attempt, the download/install process repeatedly froze at various percentages (14%, 36%, 43%, 47%, 52%, 69%, etc.). The only way to get any further progress was to quit MyDrive Connect from the taskbar and restart it. Each restart gave a small “delta” increase in the percentage, but the process was extremely unstable and unpredictable.
At the same time, I kept seeing a pop-up message saying (in Dutch) something like:
“Downloaden van inhoud voor je GO 5000 met ID QR1296K02004
Raadpleeg de netwerkinstellingen.
De URL is als volgt:
”
This “network settings” message is very alarming: it makes it look as if the whole update has failed, even while the main window sometimes still shows progress. It really throws you off your chair, because you don’t know whether to trust the process or not.
At one point, after a failure, my device even showed “No maps available”. That is quite dangerous if someone needs to rely on the device shortly afterwards.
see the famous ''orange band'' error screen
For context:
– My internet connection is a wired fibre connection, tested at about 1.1 Gbps.
– The PC and network were otherwise idle.
– I used the same USB port and TT supplied cable throughout.
Given this, I find it hard to believe that this was a simple network issue on my side. It feels more like a problem in MyDrive Connect’s caching/resume logic or error handling for large (±9 GB) updates.
Second update attempt – suddenly stable..this is the 2nd round-after the 1st hellish round -
Later, using the same PC, same port, same cable and same internet connection, the procedure is repeated . This time the download and install went through much more smoothly, and the second phase (“System is being updated”) completed successfully. No network changes were made between the first and second attempts.
This contrast makes me suspect that something in the first attempt (a corrupted cached chunk, an incomplete package, or a bug in the resume mechanism) caused all the instability, rather than my hardware or connection.
''Device sleep during critical updates'' ::
A further point of concern is that the device tries to go to sleep during the long internal update phase (black screen with “Updating – Do not disconnect your device”). There is no clear “stay awake during updates” mode that I can find. This means a user has to physically monitor the device and wake it up periodically to avoid interruptions. For such a critical firmware/map operation this feels very fragile and user-unfriendly.
What I am asking for
Concretely, I would like to ask:
– Are there any known issues with MyDrive Connect and the latest Europe map update for devices (e.g. problems with partial downloads, cached files, or resume behaviour)?
– Is there an official recommended recovery procedure for situations where MyDrive repeatedly stalls and the device ends up with “No maps available”?
– Can the confusing “network settings / URL” pop-up be improved, so that users are not misled into thinking everything has failed while the main progress bar is still valid?
– Is there any way (now or in a future software update) to prevent the device from going to sleep during a long update, so the process can safely run unattended?
in addition to the symptoms above, I want to explicitly mention the technical behaviour I observed during the failed first attempt, because it appears directly related to how MyDrive Connect handles chunked downloads and integrity checks:
– Each map portion goes through:
Download chunk → Verify chunk (CRC check) → Send to device → Install internally.
– If any chunk fails (bad cached block, internal retry glitch, USB hiccup, or momentary server lag), MyDrive Connect completely freezes, even though the UI does not say the process is corrupted.
– During my first round, this required 5–15 forced restarts of MyDrive Connect before passing certain “barrier percentages.”
– Once I passed ~60%, the update became noticeably more stable.
– Past ~70–80%, the behaviour matched what many users report: the installation suddenly skips smoothly:
80 → 90 → 96 → 100.
– If the percentage stays frozen for more than ~3–4 minutes, I learned that it is already stuck, even if the interface does not admit it.
I also closely monitored the system tray icon behaviour of MyDrive Connect:
– Green icon = stable connection / chunk accepted.
– Orange icon = retrying, chunk rejected, interrupted, or waiting for connection.
During the first round the icon constantly flipped to orange, despite my very stable 1.1 Gbps fibre connection.
This created a situation where I effectively had to:
• “babysit MyDrive”
• “babysit the USB connection”
• “babysit the device” (which also tries to enter sleep mode mid-update)
It should not be necessary for a user to sit beside the PC for over an hour, repeatedly killing the taskbar process to make the update crawl forward.
To summarise the symptoms clearly:
• stuck at repeating fixed percentages (14, 36→44→52→69…)
• progress resumed only after restarting MyDrive Connect
• recurring “Downloaden onderbroken” popup
• device attempting to sleep during critical firmware/map update
• misleading “no maps available” orange error screen
• update failing to resume gracefully
• need to kill MyDrive from taskbar 10+ times
• USB/device babysitting required
• internal retry/integrity logic seems to break silently
• UI gives no indication of corrupted chunks
• psychological damage (to be taken humorously — Murder by Death meme)
All of this is unacceptable for a 9GB critical map update with no contingency mechanism.
I hope this feedback can be forwarded to the appropriate product/engineering team. A more robust and transparent update process would make a big difference for long-time TomTom users like me/US !
Last edited:
