Windows Cannot Find Vcredist

I ran the vcredist files, and the x86 one installed without problems, but the x64 one didn't. It just says that one or more issues caused the setup to fail. It says that it can only be installed on Windows XP SP1 or newer platforms, but I have Win Xp SP3, so shouldn't it work? I find it strange that x86 worked bot not x64. Can anybody help?

Windows Cannot Find File Error
Windows Cannot Find Vcredist_x64 Exe Elder Scrolls Online
Windows Cannot Find Vcredist_x64.exe
Windows Cannot Find File
Windows Cannot Find Vcredist X86_2005.exe

Vcredistx64.exe problems can be attributed to corrupt or missing files, invalid registry entries associated with Vcredistx64.exe, or a virus / malware infection. More specifically, these vcredistx64.exe errors can be caused by: Corrupt Windows registry keys associated with vcredistx64.exe / MSDN disc 5063.01.
Is there a way to make ESO Launcher accept both versions of this vcredist? Launcher can't try to call both version of vcredist? They should be cross-compatible anyway. As regular user i don't care if i have 2017 or 2015 installed, but you know, newer is better.

-->

Note

Are you here because you are looking for a download of one of the Visual C++ Runtime files? Go to the Microsoft website and enter Visual C++ Redistributable in the search box. Download and install the redistributable package for the architecture of your computer (for example, x64 if you are running 64-bit Windows) and the version of Visual C++ (for example, 2015) that you need.

When you deploy an application, you must also deploy the files that are required to support it. If any of these files are provided by Microsoft, check whether you are permitted to redistribute them. To review the Visual Studio license terms, see the License terms link in the About Microsoft Visual Studio dialog box in the IDE, or download the Microsoft Software License Terms file. To view the 'REDIST list' that is referenced in the 'Distributable Code' section of the Microsoft Software License Terms for certain editions of Visual Studio, see Distributable Code for Microsoft Visual Studio 2017 and Microsoft Visual Studio 2017 SDK (Includes Utilities and BuildServer Files), or for Visual Studio 2015, see Distributable Code for Microsoft Visual Studio 2015 and Microsoft Visual Studio 2015 SDK. For more information about redistributable files, see Determining Which DLLs to Redistribute and Deployment Examples.

To deploy redistributable Visual C++ files, you can use the Visual C++ Redistributable Packages (VCRedist_x86.exe, VCRedist_x64.exe, or VCRedist_arm.exe) that are included in Visual Studio. In Visual Studio 2017, these files can be found in the Program Files[ (x86)]Microsoft Visual Studio2017editionVCRedistMSVClib-version folder, where edition is the Visual Studio edition installed, and lib-version is the version of the libraries to redistribute. In Visual Studio 2015, these files can be found under your Visual Studio installation directory in Program Files [(x86)]Microsoft Visual Studio versionVCredistlocale. Another option is to use redistributable merge modules (.msm files), which in Visual Studio 2017 can be found in the Program Files [(x86)]Microsoft Visual Studio2017editionVCRedistMSVClib-versionMergeModules folder. In Visual Studio 2015 these can be found in Program Files [(x86)]Common FilesMerge Modules. It's also possible to directly install redistributable Visual C++ DLLs in the application local folder, which is the folder that contains your executable application file. For servicing reasons, we do not recommend that you use this installation location.

Windows Cannot Find File Error

The Visual C++ Redistributable Packages install and register all Visual C++ libraries. If you use one, you must set it to run on the target system as a prerequisite to the installation of your application. We recommend that you use these packages for your deployments because they enable automatic updating of the Visual C++ libraries. For an example about how to use these packages, see Walkthrough: Deploying a Visual C++ Application By Using the Visual C++ Redistributable Package.

Each Visual C++ Redistributable Package checks for the existence of a more recent version on the machine. If a more recent version is found, the package is not installed. Starting in Visual Studio 2015, redistributable packages display an error message stating that setup failed. If a package is run by using the /quiet flag, no error message is displayed. In either case, an error is logged by the Microsoft installer, and an error result is returned to the caller. Starting in Visual Studio 2015 packages, you can avoid this error by checking the registry to find out if a more recent version is installed. The currently installed version is stored in the HKEY_LOCAL_MACHINESOFTWARE[Wow6432Node]MicrosoftVisualStudiovs-versionVCRuntimes{x86|x64|ARM} key, where vs-version is the version number for Visual Studio (14.0 for both Visual Studio 2015 and Visual Studio 2017, because the updated 2017 redistributable is binary compatible with the 2015 version), and where the key is ARM, x86, or x64 depending on the installed vcredist versions for the platform. (You don't need to check under the Wow6432Node subkey unless you are using RegEdit to view the version of the installed x86 package on an x64 platform.) The version number is stored in the REG_SZ string value Version and also in the set of Major, Minor, Bld, and Rbld REG_DWORD values. To avoid an error at install time, you must skip installation of the redistributable package if the currently installed version is more recent.

If you use a merge module that contains a Visual C++ DLL, you must include it in the Windows Installer package (or similar installation package) that you are using to deploy the application. For more information, see Redistributing By Using Merge Modules. For an example, see Walkthrough: Deploying a Visual C++ Application By Using a Setup Project, which also shows how to use InstallShield Limited Edition to create an installation package.

Potential Run-Time Errors