autopsy icon indicating copy to clipboard operation
autopsy copied to clipboard

Hangs at startup on Windows + work around

Open quintesse opened this issue 1 year ago • 13 comments

Not really sure what's going on but after installing and running the app there's this dialog that pops up that's completely white (no borders, no icons, no titlebar) and that's inactive (tried clicking everywhere).

Waited for a long time but it wouldn't continue so the only thing I could do was to kill the process.

I then tried running it from a console to see if there were any errors, but none showed, just a bunch of very normal looking log messages.

Finally, seeing there was also a bash script in the same folder as the autopsy64.exe I fired up my Git Bash and started the app using the script and everything worked fine.

quintesse avatar Sep 25 '24 15:09 quintesse

Same problem. Application dowsnt launch and stays suspended in task manager. Screenshot_8 Dead white screen.

Geozstevenzz avatar Dec 14 '24 08:12 Geozstevenzz

How are you making the application? Are you compiling from sources or downloading the release? Do you see this behavior on the math machine? Do you see this behavior with the official distribution on your machine? How about with the official distribution on another machine?

simsong avatar Dec 14 '24 11:12 simsong

Can you move the white screen around to see if there is a pop up behind it that needs attention.

markmckinnon avatar Dec 15 '24 23:12 markmckinnon

@markmckinnon no, there's nothing behind it.

Edit: also, you can't right-click and select close on the taskbar icon either, it will just ignore it. You have to manually kill it using the task manager.

quintesse avatar Dec 16 '24 20:12 quintesse

Can you post the messages.log file from the following directory C:\Users<User Name>\AppData\Roaming\autopsy\var\log

On Mon, Dec 16, 2024 at 3:31 PM Tako Schotanus @.***> wrote:

@markmckinnon https://github.com/markmckinnon no, there's nothing behind it

— Reply to this email directly, view it on GitHub https://github.com/sleuthkit/autopsy/issues/7918#issuecomment-2546670004, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACEVPDDQZYECTPSVUPTIDPL2F42CJAVCNFSM6AAAAABO23SCT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBWGY3TAMBQGQ . You are receiving this because you were mentioned.Message ID: @.***>

markmckinnon avatar Dec 16 '24 21:12 markmckinnon

Sure, here you are (lots of exceptions!)

messages.log

quintesse avatar Dec 16 '24 22:12 quintesse

Here is mine as well messages.log

There is no pending dialogue box behind the white screen and I am using the release version. I am not building

Geozstevenzz avatar Dec 17 '24 06:12 Geozstevenzz

@Geozstevenzz @quintesse Do either one of you have JDK or JRE installed as a standalone app? If so what versions?

markmckinnon avatar Dec 17 '24 14:12 markmckinnon

Version 17.0.10 Uploading Screenshot_10.png…

Geozstevenzz avatar Dec 17 '24 14:12 Geozstevenzz

@Geozstevenzz is that installed to fullfill a requirement for some other software on your computer. if not then what happens if you uninstall it. If it is a requirement for some other software then do not uninstall it. Autopsy comes packaged with a JRE so it does not require you to install java to run it.

markmckinnon avatar Dec 17 '24 14:12 markmckinnon

@markmckinnon yeah, I'm pretty sure our local JDKs are getting preference over the included JDK. Because my default JDK is 17.0.11, if I switch it to 11.0.23 Autopsy starts correctly (which I'm guessing works because in 11 JavaFX was still distributed with the JDK by default while from 17 onwards that is no longer the case)

quintesse avatar Dec 17 '24 17:12 quintesse

@quintesse I would agree that is what is happening in your case. Is your local JDKs also included in your PATH? If you could remove that temporarily then you can see if Autopsy would start then.

markmckinnon avatar Dec 17 '24 20:12 markmckinnon

@markmckinnon yes, in that case it starts just fine.

quintesse avatar Dec 17 '24 21:12 quintesse