[Solved] Fallrim Re-Saver and Java 1.8.0_461?

[anjenthedog]

Java 20 is enough of a confirmation for my purposes.

 

thanks

 

Will report back a bit later to close this up but it sounds like it's a done deal

[anjenthedog]

2 minutes ago, traison said:

Edit: Well done, you solved this mystery. You can now go teach the rookies over at the Nexus how to do things properly. 👍

Lol Me? Nah, it was you., thank you.

[Grey Cloud]

I had this problem a few months back.

Tried to upgrade java because of Re-saver error but for whatever reason no matter which 64-bit version I tried to download it always grabbed the 32-bit version and always said it had installed correctly but Re-saver still threw up the same error message and refused to run.

I eventually got it working but I have no idea what I did that was different to the other umpteen attempts. 

According to the file timestamps this was 10th February.

 

This is what I have:

 

java version "1.8.0_441"
Java(TM) SE Runtime Environment (build 1.8.0_441-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.441-b07, mixed mode)

 

Re-saver 6.0.643

  

Edited July 20, 2025 by Grey Cloud

[traison]

Hit them with a "Duh, the JFXPanel class version is 54. You need Java 10 or newer."

 

Like a wolf among sheep.

[traison]

3 minutes ago, Grey Cloud said:

Tried to upgrade java because of Re-saver error but for whatever reason no matter which 64-bit version I tried to download it always grabbed the 32-bit version and always said it had installed correctly but Re-saver still threw up the same error message and refused to run.

 

One great and horrible thing with Java is that every version installs next to the previous version - you can have 10 versions installed at the same time and every program you run will pick one most suitable. Great when you have applications that abuse a bug only present in a specific version, absolutely horrible when there's a security hole.

 

What I'd do in your case is just uninstall everything Java related, then install the newest version.

 

Also I think it would be important to know how you determined that it installed the 32-bit version (is there a 32-bit version?).

 

5 minutes ago, Grey Cloud said:

I eventually got it working but I have no idea what I did...  This is what I have: java version "1.8.0_441" ...

 

Based on what we've seen here, what you did was switch to an older version of ReSaver. Either that or you do indeed have both 32 and 64 bit versions installed, and when you checked the version just then its from a bitness that ReSaver isn't using.

[Vortec]

 I had this problem as well when I updated Java, all I did was I found an previous Java update and overwrote the new Java update. Re-saver works fine for me now, I'm not sure what all Java is good for anymore due to security problems it causes.

[traison]

4 minutes ago, Vortec said:

I'm not sure what all Java is good for anymore due to security problems it causes.

 

It's used in everything from SIM cards to cars. The reason why I said you shouldn't have it in your browser was the same reason why you shouldn't have anything else in your browser: if you're not specifically using it for something, it's a really bad idea to increase the attack surface. Java is probably no less secure than .net.

 

An example: When the large browser vendors like Chrome and Firefox announced that they will be adding hardware acceleration to HTML5, I knew this would be abused - I knew how I would abuse it. So the first thing I did when the Firefox patch rolled around that added WebGL was go into the hidden configs and disable it. Sure enough a few months later we had reports of websites popping graphics cards by overheating them. They did exactly what I would have done, had I wanted to abuse it: Create an accelerated app with very little to render, and no vsync. When fps hits the 10,000-15,000 mark your temps will skyrocket. Sure, modern hardware turns itself off to protect itself from heat damage, but I imagine a GPU can only take such rapid increases to 100°C so many times...

[Grey Cloud]

1 hour ago, traison said:

Based on what we've seen here, what you did was switch to an older version of ReSaver. Either that or you do indeed have both 32 and 64 bit versions installed, and when you checked the version just then its from a bitness that ReSaver isn't using.

As I said this was back in February so I can't really be sure what I did.  I got java updated and Re-saver working and it still works (checked it earlier). 

[PippinTom]

5 hours ago, anjenthedog said:

Anyone else using the latest JAVA and also cannot open Re-Saver.exe?

 

Add (create if does not exist) registry key

Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs\resaver]
"settings.javafx"="false"

 

Edited July 21, 2025 by PippinTom

[anjenthedog]

On 7/20/2025 at 6:01 PM, traison said:

Hit them with a "Duh, the JFXPanel class version is 54. You need Java 10 or newer."

 

Like a wolf among sheep.

 

 

Said I'd get back on this...so here I am. (took me a bit longer than I wanted, since I got caught up in other crap...)

 

Uninstalled Java 8 JDK... and Java 8 461

 

