visit icon indicating copy to clipboard operation
visit copied to clipboard

Published 20 hours ago • verified publisher icon visit-dav

the lastest VisIt in Windows stystem can't run.

Open Ron-Wang opened this issue 2 years ago • 5 comments

I used VisIt 3.2.2 in my Windows device and it can't run now. I wonder if some update of Windows caused it. Thanks for your applying.

Ron-Wang avatar May 12 '22 08:05 Ron-Wang

Can you please be more specific? Which version of Windows are you running? What exactly happens when you try to start VisIt? Do any of VisIt's components start (gui, viewer)? Are you using the Start-menu icon to launch or running from a command prompt? Do any error messages pop up? Can you try running the 'VisIt with debug logging' icon from the Start Menu and see if any log files are generated. If they are generated they will be in your 'home' directory as described in the File Locations of our docs.

You could also try uninstalling and then re-installing VisIt.

biagas avatar May 12 '22 15:05 biagas

Thanks a lot! My version is Windows 10 pro (21H2). When I open "VisIt 3.2.2", it loads about 80% and close. None of VisIt's components starts (gui, viewer). I try running the 'VisIt with debug logging' icon from the Start Menu, but it has the same problem and I can't find any log files. I try uninstalling and re-installing VisIt in different versions, but it is useless.

Ron-Wang avatar May 13 '22 06:05 Ron-Wang

Have you tried looking at the log files for Windows firewall (or any anti-virus programs you have) to see if VisIt's components have been blocked or quarantined? gui.exe, viewer.exe, mdsever.exe,

I don't have access at the moment to that particular version of Windows for testing.

A long while ago, we used to have problems with VisIt hanging at startup. We were able to work around it by installing VisIt with fewer database plugins. This can be accomplished from the installer gui, by expanding the 'Database Plugins' in the 'Choose components' dialog: databasePlugins

You can uncheck a few, or uncheck all, then re-check only those readers that support your needs. Reducing the number of database plugin speeds startup, but still may not resolve your issue.

Would you be willing to try a console version of 3.2.2? All VisIt components will launch as console apps instead of windows-apps and it may display error messages to the command window that help diagnose why VisIt is crashing at startup.

biagas avatar May 16 '22 19:05 biagas

Unfortunately it seems I am unable to update my personal Windows 10 pro 21H1 to 21H2, so I am unable to test running VisIt on the same OS version as you are trying. It worked fine on 21H1.

biagas avatar May 23 '22 18:05 biagas

@Ron-Wang, I finally gained access to a Windows 11 system with OS Build version 21H2, and could not duplicate your issue. It was running OS build 22000.613, no issues. I ran windows updated to 22000.729, still no issues running VisIt. Then installed another windows update that moved the OS build to 22000.778, still can not duplicate.

Are you still experiencing problems?

biagas avatar Jul 06 '22 23:07 biagas