Has anyone else been hit with the Windows 10 "Developers" update? I got it Saturday night and now Vivado (2016.1) can't start. It fails with an access violation (reading address 0x0000000000000000) in the JRE.Any suggestions? Xilinx suggested running vcredist_x64.exe, which had no effect.Any other ideas out there?Thanks,-Nick
Even the Vivado installer won't run. I was going to try installing 2017.1, but apparently that's not an option.
On Sunday, June 4, 2017 at 10:16:41 PM UTC-7, Nick Burkitt wrote:Has anyone else been hit with the Windows 10 "Developers" update? I got it Saturday night and now Vivado (2016.1) can't start. It fails with an access violation (reading address 0x0000000000000000) in the JRE.Any suggestions? Xilinx suggested running vcredist_x64.exe, which had no effect.Any other ideas out there?Thanks,-Nick
Sorry, make that "Creators" update.I've used the "Reset your computer" option to uninstall the update. The process seems to have broken a few things, but at least Vivado will start.Needless to say, I strongly recommend NOT installing the creators update.-Nick
On Sunday, June 4, 2017 at 10:29:05 PM UTC-7, Nick Burkitt wrote:Even the Vivado installer won't run. I was going to try installing 2017.1, but apparently that's not an option.
On Sunday, June 4, 2017 at 10:16:41 PM UTC-7, Nick Burkitt wrote:Has anyone else been hit with the Windows 10 "Developers" update? I got it Saturday night and now Vivado (2016.1) can't start. It fails with an access violation (reading address 0x0000000000000000) in the JRE.Any suggestions? Xilinx suggested running vcredist_x64.exe, which had no effect.Any other ideas out there?Thanks,-Nick