Anyone had this with stuff from the sister site? I have some activating and working fine and some always have the popup, such as Battery 4, Komplete Kontrol etc, despite activating using the R2R tool.

Anyone know how to get around this?

 

Cheers for this. I'll try to give it a go now!

The latest NI KG I have from R2R is 3.1.3 though?!

I also already have Native Access installed, but not logged in with my NI user account, but seems to make no difference as to whether the popup pops up or not.

 

Ni Keygen 3.4.0 is in
Native Instruments Super 8 R2 v2.0.0 Incl Patched and Keygen-R2R

 

Thanks for the pointers. This fixed it and all working now! Huge kudos for the help!

 

i also see that they changed the registration scheme. and product upid.
it need a xml file rectification in service center to work from the R2R Keygen.(i updated my fix)

<?xml version="1.0" encoding="UTF-8"?>
<ProductHints>
<Product version="4">
<UPID>c6b8ce64-9c20-49bb-96a7-4a13e3b2edfd</UPID>
<Name>Battery 4</Name>
<InternalName>Battery 4 Application</InternalName>
<Type>App</Type>
<ProductFamily>
<Name>Battery</Name>
<Version>4</Version>
</ProductFamily>
<RegKey>Battery 4</RegKey>
<SNPID>249</SNPID>
<AuthSystem maxVersion="4.1.6">RAS2</AuthSystem>
<AuthSystem minVersion="4.2.0">RAS2</AuthSystem>
<BinName>Battery 4</BinName>
<PluginID>0x4e426134</PluginID>
<HostMode>Engine</HostMode>
<Company>Native Instruments GmbH</Company>
<ShopLink>batterypricing</ShopLink>
<Icon>battery4</Icon>
</Product>
</ProductHints>

this use the old UPID for battery 4

there is another UPID for Battery 4, maybe used for the older version, or Battery Now.
dc2b870a-7dd5-4e47-9a43-01d168f26c82

it will generate a circus management for licenses between old and new version.
the VR license using 3671d444-6778-42f1-a616-e8ad35c0d602 upid/jwt
become the Battery Now Library content

i had to update my online version to prevent the demo joke.

 

Last edited: Mar 31, 2022

Help needed. After (disk imaging/cloning is a must... note to self) "clean install" reinstalling windows and making/taking a time to force them more-or-less nag-free stable, after installing few NI products (Maschine, Reaktor, Massive...) I noticed that none of R2R releases give love. All is in demo-buy-activate, or fuck of state of affairs.

Without "ras3" folder/keys generated by kgn/s, nag screen suggests "Thank you for using NI...!" With "ras3" folder/keys generated by kgn/s, nag-screen kindly suggests "Your activation is invalid." NativeAcess.xml in Service Center folder is from GRig 6.3.0. Installed od not (version 1 and/or 2), native access app doesn't change anything. Only one working version of anything NI, is Reaktor 6.4.3 (Bob Dule Repack 14/09/2021) which doesn't need license or keygen. Why, oh why, I deleted all "VR-CE" ("Collectors Edition") versions.

Let say "just for fun," just for fun installation of "Maschine" on another non-audio machine, populating "ras3" folder by keygen, copying NativeAcess.xml, gives.... lo and behold, it fucking works. Bedazzled. Before reinstalling same version of windows (W10E LTSC), on same machine, no problem whatsoever with demo-buy-activate, or fuck of state. While lamenting what could be the possible culprit, I stumbled on "uret_cache" file in Roaming/NI/NativeAcess folder, which reports machine specifications, and URET machine id and distinct_id. Keygen is generating keys on that machine id and/or distinct_id, I suppose? Any suggestions/recommendations will be (greatly) welcomed and much appreciated.

 

I have the same problem after resetting windows 11 recently on my PC.
all r2R keygens generate invalid .jwt files. As a result, all plugins are in demo mode with the message "Your activation is invalid".
I also have a laptop and the R2R keygens work fine, like the latest version of Kontakt 7.4.0 or Guitar Rig 6.4.0, but I can't get a valid .jwt on my PC!
I also have legit plugins that are correctly activated on my PC. Uninstalling native access hasn't changed anything for others.
I despair...

 

On one machine R2R keygen will generate keys and activation of everything will be successful, but on another machine, R2R keygen will generate keys and activation of anything, for some reason, will not be successful. Installing, reinstalling, cleaning folders, cleaning registry... installing, reinstalling, cleaning folders, cleaning registry... will generate only frustration. If that another machine is ment only for audio/video, and first one for regular, daily tasks, that's a bummer. Hunting and installing VR-CE releases "solved mystery."