SONAR X1 still using outdated, unsupported, buggy MSVC++ 2005 redistributable

If you have a 64-bit Windows OS, after installing SONAR X1 you'll likely see a file named msdia80.dll in the root of the hard drive from which you installed the product. Why? Because Roland is still using an old, buggy, unsupported version of the Microsoft Visual C++ 2005 redistributable, installing it even if you already have the later version of your system. Besides the fact that this version will put your computer at risk, its installer is notorious for not putting its DLL in the correct place.

To fix this after installing SONAR:

1. Go into your Windows Control Panel and remove the "Microsoft Visual C++ 2005 Redistributable (x64)" version 8.0.56336.
2. Download and install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package ATL Security Update, which should show up as "Microsoft Visual C++ 2005 Redistributable (x64)" version 8.0.59192.

This has been a known, reported issue since SONAR 6 back in 2007.

Hehehe, those was exactly my thoughts while installing SONAR X1.

Why the heck are they still using the Microsoft Visual C++ 2005 Redistributable? :-)

LOL Dave :-)

I'm really glad that there are people here who point out the relevant info. Thanks man.

Many thanks for this helpful important info!

I saw X1 installing the C++ 2005 redistributable, but then a moment later, it also showed it was copying "2010" files. Are the two unrelated, and the 2005 version still needs updating?

 
They are unrelated and are two different redistributables. We would love not to install that POS :-) There are however older 3'rd party plugins that we do not build ourselves that rely on that installer hence we need to continue to install it for now. Otherwise they would not run on a new Windows install.

SONAR itself and all the newer stuff we build uses the latest generation compiler and requires the VS2010 redistributable.
 

Noel, I understand why you are installing the VC++ 2005 redistributable, and I don't mind so much.

But do you want to comment on why you are forcing an install of an outdated, unsupported version of that redistributable, which contains a security risk, and ignoring whether our system already has an updated version of the VC++ 2005 redistributable? (See my original post for the references.)

Will the upcoming X1 patch have an updated VC++ 2005 redistributable, or will I once again have to clean up after SONAR's installer just to remove the security risks and the DLL littering the root directory of my hard drive?

We have no control over what the Microsoft installer does unfortunately - all we do is launch it. There is no Microsoft documented way to determine whether the component is installed either. In theory the installer should do that check and do nothing. We'll look into using the updated redist.
Regarding the upcoming update, updates typically do not install redist's since the main application is already installed. So you shouldn't have to repeat what you did.

bvideo


The installer apparently attempts to dial home. I wonder what happens if there is no internet?
Bill B

Microsoft doesn't know about you, your wife, your first born, that pirated copy of Win95 you still have laying around etc....

Noel Borthwick [Cakewalk
]

I saw X1 installing the C++ 2005 redistributable, but then a moment later, it also showed it was copying "2010" files. Are the two unrelated, and the 2005 version still needs updating?

 
They are unrelated and are two different redistributables. We would love not to install that POS :-) There are however older 3'rd party plugins that we do not build ourselves that rely on that installer hence we need to continue to install it for now. Otherwise they would not run on a new Windows install.

SONAR itself and all the newer stuff we build uses the latest generation compiler and requires the VS2010 redistributable.
 

You don't have to install the redistributables at all.

If you avoid using the shared MSVCxxx.dll for runtime, and use linked in runtimes (/MT switch) you do not need the redistributables.

So it's a choice you can make.

I've checked and its already installed that update of the file on my system - It's dated today, same day  I installed X1 so its either dialled home or the new distributable was included in the SONAR files.
 
so it might pay to have a look at your system in Programs and features in WIN 7. Don't forget to click view Installed Updates so that it becomes visible in the window.

If you find C++ 2008 on your machine after the X1 install, you might just go ahead updating those as well.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2051a0c1-c9b5-4b0a-a8f5-770a549fd78c


@chrisharbin: I'd uninstall both, then reinstall the new.

Thanks "Yes", update to SP1 make many graphical bugs fixed in X1, but not all graphic bugs..


Its bad that they have continue use this old pack...why don't they include and use the new 2010 version instead? AFAIK it include exactly the same building blocks just updated version of it.



Regards
Freddie

I dunno...second guessing the developers might introduce untested variables into the system and make X1 unstable.

I used to be a Windows developer and nothing is worse than someone upgrading the OS, language, dll's and or drivers that haven't been tested.

There is more to X1 than a pretty face and Cakewalk are reasonably well connected to Intel and Microsoft. I'm leaving the heavy lifting to them.

sdpate


I dunno...second guessing the developers might introduce untested variables into the system and make X1 unstable.

I used to be a Windows developer and nothing is worse than someone upgrading the OS, language, dll's and or drivers that haven't been tested.

There is more to X1 than a pretty face and Cakewalk are reasonably well connected to Intel and Microsoft. I'm leaving the heavy lifting to them.

Yeah I'm a little uneasy about it as well so I think I'll sit tight on this one until official word comes down the pipeline.