How to authorize NI B4 II for 64 bit DAW?

[Harry_HH]

I have always liked the old NI B4 sound, although the implementation is old and only 32 bit.
I have both the B4 and the B4II upgrade.
jBridge works well, and both the B4 and B4II appear in my Live 9 64 bit.
The installation of the B4 includes the product authorization, and it works great in the Live 9,
but when I try to auhtorize the upgrade (the B4II), the Native Access won´t recognize the B4II plugin.

The B4II runs there in the demo mode, and the plugis ask the activation: I even tried the activation via the old NI Service Center, which says that the pugin IS ALREADY activated, but is still runs only in the demo mode.

The NI support was very laconic: they have finished supporting the B4, no help from there.

Has anybody any idea how to get the good old B4II upgrade authorized for the 64 bit Live /Win 10?

[teacue]

Probably not a real help but at least I can report that last year I could install and activate B4 II through NI Service Center and I did not encounter any particular problem.
B4 II is running on my system through jBridge 1.75 (Windows 10 - 64 bit and Cubase 9.5 - 64 bit)
But I did not installed B4 I, only B4 II

[Harry_HH]

Probably not a real help but at least I can report that last year I could install and activate B4 II through NI Service Center and I did not encounter any particular problem.
B4 II is running on my system through jBridge 1.75 (Windows 10 - 64 bit and Cubase 9.5 - 64 bit)

OK. I have the same setup, except Live 9 in stead of the Cubase.
In fact I have tested this both in my laptop and in desktop, which include the same DAW setup.
The result is the same, NI authorizer (nor SC or NA) can´t recognize the B4II.

BTW, did you install the B4II standalone as well, or only the plugin?
Sometimes the standalone works better in upgrades and auhtrizations - just a though, because I have only the plugin installed.

[teacue]

BTW, did you install the B4II standalone as well, or only the plugin?
Sometimes the standalone works better in upgrades and auhtrizations - just a though, because I have only the plugin installed.

I installed the standalone version.
And now that you mention it, I vaguely remember that I somewhere read something like installing and activating the stand alone version works better, but I am not 100% sure.

[Ah_Dziz]

It hasn't installed properly for me since windows 7 64 bit.

It will still authorize though service center though. The trouble is when it tries to launch. It gives an error about "tonewheel files" which I believe are the samples that it's based off of.

[jancivil]

AFAIK all NI plugins are supposed to be run in standalone first.
I wish I could remember what made the difference but I ran into exactly this with Kore 2, NA never saw it and SC threw an error. But one day it activated. Then I cleaned some cache and killed that and I just deleted it, it was a PITA to install and worse to activate.

[Harry_HH]

Thank you for commenting.

I decided this time not to re-install the B4II and try the standalone authorization.
I´m happy for the B4 (basic), it sounds as good as the B4II, I think. The main additions in the ver II are, I think, distortion effect, some tweaking in the leslie and more presets.

BTW, for some reason this 15 year old NI B3 sounds better than most I´ve heard, I own several emulations, but there are something sweet in the NI B4 sound...

[JonSolo]

For whatever weird reason I had to delete my old jBridge files before installing update. Then rerun jBridge and it authorized.

[Harry_HH]

For whatever weird reason I had to delete my old jBridge files before installing update. Then rerun jBridge and it authorized.

You mean by the "old jBridge files", all the files, including the B4 vst .dll-file?
Does this mean, that you can´t have both B4 and B4II installed at the same time?

[amhosib]

I use B4_2 as a standalone using Windows 7 Pro 64 bit and initially could not get B4 to function,it was apparently activated but still requesting activation on start-up.
My solution was to uninstall B4, and delete both the 32bit and 64bit Windows registry details of B4.
Do a fresh install from my original CD but don't allow it to start the in-built service centre.
Down load a legacy service centre and say NO to the automatic later update, this will then allow entering of the activation sequence.
You then have to enter the registry and delete the following three files within the 64bit registry:
KEY,SNO, and SYSTEMid.
This allows B4 to run as a standalone in my 64bit Windows 7, and I imagine the same applies for
Win 10.
You can then use jBridge etc, for its use as a VST within a 64bit environment.
32bit registry found at:
HKEY_LOCAL_MACHINE,SOFTWARE,WOW6432NODE,NI,B4
delete KEY,SNO AND SYSTEMID prior to re-installation.
64bit registry found at:
HKEY_LOCAL_MACHINE,SOFTWARE,NI,B4
delete KEY,SNO and SYSTEMID prior to and after re-installing B4

Hope this is of use.
ps in the pathway, the comas should be backslash (keyboard issue)

[Harry_HH]

Hi, than you for refreshing the thread. I have win 10 64 bit DAW, tried about dozen different installation variations, maybe not your suggestion.
I have to admit being given up, one reason is, that I have purchased the UVI organ library. And the NI Komplete 11 Ultimate, which I have, include set of vintage organs, too.

But I will try your suggestion in the next convinience.

[root]

I use B4_2 as a standalone using Windows 7 Pro 64 bit and initially could not get B4 to function,it was apparently activated but still requesting activation on start-up.
My solution was to uninstall B4, and delete both the 32bit and 64bit Windows registry details of B4.
Do a fresh install from my original CD but don't allow it to start the in-built service centre.
Down load a legacy service centre and say NO to the automatic later update, this will then allow entering of the activation sequence.
You then have to enter the registry and delete the following three files within the 64bit registry:
KEY,SNO, and SYSTEMid.
This allows B4 to run as a standalone in my 64bit Windows 7, and I imagine the same applies for
Win 10.
You can then use jBridge etc, for its use as a VST within a 64bit environment.
32bit registry found at:
HKEY_LOCAL_MACHINE,SOFTWARE,WOW6432NODE,NI,B4
delete KEY,SNO AND SYSTEMID prior to re-installation.
64bit registry found at:
HKEY_LOCAL_MACHINE,SOFTWARE,NI,B4
delete KEY,SNO and SYSTEMID prior to and after re-installing B4

Hope this is of use.
ps in the pathway, the comas should be backslash (keyboard issue)

Yeah man it did! Standalone and vst plugin now activated. Sucks they discontinued this and we should have a 64 bit version of the software. I'm in the credits for this one and I had to hack the registry to re-activate!

[Ah_Dziz]

does anybody know if these registry tricks will get vokator, Kontakt 2, elektrik piano and akoustik piano up and running via jbridge? They all show up registered in SC and they all run standalone, but they either won't launch or say they're in demo mode as plugins....... It sucks because I want to revisit old projects and tons of them use b4II and Kontakt 2 especially.

JJ

[KIMCHRISTOPHER]

Hi everyone, maybe you might be interested. An option for those who had to abandon Native's B4II due to its 32-bit architecture... I made some presets for the Arturia B3 using the B4 as a base. They were very close, maybe it will help to migrate to something with updates...
https://www.kvraudio.com/product/b-3-v2 ... /downloads