I just started having the same issue today with my ONE V2. Sometimes I can get it to work, other times not. It's completely unpredictible.
It's that same "SAM server" error. It's not clear whether the issue is with the connection between the device and the computer or between the computer and Tomtom's update server. My computer is recognizing the Tomtom and even HOME is seeing that it's connected - since HOME does give me the option of disconnecting it. I can browse Tomtom on Windows Explorer. So, I'm going with it being an issue with the Tomtom server. What boggles my mind is that HOME just completely borks out if it can't reach the server as opposed to still letting you access your device. It would be like your computer refusing to boot up and let you use MS Word because it can't connect to the internet. It's strange and frustrating. Especially since it had been working great prior to the update to HOME 2.
Unfortunately I have just found that my map is corrupted... Just a white screen with a bunch of Dunkin Donuts logos floating around. Since I can't get HOME to work, I guess my tomtom is just an expensive paperweight for the time being. Sweet
Further experimentation with the expensive paperweight...
I had manually copied the folders off my tomtom to my computer as soon as I got it home. I also have backed it up with my OEM HOME install (don't know which version, but not HOME 2) AND in HOME 2 after it updated. I just tried copy/pasting my USA_and_Canada folder from my manual copy back into the expensive paperweight, no dice. "the file or directory is corrupted and unreadable" is what I get. Is it my tomtom that is corrupted or my backed up files? Who knows. So, expensive paperweight goes in it's case to be ignored.