A few years ago Microsoft
adopted bought a sync technology and "enhanced" it. Windows Live Mesh turned into Windows Live Sync and then Windows Live Mesh again. Each time that technology changed names I tried it.
I tried it hard to have a successful relationship with Windows Live Mesh. It's imperative that something like this "just works" (TM). I have thousands of files in My Documents, in a development repository, my music and video folders that I
want need to keep in sync between my desktop and laptop. That's because the promised sync would allow me to grab the laptop and go, free of my desk.
In every single interaction Microsoft failed to deliver. The latest fail came today when I saw a blog post about Windows Live update, "This minor release includes numerous updates across all of the programs in the Essential package, including Windows Live Messenger, Mail, Photo Gallery, Movie Maker, Family Safety, Writer, and Mesh."
It's a minor update. It shouldn't break anything right?
It did break. EVERYTHING.
The folder My Documents is no longer syncing - neither to the cloud nor to my laptop. The folder DevRepository is receiving files from the cloud, where just before the update everything was in sync. Together both folders hold about 4.5GB of data. And Windows Live Mesh is downloading this, even though nothing has changed (well, nothing on my data).
The folders My Pictures, My Videos and Prinstcreen all sync to my laptop only (no cloud involved). As you can see Windows Live Mesh thinks BOTH sides are waiting to receive files, effectively a deadlock, since neither side should have been flagged to update anything and each side is waiting for the other.
It also turned off the option to sync Microsoft Office styles, templates, custom dictionary and email signatures I have in place.
Do the engineers behind this product even bother testing what they release? This is most appalling piece of reckless release software I've ever seen.
Other related posts:
Testing the Kingston DataTraveler Locker+ G3
Telecom enforces SSL email, uses wrong name in certificate
Windows XP end of support: 8 April 2014
comments powered by Disqus