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: 702 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 #2082 is a reply to message #2079] |
Fri, 05 January 2024 17:31 |
Jay
Messages: 7 Registered: December 2023
|
Junior Member |
|
|
Thank you, Thomas. Ran the debug version of DW600 from command line (file properties checked and not blocked)--another blank command window popped up for a couple of second then closed by itself, and no message. Below is Windows Logs info, probably useless...I double checked Windows Security center & my company's security software SentinelOne Agent, and neither registered anything in the threat history.
The only two applications that I installed on this brand new PC are Pymole & ChemOffice, both weeks before DW. Obviously I tried to open DW after restart without opening any other applications... Very weird.
Fault bucket 2140585459117814558, type 5
Event Name: BEX64
Response: Not available
Cab Id: 1494130237812378202
Problem signature:
P1: DataWarrior_d.exe
P2: 0.0.0.0
P3: 63bef016
P4: StackHash_285e
P5: 0.0.0.0
P6: 00000000
P7: PCH_40_FROM_ntdll+0x000000000009FEC4
P8: c0000005
P9: 0000000000000008
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.1262f76d-0 03f-4a31-b6b2-23e2232a4cb7.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.29a27d47-6 47f-45c7-8e24-42e2fb9b0fac.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.31c9cb7c-0 a0a-43dc-a991-1fed4ab9cb99.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.d954634f-3 f6c-4945-8954-5c32199923f7.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.fa0ad256-7 5ef-4487-8f46-9a70b241842a.tmp.xml
\\?\C:\Users\\AppData\Local\Temp\WER.bf955ba7-70b 7-4b7f-9446-da81e83fcd7a.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4181eb2b-5 779-4c7b-a9a4-2837a3dadb97.tmp.hdmp
\\?\C:\Users\\AppData\Local\Temp\WER.500a4b17-57e b-4a06-bdb1-06faa3052670.tmp.WERDataCollectionStatus.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCr ash_DataWarrior_d.ex_757a10957d385b25c6c5b26c66fa54e0783d5e2 4_a53b6bcc_cab_33d0776a-61c2-4f50-88e7-c0015f9b6ae0
Analysis symbol:
Rechecking for solution: 0
Report Id: 07e1d64f-7741-42a4-b48c-f30024f1fcad
Report Status: 268435464
Hashed bucket: 45fc86d6e2720b5e2db4e3223e15731e
Cab Guid: f787a5be-291c-464f-a4bc-3788f8fa0a5a
[Updated on: Fri, 05 January 2024 17:33] Report message to a moderator
|
|
|
|
Re: Windows 10 Startup Issues [message #2092 is a reply to message #2086] |
Mon, 08 January 2024 21:50 |
Jay
Messages: 7 Registered: December 2023
|
Junior Member |
|
|
Yes sir "SentinelOne" is indeed the culprit! White-listing solved this issue.
What makes this issue hard to spot is that the antivirus software never registered it as a threat even from the IT end. They have to manually instruct it not to check the DW.exe file.
Thanks again for your time and help. Really appreciate it!
|
|
|