Windows 10 Startup Issues [message #1591] |
Mon, 11 April 2022 22:23  |
KymeraIT
Messages: 2 Registered: April 2022
|
Junior Member |
|
|
All,
After installing DataWarrior 5.5, the application simply does not run on a Windows 10 system. Some investigation does show that it is erroring out, but the only indication with no detail is in the Windows event logs (the generic BEX64 error).
We have attempted to run with elevated permissions with the same result. We have also reinstalled the application with no luck. We can also confirm that antivirus software is not reporting any issues relating to DataWarrior.
Any further suggestions/advice would be appreciated.
|
|
|
Re: Windows 10 Startup Issues [message #1594 is a reply to message #1591] |
Thu, 14 April 2022 11:00   |
thomas
Messages: 514 Registered: June 2014
|
Senior Member |
|
|
Do you see any messages, when starting DataWarrior.exe from the command line?
Did you check the MD5 sum of the msi?
Did you make sure that none of the exe, dll, or jar files in the DataWarrior directory are blocked in the file properties dialog?
You may download a debug version 'DataWarrior_d.exe' from openmolecules.org/datawarrior/dw550_d.zip. Then unpack and copy these files into the DataWarrior installation directory. Make sure, none of the new files is blocked. Then start DataWarrior_d.exe from the command line. Any messages?
Thomas
[Updated on: Mon, 06 June 2022 09:45] Report message to a moderator
|
|
|
|
|
|
|
|
|
Re: Windows 10 Startup Issues [message #1634 is a reply to message #1633] |
Mon, 13 June 2022 16:18  |
chemtv
Messages: 20 Registered: February 2015 Location: Indianapolis
|
Junior Member |
|
|
Hmm, Please ignore my message above...
I just saw a thread in "if my PC do not install office, how can we install datawarrior and initiate it?" referencing the need to install 'vcruntime140.dll' Once I did that datawarrior runs fine.
Thanks for a fine program, it's a great tool! I use it predominately on Macs and Linux, but occasionally need to run it on Windows... maybe need to push the 'dll' message to the top.
regards,
Greg
|
|
|