Vivado 17.2 and Windows 10 1709 (Fall Creators Update)

[woitha]

After the update to Windows 10 1709 (Fall Creators Update) starting Vivado aborts with error "R6025 - pure virtual function call". I went back to  Windows 10 1703, so I can continue working.

However if other people have the same issue, the problem should be solved.

[nupurs]

@woitha

While this update for Windows 10 is not officially supported with Vivado 2017.3, the following work-around is available:

1. Navigate to (Vivado Installed Directory)\2017.3\bin\unwrapped\win64.o
2. Backup 'vivado.exe' by renaming it to 'vivado.exe.backup'
3. Copy 'vivado-vg.exe' and paste it into the same folder.
4. Rename 'vivado-vg - Copy.exe' to 'vivado.exe'

After the above steps are followed, Vivado will launch normally.

[weberbe1]

Thank you for that tip!

It helped very much with vivado 2017.2

Is ther any work around for 2017.3. It won't start. After 2 minutes a get a timout from start manager.

Microsoft has done a very well job with this update. destroy many hours of work and searching for workarounds of a broken update...

Unfortunately I have none roolback option for this last fall creators update from Microsoft

[weberbe1]

Hi, have discovered AR#69908 with the same solution for Vivado 2017.3. Works fine for me!

[samcossais]

I had almost the same problem with Vivado 2017.3, launching it gave a time out since I updated Windows to v1709, and your solution solved the problem, thank you.

[jgerstenberger]

This workaround fixed my problem with 2017.2 failing to launch.

How can Xilinx think they can get way with saying the latest release of Windows 10 is not supported?!?

Just for the record, my Quartus tools run just fine.  In fact, all other software on my PC seems to run fine.

[jau1993]

Hi I have same issue with vivado lab edition 2017.2 but i couldn't find vivado-vg.exe. Is this a file specific to the design suite? is there is a similar solution for Lab edition?

[dr_k]

Thanks Nupur,

I'm back up and running again.

[palmercliff]

Well done, Nupurs!  Your solution works for Vivado 2017.3.1 as well.

[vidigi]

Hi, I Recently updated to Windows 10.0.16299 build 16299 and Vivado doesn't work anymore. I tried the solution above but the software continue to not start. Any ideas? I have to come back to the older version of windows?

[mark1234]

Yes same problem here. Windows did big update last nite 13 Dec 17 and vivado 2017.3.1 failed to start. - (.bat timeout)

Windows 10 Pro, 1709, OS build 16299.125.

Did the copy trick shown above and now starts.

Has anyone any idea about what is causing this?

Can I trust the operation of the s/w with the Vivado-vg.exe start up?????

Thanks

Mark

[samcossais]

Version 1709 was released 2 months ago, not the 13th...

You might as well not trust the operation but you won't be able to start Vivado so it's not like you have a choice...

[sgrandpre]

I'm having the same issue in Vivado 2018.1.  

Where can I find the vivado-vg.exe file?