cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Visitor
Visitor
18,550 Views
Registered: ‎04-20-2017

Problem with Vivado 2017.1 and Visual Studio 2017

Jump to solution

Hello,

 

There appears to be an incompatibility between Vivado 2017.1 and Visual Studio 2017 (latest release).  The issue is that Vivado 2017.1 insists on trying to install Visual C++ 2015 Redistributable, however Visual Studio 2017 replaces that with a newer version.  The Vivado installer and runtime will "make sure" that the C++ 2015 redistributable is installed (even though the 2017 one should be a newer "binary compatible" version and shares the same registry entry).  This means you cannot have Visual Studio 2017 installed with Vivado 2017.1 (the previous Vivado release didn't have this issue, so I have downgraded).

 

I tried various combination of installing Vivado, then VS 2017 etc., but Vivado refuses to start (mentioning the redistributable install failing and suggesting to install in manually - which will fail).  Searching around I found this same issue discussed by Microsoft and it seems Vivado is not following Microsoft "best practices" regarding the redistributable.  From https://developercommunity.visualstudio.com/content/problem/14701/visual-c-redistributable-for-visual-studio-2015-ca.html I quote:

"It sounds like the application's installer, which is attempting to install the Visual C++ 2015 Redistributable, is not checking for existence of newer versions of the redist already installed on the system as described here:

https://msdn.microsoft.com/en-us/library/ms235299.aspx

The Visual C++ 2017 RC Redistributable is a binary-compatible in-place upgrade of the Visual C++ 2015 Redistributable and shares the same registry keys. An application installer that follows the guidance, from the link above, will skip installation of the 2015 redistributable without error."

 

Thanks for your attention and I look forward to 2017.2. :-)

 

-Ken

 

1 Solution

Accepted Solutions
Highlighted
Visitor
Visitor
29,431 Views
Registered: ‎10-10-2015

I resolved this issue by editing the loader.bat file and removed the redistribution check.   In loader.bat, search for "Microsoft Visual C++" and you will see a block of script that checks the version, I just removed that block of script.    (Obviously, always make a copy before editing any 3rd-party script).

View solution in original post

18 Replies
Highlighted
Observer
Observer
18,530 Views
Registered: ‎11-06-2012

I met exactly the same issue, VS2017 and Vivado 2017.1.  Is there a hotfix or workround? Uninstall VS2017 is not practical for me.

 

Cheers

C

0 Kudos
Highlighted
18,374 Views
Registered: ‎04-03-2014

Hi

 

I also have this problem.

 

The workaround I used was to rename "xvcredist.exe" to "xvcredist.old" in the following directories

C:\Xilinx\Vivado\2017.1\tps\win64

C:\Xilinx\SDK\2017.1\tps\win64

 

This stops the loader script from checking whether the runtime libraries are installed.

 

YMMV.

 

Cheers

 

Gavin

 

Highlighted
18,368 Views
Registered: ‎04-03-2014

Oops, also missed out this directory

 

C:\Xilinx\Vivado_HLS\2017.1\tps\win64

 

Cheers

 

Gavin

 

0 Kudos
Highlighted
Visitor
Visitor
18,310 Views
Registered: ‎04-20-2017

Hello,

 

Cool.  Thanks for the work-around.  I'll give this a try soon.

 

-Ken

0 Kudos
Highlighted
Observer
Observer
18,240 Views
Registered: ‎11-06-2012

Hi Gavin,

 

Thank you for the workaround, but it does not work for me; after renaming, the loader script stops if the xvcredist.exe is not found.

 

Cheers

0 Kudos
Highlighted
Visitor
Visitor
18,143 Views
Registered: ‎04-20-2017

Hello,

 

I too was unable to get this work-around to function for me.  I spent much of Saturday uninstalling and reinstalling Vivado 2017.1 and Visual Studio 2017 but never was able to get things running correctly.

 

I hope Xilinx can get this sorted properly (but until then, I can live with older Vivado for a while longer).

 

-Ken

 

0 Kudos
Highlighted
Visitor
Visitor
18,046 Views
Registered: ‎04-26-2017

Thanks this works for me.!!!

0 Kudos
Highlighted
Observer
Observer
18,024 Views
Registered: ‎05-18-2015

Do you know of a fix to this installation problem?

Thanks.

 

0 Kudos
Highlighted
Visitor
Visitor
29,432 Views
Registered: ‎10-10-2015

