Yes indeed I went back to last year's version, and fortunately the problem disappeared. So I can continue working with my Goodhertz plugins on peojects

 

Download the installer from the official site, then unlock it with the latest keygen. Everything works including recalls.

 

No need to block anything

 

There is no upside to not doing it. I have not seen any outbound traffic from newest version yet, but I do not take that as I won't. Downloaded directly from them, unpatched and kg'd only, and there is no loss of saved state in project.

 

Yes, confirmed, it does NOT reload the settings. Did the witches choke on a fly again or what?

Anyway, you can save a preset with the current config and manually reload it after opening the project in the DAW. This workaround works perfectly, no complaints there.

Now let’s be real: having to save/load the last used preset every single time you tweak something or open the damn DAW is a massive pain in the ass.

Looks like from now on we’ll have to save presets with names like “Track_X_69_Final_ThisOneForReal” plus version numbers, and keep a backup folder of all our presets like we’re paranoid exes who still screenshot every chat, like just in case situations.

What a glorious life...

Thanks Witches, for sure, a fix is coming any decade now!

 

what about it calling home?

WINDOWS

Download the official installer but don't uninstall the R2R release. Install.
load up the DAW and you will see you have 2 of every plugin. The first one in Bitwig for me was official, and the second one was R2R for me. You can right click the plugin in the browser to see it's location. You shouldn't have to authorize because you have both installed. You should also see that the official plugs are in the VST3 folder individually while the R2R release is housed within "Goodhertz" folder within the VST3 folder. DELETE THAT FOLDER. Now go load up and you can now save the last state as intended. You're welcome.

DO NOT UNINSTALL THE R2R RELEASE YOU CANNOT AUTH WITHOUT IT

edit: I'll just add emphasis on not uninstalling the R2R as if caps is not enough lol. When you uninstall the r2R release you will lose functionality with the plugin and it will not load. At least that's what happened to me when I Revo'd either the official release or the r2r, so just leave em be and don't be OCD like me.

edit 2: I'm curious if someone would also try just unhousing the R2R release itself from the "Goodhertz" folder and let the plugins rest indiviually inside the VST3 folder and if that may solve the save state without having to install the official release. Someone try that and report back and I'll leave mine the way it is until something fails or all is gravy.

I would also make sure they are blocked since we're basically sneaking into the official release. Mine are blocked from the last release so I'm not having any issues as of currently and I'll be using them a lot today to test so if they timebomb I'll know.

 

Last edited by a moderator: Dec 2, 2025 at 3:07 PM

Nailed it! works like charm.

 

It seems to only do it with the vst3 plugins. What I did was installed the bundle in vst2 then I installed the old bundle that works in vst3 that easy I can get the new vulf compressor and clipper. Works like a charm.

 

Hey everyone, just for the record: be careful with the option to install the VST3 plugins from the original Goodhertz plugin pack downloaded from their site, 'cos after installing the official pack from the website, I can no longer load the challenge code: every time I try to load it, the keygen crashes instantly! (I'm running it with Microsoft Defender disabled and DEP protection also turned off... also, the keygen has been added to the exceptions list).

I have the Microsoft Visual C++ Redistributable (2015–2022) x64 fully updated, the latest version of R2R Network Block Runtime, and the domains blocked in the hosts file (0.0.0.0 goodhertz.com; 0.0.0.0 www.goodhertz.com; and 127.0.0.1 goodhertz.com).

I’ve already uninstalled using Revo Uninstaller and reinstalled about 10 times, with no success.

After failing to activate, I tried rolling back to previous installations using different keygens (from 3.13.2, 3.13.1, 3.11.0), but still no luck. I even tried removing the TEAM R2R Network Block Runtime and also deleting the Goodhertz entries from the Windows hosts file, both before and after the multiple reinstall/activation attempts, and still had no success at all.

So, heads up, because I believe my PC got infected with some kind of “gift” that came bundled with the original suite. I repeat: I had installed version 3.11.0 and updated to version 3.13.2 normally without any issues. The problems only started after installing the official installer... So, better safe than sorry.