Sidroe
I just went thru 5 excruciating days of the same symptoms with VB3!!! The culprit turned out to be a corrupt or interrupted Windows 10 update that was installed the 25th of July!!!
I would take a look at that. Simply go to settings and check your update history in Windows Update. You can uninstall that update and let Windows Update reinstall it. It straightened VB3 out for me.
Can't make any promises.
what's the KB number of the update, please?
and how did you figure it out, trial and error?
i wonder, is it the same update that broke the ni controller stuff?
/tia