1.0.12-2 fails to start up on Windows 10 - Failed to find library - jvm.dll

windows
#1

I just tried installing Axoloti on a new Windows 10 machine. After installing the latest runtime and msi from 1.0.12-2 I found I could not launch the application. It popped up three dialogue boxes immediately:

Failed to find library.

C:\Program Files (x86)\Axoloti\runtime\bin\client\jvm.dll

then

Failed to locate JNI_CreateJavaVM

then

Failed to launch JVM

Oddly the first file appeared to be there. I'm not very knowledgeable on Windows so perhaps I was missing something.

I've uninstalled that version and am using 1.0.11 which appears fine so far.

Choosing a laptop to run Axoloti Editor
#2

I have this exact same problem when trying to run 1.0.12-2 on Windows 7. I had thought initially it was a problem with Windows 7 and was considering upgrading to Windows 10 but now don't want to waste my money upgrading if I will still encounter the same issue.

I've googled the above errors and there doesn't appear to be a straightforward fix for a layman such as myself. Running 1.01.11 is fine for the short term getting to know the editor and the basics of the Axo but I am missing out on all the juicy 1.0.12 patches that are in the contributor libraries (of which there are many!).

Any ideas @thetechnobear or @johannes ? If not on a fix for Windows 7, at least some reassurance that I'll be able to get 1.0.12-2 to work on Windows 10.

#3

Sorry, me again. In case this is useful to others I am now running 1.0.12 after following the directions on this video:

Haven't tried 1.0.12-2, just happy that I have a version of 1.0.12 working! :smiley:

#4

That seems a little peculiar, that video is about installing DirectX so if it's fixing it then it could be just because of a side-effect or another action (like reboot) associated with installation.

Note in that video he also makes a comment about downloading it from any other website if you cannot find it on Microsoft site. Installing software particularly device drivers from random web sites including ones not associated with the product is extremely unwise. That does not include mirror/cdn sites where file is verified after download.

I'm not familiar with the wonderful world of dynamic linking/loading on Windows, perhaps someone more au fait with this can comment?

#5

I suspect that that might mean a JVM version mismatch - that video shows a workaround for stuck DirectX dlls that could not be updated due to file locking issues. What are the permissions on jvm.dll and the folder it is in? Did you stop Axoloti before you updated?

#6

I’d like to stress that I changed 2 variables to get the patcher to work - installing 1.0.12 rather than 1.0.12-2 and running this update.

I downloaded from Microsoft.

Axoloti wasn’t plugged in.

#7

I’m gonna have to try that. have had my Axoloti for 6 days now and haven’t even got it to make a noise yet. Was running lubuntu and just wiped disk and re installed win 10(now running 150x slower) and i am no closer to making any music... fingers crossed

#8

Hello, i had the same error installing the axoloti-software in windows 10.

For me it works, after deinstalling "axoloti-win-1.0.12-2.msi"

and reinstalling: "axoloti-win-1.0.12-2-java1.8.0-191.msi" from https://github.com/axoloti/axoloti/releases.

hope it will help other new people like me to axoloti... =)

Best greetings

#9

Hello -
Similar issue here. I cannot get the patcher to load / launch correctly. I've been using an older laptop until a few weeks ago, and now cannot install Axo on my new machine.

Windows 10
Tried current releases are well as older ones - no success.

1.0.12 (older rev)
User Library version mismatch, do you want to upgrade? This will stash any changes, and then reapply to new version. If not, then you will need to manually back up changes, and then sync libraries.

Click 'yes'

Dialog box:

Firmware CRC mismatch detected. Asks if I want to update firmware, tells me LEDs will blink (they do not)

unidentified header : 0x726F7841
AxoA
unidentified header : 0x726F7841
unidentified header : 0x72AxoT6F7841
AxoA
Firmware version: 2.0.0.0, crc=0xDAEFEECD, entrypoint=0x900E0208
Firmware CRC mismatch! Please flash the firmware first! Hardware firmware CRC = DAEFEECD <> Software CRC = E95BAC96
Firmware is newer than the software release,
firmware updatAxoTe will fail,
and connection will fail too.
You need to downAxoTgrade firmware via the rescue (DFU) method!
AxoTunidentified header : 0x796F7841
AxoTunidentified header : 0x796F7841
AxoA
Ping: WaitSync Timeout, disconnecting now
Disconnect request
unidentified header : 0x726F7841
AxoTunidentified header : 0x726F7841
AxoTunidentified header : 0x726F7841
AxoTunidentified header : 0x726F7841
AxoA
Link to firmware CRC E95BAC96

OR

connected
Can't obtain signature, upgrade firmware?
search path : C:\Users\aliss\Documents\axoloti\axoloti-factory\objects
Firmware version: 2.0.0.0, crc=0xDAEFEECD, entrypoint=0x900E0208
Firmware CRC mismatch! Please flash the firmware first! Hardware firmware CRC = DAEFEECD <> Software CRC = E95BAC96
search path : C:\Users\aliss\Documents\axoloti\objects
search path : C:\Users\aliss\Documents\axoloti\axoloti-contrib\objects
finished loading objects
Firmware is newer than the software release,
firmware updatAxoTe will fail,
and connection will fail too.
You need to downAxoTgrade firmware via the rescue (DFU) method!
AxoA
Ping: WaitSync Timeout, disconnecting now
Disconnect request
unidentified header : 0x726F7841
AxoTunidentified header : 0x726F7841
AxoTunidentified header : 0x726F7841
AxoTunidentified header : 0x726F7841
AxoA
Ping: WaitSync Timeout, disconnecting now
Link to firmware CRC E95BAC96
Start uploading firmware
Done uploading firmware
Start uploading patch
Done uploading patch
Start flashing...
flashing... (ready when the green LED is steady on)

But the LED never flashes, and the patcher window never provides further updates. It hangs there.

Any ideas? Suggestions?