I resolved this issue by editing the loader.bat file and removed the redistribution check.   In loader.bat, search for "Microsoft Visual C++" and you will see a block of script that checks the version, I just removed that block of script.    (Obviously, always make a copy before editing any 3rd-party script).

View solution in original post

Highlighted
Observer
Observer
12,160 Views
Registered: ‎05-18-2015

Launching the Vivado i get the following error:

 

vvgl.exe - System Error

The program can't start because MSVCP140.dll is missing from your computer.

 

any idea what to do?

0 Kudos
Highlighted
Visitor
Visitor
12,105 Views
Registered: ‎04-20-2017

Hello,

 

Thanks kentcedola, editing the loader.bat and commenting out the section that checked for the redistributable worked great for me.  When I re-installed Vivado 2017.1 (after Visual Studio 2017 was installed) it said "Installation successful, except for redistributable" (and suggested I manually install it - which will fail).  However, after editing loader.bat and adding "rem #" in that redistributable section allowed Vivado to run without complaints and it seems to work fine (doing some limited testing of simulation and bit-stream generation).

 

-Ken

 

0 Kudos
Highlighted
Visitor
Visitor
12,077 Views
Registered: ‎10-10-2015

On my computer, I enter "where MSVCP140.dll" on the command line and displays the \Windows\System32 directory.

 

In theory(ie, guessing), it should be installed via the Visual Studio 2015 or Visual Studio 2017 installer.   Possible enabling the C++ compiler support in Visual Studio 2017 will "work around" the issue.

 

 

 

0 Kudos
Highlighted
Advisor
Advisor
12,060 Views
Registered: ‎04-26-2015

HLS 2017.1 was working for me until today - now it's giving the same error that other people are seeing:

 

ERROR: This host does not have the appropriate Microsoft Visual C++ redistributable packages installed.

Launching installer: "C:/Xilinx/Vivado_HLS/2017.1\tps\win64\xvcredist.exe"

The only version of Visual Studio that I've got installed is 2015, and that has been installed for over a year. OS is Windows 7 x64. As far as I can recall, there have been no updates or other programs installed since HLS 2017.1 was last working. I've tried uninstalling and reinstalling the VC++ redistributable, uninstalling and reinstalling Vivado, and (of course) restarting the PC. Same error every time.

 

For now I'll be using older versions of HLS.

 

 

0 Kudos
Highlighted
Xilinx Employee
Xilinx Employee
12,042 Views
Registered: ‎07-22-2008

In Vivado 2017.1 version 2015 of the Microsoft redistributables is required.

Vivado 2016.x used version 2012 of the Microsoft redistributable package.

 

This topic is addressed in Answer Record 69076 (https://www.xilinx.com/support/answers/69076.html)

 

So far, the top solutions have been

 - to install SP1 for Windows 7 and

 - to set the XIL_PA_NO_REDIST_CHECK environment variable to 1, in order to bypass the vcresidt check (should do same thing as editing the loader.bat solution that was suggested in this thread). 

 

There have also been reports that rebooting the system resolved the issue.  In these cases, the Xinstall.log file actually had a message suggesting that a reboot was needed after installing the 2015 Microsoft redistributables.

 

As we learn more we will update the AR.

0 Kudos
Highlighted
Newbie
Newbie
11,098 Views
Registered: ‎06-05-2017
Thanks!
0 Kudos
Highlighted
Scholar
Scholar
11,084 Views
Registered: ‎03-22-2016

I have seen a ton of problems with Vivado 2017.1 crashing when doing mundane tasks that 2016.4 passes. My friend only solved them by uninstalling Windows SDK (that we use with QtCreator) and removing everything else from PATH but the strictly essential.

 

vitorian.com --- We do this for fun. Always give kudos. Accept as solution if your question was answered.
I will not answer to personal messages - use the forums instead.
Highlighted
Observer
Observer
4,116 Views
Registered: ‎11-28-2018

It seems this is still a problem with Vivado 2018.3; Windows 10 1809; and Visual Studio 2017 15.9.6. Are there any other workarounds? I'd really like to start on our drivers, but I can't if I can't run Vivado and VS 2017 on the same Windows machine...

Viggy

0 Kudos
Highlighted
Newbie
Newbie
142 Views
Registered: ‎09-01-2020
Thanks for the solution, the file to modify by removing the revision block is in this path:

C:\Xilinx\Vivado\2017.1\bin

Just remove this block and it will work:

set ......
...
)
0 Kudos