Installed Java 24 JDK (couldn't find any JRE... but honestly, I didn't' look very hard either)

 

Fallrim ReSaver works.

 

Thanks again for your help

[traison]

Latest JRE seems to be 10.0.2. That would be enough to run ReSaver.

 

Edit: Personally I'm gonna stick with 24, just because I never know when I'm gonna need the debugging tools again.

Edited July 22, 2025 by traison

[anjenthedog]

On 7/20/2025 at 6:00 PM, Grey Cloud said:

I had this problem a few months back.

Tried to upgrade java because of Re-saver error but for whatever reason no matter which 64-bit version I tried to download it always grabbed the 32-bit version and always said it had installed correctly but Re-saver still threw up the same error message and refused to run.

I eventually got it working but I have no idea what I did that was different to the other umpteen attempts. 

According to the file timestamps this was 10th February.

 

This is what I have:

 

java version "1.8.0_441"
Java(TM) SE Runtime Environment (build 1.8.0_441-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.441-b07, mixed mode)

 

Re-saver 6.0.643

  

That'll work. I believe the next update (451) is where the issue started. And several posts in the Fallrim bugs section indicated that rolling back to 441 is one solution

 

Also, got a reply over at nexus this morning that suggested a mod which I guess uses OPEN JDK code chunk or something, with the clever name ReSavor

 

I didn't try it, since I was already committed to the "replace Java 8 with Java 24" track by then, but for anyone who wants a simple, ~immediate mod solution without jumping through Java hoops, that might be an avenue for you.

 

----

 

In any case, to get the 64-bit versions of Java 8, go to

https://www.oracle.com/java/technologies/javase/javase8-archive-downloads.html

and then scroll down to the heading "Java SE Runtime Environment 8u202", where you'll find the 64 bit versins at the botom of its chart

 

And for Java 24 > https://www.oracle.com/java/technologies/downloads/#jdk21-windows (although for that all I know is how to get the JDk, which includes the java code, but isn't the JRE so may be a little more sluggish) < note: Re-Saver pops open faster under Java 24 JDK than it did under Java 8 JRE before I updated it to 461 and caused this chain of  events)

[anjenthedog]

On 7/20/2025 at 6:27 PM, Vortec said:

 I had this problem as well when I updated Java, all I did was I found an previous Java update and overwrote the new Java update. Re-saver works fine for me now, I'm not sure what all Java is good for anymore due to security problems it causes.

Yep. That works...

 

And tbh, that was my initial fallback plan (although unspoken), but for me, it would have been all the way back to 371 (the last installer I'd downloaded prior to 461), so I preferred solving it by either using 461 and some sort of patch or config fix, or via some other "forward facing" plan (like the one that @traison suggested (Java 24), if for no other reason than (ostensiblly improved) security moving forward rather than falling back...

[anjenthedog]

On 7/20/2025 at 6:07 PM, traison said:

Also I think it would be important to know how you determined that it installed the 32-bit version (is there a 32-bit version?).

Afaik, once you're on the default 32-bit path, Java keeps you on it for updates. So if you manually installed JAVA as a 32-bit app, or if the updater mistakenly switches you to the lower bit version (I've had that one happen before, both on my present 64-bit machine - dropped me to the 32-bit version, and on my old 32-bit machine - dropped me to the 16-bit version, it will continue along the lower-bit path for its auto updater

Edited July 22, 2025 by anjenthedog

[nobody12357841]

Hi all,

     I was having issues just getting resaver to work but this trick fixed it for me.

open up Regedit. Go to the highlighted location in the Image below

 

Computer\HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs\resaver

 

 If you do not see the other highlighted  text right click under (Default) select "New>Key".

Type out --> settings.javafx

press enter. Then right click the new entry and select "Modify..."

Type out --> false

press enter. Close regedit and your good to go.

 

Fingers crossed when you open up Resaver it will fire up with out issue

 

[anjenthedog]

On 7/24/2025 at 9:21 AM, nobody12357841 said:

Hi all,

     I was having issues just getting resaver to work but this trick fixed it for me.

open up Regedit. Go to the highlighted location in the Image below

 

Computer\HKEY_CURRENT_USER\SOFTWARE\JavaSoft\Prefs\resaver

 

 If you do not see the other highlighted  text right click under (Default) select "New>Key".

Type out --> settings.javafx

press enter. Then right click the new entry and select "Modify..."

Type out --> false

press enter. Close regedit and your good to go.

 

Fingers crossed when you open up Resaver it will fire up with out issue

 

When java changes enough from one's present installation version, it's really not wise to keep forcing it to stay that way, since many of the incremental changes in utilities like JAVA are expressly to secure its code infrastructure from malicious intrusions.

 

Even if I'd chosen the 4-click mod solution that I briefly described (and linked) above in another post, it would have been a temporary fix only.

Edited July 25, 2025 by anjenthedog

[PippinTom]

Mentioned change in registry does not affect JAVA installation... that should be obvious (?) by the node/path itself. It just changes resaver's (pre)configuration, instructing it to not use JAVA feature that in the resaver's code is no longer compatible with JAVA. And the same result one would get when using resaver's GUI in Options>>Settings>>General>>"use javaFX native FileChooser" (which is shitty enough to never use it anyway). The only problem is that when first run (and now I'm guessing), resaver probably performs checks of each of its features availability, and there is no failsafe/fallback in the code in case of javaFX fileChooser which is completely optional feature, as such has been added to the resaver in one of its updates - and it's not essential to run it.

 

However if you wish to elaborate a bit more about security issues (which are irrelevant in case of configuration choice which is user's anyway) comparing to other "solutions" proposed in that thread which were to downgrade whole JAVA environment just to run resaver - please continue. It's always good to learn something wise.