This may or may not be after an initially successful launch.
- Make sure that Vasari2.exe is not located in Program Files, Programs Files (x86), or ProgramData
- Check if Revit.exe *32 or Vasari2.exe*32 are running in TaskManager. If they are, your initial start may just be taking a long time (some OS security measures make the initial creation of the Vasari system on your local drive take a long time). If multiple instances of either of these are showing in task manager, right click on them and “end process”, then try again.
- A component of Vasari, WSCommCntr3.exe, might not be shutting down and is blocking next start. The cure is simple: kill WSCommCntr3.exe in the task manager. Cause is possibly associated with a crash that does not allow WSCommCntr3.exe to shut down and so it blocks Vasari starting up after a crash.
- Run a Windows Update, Vasari relies on some windows framework components that may be out of date on your machine.
- Antivirus is blocking the application: user needs to temporarily disable the antivirus. If this works, they need to change the Antivirus settings to make an exception for Vasari2.exe.
- Need Admin rights. Some configurations of machines seem to require that user have stronger Admin rights. Often an initial start of Vasari by right clicking on the app and “run as Administrator” will allow subsequent runs to be made by non-Administrative users.