(Solved) Launcher: Failed to validate signing of launch file. The signed version does not match the downloaded version.

[Tathar 48]

On starting up the game launcher, I get the error "Failed to validate signing of launch file. The signed version does not match the downloaded version."  How do I fix this?

Edited February 1, 2015 by Tathar

[Brash_Endeavors 4,735]

I have not had this error in a long time, not since changimg my shortcut to

 

C:\Windows\System32\javaws.exe http://www.wurmonline.com/client/wurmclient.jnlp

 

here are some old threads on how to solve it:

(each link has a fix that worked for someone, but they are not all the same fix!)

 

http://forum.wurmonline.com/index.php?/topic/63172-java-7-update-5-unsigned-certificate-solution/

http://forum.wurmonline.com/index.php?/topic/43997-java-problem-failed-to-validate-certificate-solved/

http://forum.wurmonline.com/index.php?/topic/83084-failed-to-validate-certificate/

http://forum.wurmonline.com/index.php?/topic/66493-click-play-open-file-and-nothingfailed-to-validate-certificatefixed/

http://forum.wurmonline.com/index.php?/topic/13040-certificate-error/

 

On one of those though, they reversed the location of 32 & 64 bit Javaws.exe. Even though it seems counterintuitive, 64-bit is in System32, while 32-bit is in SystemWoW64. I can dig up the reason why if you are curious   or see if this helps. It seems to suggest that System32 is the best default to use because it will automatically redirect if you actually need the 32-bit version instead. Though I might be reading that part wrong. 

 

Hopefully one of these solves it for you 

Edited February 1, 2015 by Brash_Endeavors

[Tathar 48]

Thank you!  The first solution (the one Enki quoted Revnik on) worked perfectly.  

 

http://forum.wurmonline.com/index.php?/topic/63172-java-7-update-5-unsigned-certificate-solution/

 

EDIT: Also worked for my laptop, which I just discovered had the same issue.  Yay, double fixes!

 

EDIT 2:  I'm also aware of the System32/SysWOW64 thing.  The Wurm installation's shortcut defaults to SysWOW64 on 64-bit systems when it shouldn't.  SysWOW64 is really short for (something like) "System Windows on Windows 64-bit" which essentially means, more or less, that you're accessing the 32-bit architecture Windows on top of your 64-bit Windows.  But most people just see the 32 vs. 64 and think the opposite.  

Edited February 1, 2015 by Tathar