Saturday, August 21

BlackBerry Media Sync errors on Windows 7

Okay, here's the scenario. You have a computer that originally used Windows Vista. You downloaded the BlackBerry Desktop Manager 5.0 to it, in order to update and backup your BlackBerry. As part of that whole process, BlackBerry Media Sync was installed to help copy music and pictures between the BlackBerry and your computer.

Now that computer has been updated to Windows 7, and you notice the BlackBerry Desktop Manager 5.0 is now the BlackBerry Desktop SOFTWARE (perhaps we no longer manage things?) 6.0. Being a well trained computer user, you decide to update. Part of that update is to update the BlackBerry Media Sync from version 2.0 to version 3.0.

And then the entire process comes to a screeching halt. You're presented with an error box that says an invalid operating system has been detected, that BlackBerry Media Sync supports only Windows XP SP2 (apparently, they didn't get the memo about Service Pack 3?) and Windows Vista. It warns you that the program will now exit, and it does.

The problem isn't the new BB Media Sync 3.0 software. It works fine on Windows 7. In fact, so does BB Media Sync 2.0, but not the version you have! Version 3.0, you see, detects version 2.0 during its installation and attempts to uninstall the old version. And that promptly fails, giving you the false impression that the software you're trying to INSTALL won't work on Windows 7, not the version that's being UNINSTALLED.

This red herring can lead you on a wild goose chase, and if you give me a moment I'll think of some other archaic metaphors... Anyway, the solution is to update BB Media Sync to the very latest revision of version 2.0. You can download that file by following this link:

BB Media Sync 2.0

Run that, and it will offer to update your copy of version 2.0. Allow it to do so, and you have a Windows 7 compatible edition. Now you need to reinstall BB Desktop Software 6.0, so it can properly update you to the BB Media Sync 3.0.

Here's hoping at least one person is saved the hair-pulling that I endured tracking this fix down! :)

No comments: