First off, huge thanks to the R2R team for this release and the continuous innovation. This new keygen method is clearly a big step forward.

I have a strictly technical question regarding the change in the keygen format. Historically, the standard .exe keygens worked flawlessly through compatibility layers like CrossOver or Wine. However, I noticed this new release uses a different extension/method instead of the traditional standalone executable.

Does this new format inherently restrict the keygen to a native Windows environment, or is there a known workaround to execute it through CrossOver/Wine as we used to do?

To be absolutely clear: I am not asking for a Mac release or port. I fully respect the team's focus and rules. My question is purely about the cross-platform emulation compatibility of this new keygen mechanism. Thanks again for your hard work!

 

"To be absolutely clear: I am not asking for a Mac release or port. I fully respect the team's focus and rules. My question is purely about the cross-platform emulation compatibility of this new keygen mechanism. Thanks again for your hard work!"

Hi pal, here you can touch the propossed topic from any perspective, no worries here about crossed platforms chats.

 

yes

no

 

If someone wants to "use an R2R keygen" to make a Mac release of something, which is exceedingly rare these days, the holdup will be getting an original Windows installer. Even that is a stretch.

 

Thank you! I know its a longshot but I had to ask, it is really an excelente approach from R2R but sadly it seems we eventually be fucked using mac/Linux with their keygens.

Not exactly needed a Mac release with their keygen, we can download oficial installers and just use the keygen with wine, at least it is what i was doing so far, still works flawlesly with their true keygens (not with their patched installers). Eventually if they dont change this system or at least give us a way to get our machine id outside a sandbox, we will be left behind with New releases/products.

 

They are likely not using the terms in title "patched and with keygen" anymore because their System release makes that just duplicated information. If you look at all their releases prior to System, you will see a large majority of their releases also needed to be patched. So the number of patched vs unpatched is probably something like 80% or 90% (which is just a guesstimate without real numbers quickly available). It's a large majority. Of the releases which have no patching done, the number gets even smaller when you can just download their keygen and use it with an official Mac version installer. The actual difference now will be the titles of their releases, because now you will not know without actually trying to do that.

 

The user Karnot posted this under TEAM R2R System v1.0.2-R2R on the sister site.

"Thanks to the R2R witches for your hard work!

For the few people trying to getting the keygens to run on Linux via wine, it doesn't seem to work at the moment and will throw "Signature Verification failed". Even if you have the root certificate installed and get the 'All OK' through WitchDiag.
It seems wine hasn't the necessary bcrypt functions implemented or translated to gnutls:


fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:key_asymmetric_verify flags 0x8 not supported
fixme:bcrypt:key_asymmetric_verify hash size 64 not yet supported


Time to play around in a Windows VM."



Follow up to the comment left under TEAM R2R System v1.1.0-R2R

"Fixed it. The problem is actually extremely trivial: a missing case statement for 64-byte keys. Adding this single line to the key_asymmetric_verify function in dlls/bcrypt/dlls/gnutls.c and rebuilding works perfectly (only tried on R2R System 1.10):

case 64: hash_alg = GNUTLS_DIG_SHA512; break;

N.B. I've only tried this with Wine 9.21 due to the yabridge mouse positon bug."




Also R2R have mentioned a fix for emulated windows environments in the latest TEAM R2R System v1.2.0-R2R

"v1.2.0
- New : Added new WitchUnIns to create batch uninstaller for R2R installers.
- New : WitchWand shows error when the WitchMagic is built for newer R2R
System.
- New : R2R Signature is updated to V2. V2 is (stronger than V1 and) more
compatible for emulated Windows environment. Upcoming Magic will be
signed by V2. Verification of V1 signature in R2R System will be
dropped in the future.
- Fixed : The text output from EZKG_Juce*() functions are not ZERO terminated.
- Fixed : Slightly improved performance of R2RSys_GetVersion().

------------------------------------------------------------------------------

Comments for this update :

* Uninstalling plugin bundle is now much easier than before!
* We din't thought we need to code version check, because we always write
enough information in Runtime.txt.
* Signature V1 uses ECDSA P256 + SHA512. There are no problems in the real
Windows machine at all. The problem is that P256 + SHA512 combination is not
that popular and it tend to have problems in emulated Windows environment.
That's the reason we switched to V2 (ECDSA P521 + SHA512). Please
note that we won't change the signature scheme anymore unless there is
vulnerability. If the Windows emulation is still not working as expected,
please ask the fix to the emulator developer, or contribute yourself."

 

Thanks for such a detailed answer. Of course I understood half of it but count I'll take the time to understand what you said and try to make it work! Much appreciated!

 

Hi everyone,

I'm struggling to get the new R2R WitchMagic (.r2rwm) files running on macOS (M2 Max) using CrossOver. I’ve followed the manual for TEAM R2R System v1.2.0 to the letter, but I’m still hitting a wall with "Signature Verification failed".

Here is exactly what I’ve done so far:

Spoiler

1. Environment: Created a clean Windows 10 64-bit bottle ("R2R Lab") in CrossOver.
   
   
2. System Installation: Successfully installed TEAM R2R System v1.2.0.
   
   
3. Certificate Import: I’ve tried importing the R2RCA.cer using the control inetcpl.cpl method (Content > Certificates > Trusted Root Certification Authorities).
   • The Issue: Even though the import wizard says "Successful," the certificate does NOT appear in the Trusted Root list when I check it manually afterward. It seems like CrossOver is silently failing to write it to the registry/store.
4. Diagnostic Results:
   • R2RCERTEST.exe: Returns "OK" and says the certificate is installed (strangely, it gives this "OK" even before I manually attempted the import).
     
     
   • WitchDiag v1.2.0: I ran the official diagnostic tool and it shows "Digital signature is verified by WinVerifyTrust()" for all components (WitchWand, WitchConfig, R2RSYS.dll, etc.). Everything is flagged as SUCCESS.
5. The Error: Despite WitchDiag claiming everything is verified, whenever I try to run a .r2rwm file (using WitchWand.exe with the correct arguments), I immediately get: "Signature Verification failed".

Observations: I’ve read about the bcrypt SHA512 (64-byte keys) issue in Wine's gnutls.c. Since I am on a Mac Studio (ARM), it feels like the V1 signature check is failing at the translation layer. However, I’m seeing this even with very recent releases that should theoretically be using the newer V2 signature.

My questions for the experts:

• Why does WitchDiag report "Verified" while the actual WitchMagic execution fails with a signature error?
  
  
• Is there a way to force the certificate into the Local Machine Root Store via Registry or Command Line in CrossOver so it actually sticks?
  
  
• Does the v1.2.0 system actually bypass the SHA512 bug on unpatched Wine builds, or are we still dependent on the gnutls.c patch for older V1 signed files?

Any help or technical insight would be greatly appreciated. I’m trying to avoid moving to a full VM (UTM/Parallels) if this can be solved within the CrossOver environment. (tahoe 26.4 and crossover 26 demoing)

Thanks in advance!

 

Last edited by a moderator: Mar 28, 2026 at 8:59 PM

I don't see why the fixation and multiple tries with Crossover and/or Wine. Just run the soft within VMware or Parallels in a virtual Windows installation. I know it takes a bit more effort and disk space but you will only do it once, from there and on your virtual Windows is saved on disk. That is, if you want to use the given witches software this bad hehe. It is likely though, more of the same will follow.
Cheers

 

You're absolutely right, man. I was trying to keep it as lean as possible by using bottles to save system resources, but it's clear that the security layers in macOS and the ARM architecture are making it a nightmare for the R2R certs.
I'm moving over to a VM setup (probably Tiny11 ARM) to get that native Windows environment and stop fighting with the 'Signature Verification' errors. It's definitely the way to go to get everything green on the first try.
I'll give it a shot and report back once I have the witches software running smoothly. Cheers for the heads-up!

 

Ive had great luck using parallels desktop for their VSL releases, but have not tried the new system yet. I would imagine it would be ok, as its essentially a windows machine. Bummer they are done with MAC. MAC had a good run recently, but seems to be slowing down again. I miss hciso the most. I know he has released some stuff recently, but there was a time there where there was a new hciso release almost every day lol.