Is Cloud Clipboard Syncing Service counterpart at Microsoft servers working?
Hi everyone! I have just given up trying to make Windows Cloud Clipboard Syncing work. Yes, I have tried roughly everything to fix it - except for a rain dancing. For instance, prayers and candles were not helpful at all 😋. Now, being a bit more serious, I will not enumerate in detail here everything I have tried but it ranged from from UI settings on and off, logging with a local account and back with Microsoft account, restarting and setting values to entries on Registry and Group Policy Editor. No joy! My theory: the problem is not at my side. Not on my account, my computers nor my Windows configuration. I firmly believe that the service at Microsoft side is not coping with the huge load of Ctrl+C from every user worldwide with 2+ devices logged in with the same account. So, my question is quite simple: how do I know if the Windows Cloud Clipboard Service counterpart at Microsoft servers is working properly? Is there a tool to forcefully test this API interface and thus say "you computer configuration is at fault" or "sorry, we have dropped the ball and the Clipboard Cloud Service is not available right now"? Is there a way to download the Cloud Clipboard associated to my account somehow to help debug the problem? Note: although this problem seems unrelated to my Windows version, I am running on both machines Windows 10 Pro v1909 (retail, not insider) build 18363.1082. Thanks a lot for your inputs! Sandro edit 2020-11-06: this discussion has been also posted at https://www.askwoody.com/forums/topic/is-cloud-clipboard-service-counterpart-at-microsoft-servers-working/#post-2310042 .Microsoft Account Troubleshooter: not updated since Oct. 2013
Hi! I downloaded today (2020-07-14) the tool ( https://social.technet.microsoft.com/wiki/contents/articles/13976.how-to-troubleshoot-microsoft-account-issues.aspx ) and opened it with 7-zip. The files there are from Oct. 2013. It means that the tool might not know about changes to account authentication. Therefore, it may report wrong conclusions/detections. I may be wrong but it seems to me that the tool needs some updating.
