ESO keeps asking to install Visual C++ Redistribution (IE Conflict with 2015 vs 2017 redistribution)

[Elliot]

This is an info post in case anyone else runs into this same problem. *EDIT* Forgot to put all the registry keys into the previous post.

So, I ran into an error for some time that took me a while to find the cause of. I got the "cannot find" error where the redistribution files were in the Launcher folder rather than one level higher. I then started getting (due to my UAC security settings) a notice to give permission to run the vc++ 2015 installer every time the game ran. Many people might not get the notice since my settings are at the highest level, and I have not tested if the same request happens at lower levels of UAC control.

The problem appears to be because 2017 overrides 2015 and uninstalls it silently. However, ESO looks for the vc++ 2015 keys in the registry, which are now gone because of 2017's uninstall, to see if the appropriate version is available. Why it is hard coded to only 2015 I do not know, but we have to work with what we have since it is.

Now, 2017 is one of the first distributions I know of (there could be others but I have not run across them) that completely overrides and removes previous versions of the redistributable without question. I also need 2017 for some of my stuff, including my programming, so removing 2017 was not an option. I finally found what appears to be a safe workaround and wanted to share. I hold no responsibility if something should go wrong with this fix in the future, and I apologize for leading anyone astray if it should.

1) I installed vc++ 2015 >

2) went into the registry >

3) exported HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x86 ; HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x64 ;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes ;
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64 >

4) installed 2017 >

5) backed up my registry (Always make sure you back up when messing with the registry as a JIC) >

6) imported the previously exported keys

Now ESO thinks that 2015 is installed, and it is due to 2017 being backwards compatible, and I don't get the error any more. I have only done this with the Steam ESO, and it has played just fine so far. I hope this helps anyone that has been scouring the web for a solution. On the bottom is a copy of my key file that I pulled for reference (your mileage may vary):

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes]

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x64]
"Version"="v14.0.24210.00"
"Installed"=dword:00000001
"Major"=dword:0000000e
"Minor"=dword:00000000
"Bld"=dword:00005e92
"Rbld"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\14.0\VC\Runtimes\x86]
"Version"="v14.0.24210.00"
"Installed"=dword:00000001
"Major"=dword:0000000e
"Minor"=dword:00000000
"Bld"=dword:00005e92
"Rbld"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\VC\Runtimes\x64]
"Version"="v14.0.24210.00"
"Installed"=dword:00000001
"Major"=dword:0000000e
"Minor"=dword:00000000
"Bld"=dword:00005e92
"Rbld"=dword:00000000

*EDIT*
Because I am a dog with a bone, I found a second way to correct this (and it is probably better in the long run). Apparently 2017 has a wonderful habit of not installing its own registry keys. Microsoft's "repair" for this is the run the repair of 2017's installer. I can verify that it will install keys reading v14.16.* as of this post in the proper folders.

[Requimatic]

I'm going to assume that the majority of the launcher issues people have are due to reasons like what you just listed; whether the user realizes it or not.

The difference, though, is that you actually put forth effort and provided data that people can use.. so kudos for that.

It's strange, though, that the launcher is hardcoded to only recognize 2015. Although, on second thought, maybe not so strange since ESO still utilizes the DX9 API, with no hope in sight of upgrading it any time soon.

However, I would open a support ticket with ZOS and provide them with this information; it may make them patch the launcher to work with the 2017 redist as well. (As this would solve probably 50% of the Steam users who experience launcher issues, I'm sure.)

[Elliot]

Originally posted by Requimatic:

I'm going to assume that the majority of the launcher issues people have are due to reasons like what you just listed; whether the user realizes it or not.

The difference, though, is that you actually put forth effort and provided data that people can use.. so kudos for that.

It's strange, though, that the launcher is hardcoded to only recognize 2015. Although, on second thought, maybe not so strange since ESO still utilizes the DX9 API, with no hope in sight of upgrading it any time soon.

However, I would open a support ticket with ZOS and provide them with this information; it may make them patch the launcher to work with the 2017 redist as well. (As this would solve probably 50% of the Steam users who experience launcher issues, I'm sure.)

Thank you for ther suggestion. I just finished doing so but honestly don't even know why I didn't do that after posting this. While all I kept getting was an annoying request for installing vc++ 2015 and the occasional launcher being weird with transparency, this might very well explain the people commenting about being unable to log on after patches. Oh the joy of software development and configuration problems. Anyways, hopefully this will help Zenimax correct the problem.