SourceGear Support

Just started happening last week. Possibly after an update of VS or SGV.
you have to kill VS via task manager

VS 2017 V15.8.4
SGV V10.0.0 (30736)

Any suggestions would be appreciated.

I doubt this has anything to do with Vault but wondered if you'd had this happen before and might know the cause. After a Windows 10 update over the weekend (probably a coincidence), one of our developers seems to be picking up a version 7 (3 years old) of a source file not the latest version 12. We...

Thanks

Can you recommend how to move my client to a new Pc.
Everything I have checked out needs to be checked out on the new Pc instead.
At the moment is just says it's all checked out on the old one.
Thanks

The re-binding seems to have fixed it.
I'm just slowly working my way through it now.
Thanks for all the help
Chris

Yes the project is open wih the grayed out options. There were no warnings.
I can't see any Change Vault Bindings option. Would that be in VS?
Plug-in Selection : Current source control plugin is SourceGear Vault Professional Visual Studio Extension

Windows 10, Upgraded vault to 10.0.0 and VS2015 to VS2017 Vault seems to be running Ok but not through VS12017 VS2017 'About' shows Microsoft Vaisual Studio Professional 2017 Version 15.4.4 SourceGear Vault Professional Visual Studio Extension 10.0.1.30793 SourceGear Vault Professional Work Item Ext...