BFD3.5 Won't Authorize My Expansions

[BCy2k]

I’ve managed to update to BFD3.5 and thought I had it up and running just fine. I booted it up standalone today and it said I needed to authorize all of my Expansions (at least 30). I clicked the button to authorize and all I’ve seen for the past 45+ minutes is this screen with the orbiting dot and the word, “Authorizing…”

I quit and restarted and it still wants me to authorize my expansions. I already set up all of my content paths, and had it working inside Logic Pro, but it’s a hot mess in standalone.

Prior to updating to 3.5 I reauthorized all my expansions using the BFD license manager for the next 90 days. This was less than a week ago. Now this.

So what is the deal with BFD3.5? Are there any step by step instructions on things we need to know about installing it and using the new InMusic Software Center? I’ve actually looked, and as far as I can tell there aren’t any. That seems like a gigantic mistake. According to the new Software Center app all of my expansions were already authorized. So why do I need to do it again? And why is it taking forever? It’s been running for over an hour now.

Also, are we still going to have to reauthorize expansions every 90 days like the previous BFD LM system did? Because that system was ridiculous.

I just want my software to work when I boot it up. That’s it. So why isn’t it working all of a sudden?

[Steve63]

That is an extremely long time.

When we were testing the new software centre, this was quite common and was reported.
Whilst I wouldn’t say it was fixed, it’s much better than it was.

I don’t know why yours is taking so long, but I know the initial scan will be the longest and subsequent scan should be much quicker.

It might be worth reporting via a support ticket, in the mean time, leave it running, go and have something to eat, watch a film, write a song, write a book, go to church and pray.

Steve

[ggmanestraki]

@BCy2k

According to the new Software Center app all of my expansions were already authorized

That was the case for me too, but “Authorizing…” kept spinning. For me it was fixed when I redownloaded the content. Either re-downloading had something to do with it, or it was a complete fluke.

My guess: I think that while the packs are recognized by the authorization thingy, minor changes made to them recently throws it off and leaves it hanging. So, for me maybe it was hanging at Wooden Snares for example? Because my (already installed) content was two folders; one strings on and one strings off? Whereas the “new content” available for download - the “Wooden Snares” you download from the inMusic Software Center is just one folder?

I don’t know. But it seems plausible.

If you really hate having to go through redownloading all the content again, I’d say wait and see what support has to say. Otherwise it’s worth a shot.

[BCy2k]

Thanks for your replies.

I tried it in Logic again this morning and when it asked me to reauthorize my content I selected the, “Not at this time” option. It seems to be working fine although there are some oddities like the names of certain groove suites are completely missing and replaced by what looks like code-like gibberish. Several of the preset/kit icons are missing and these default to a BFD generic icon. See screenshots:

Scrambled groove suite names -

Missing preset/kit icons -

All of my expansions seem to be present and accounted for and I am able to load them up and play them both in Logic and standalone (as long as I DON’T try to authorize anything), but this release needs actual DOCUMENTATION because if I did everything right here, this is really bad beta level stuff that got released.

I’m definitely NOT interested in having to re-download & reinstall all of my expansion content. That’s around 400gb of stuff to reinstall between the BFD ones, Platinum Samples, & Sonic Reality expansions, that’s a huge (and ridiculous) ask just for an update.

I’m going to start a support ticked now. I’ll share whatever comes of it - which will hopefully be solutions.

[CHASER]

I haven’t through the complete procedure with All the Expansions and only Test/Trial install of the update on a separate machine using only the Pre 3.5 Core Library…Presets Kits etc etc.

BFD3.5 Authorizes/checks at every startup

There is a support page for Installing and recently updated (March 18,2025) and has Specifics for v3.5

“BFD3.5 is a major update for existing BFD3 users - BFD3, the Core Library and all Expansion content has received an update. This means BFD3 users must update all content/installers upon use with BFD 3.5.”
Use of old content with BFD 3.5 will result in unexpected behavior and is not recommended.

BFD 3 | How to Install & Authorize BFD 3 Software

BFD 3 | How to Install & Authorize BFD 3 Software

On the separate machine I moved the Pre 3.5 Core Library and Presets to an Ext HDD.
The Pre-3.5 Core Library shows Authorized…the Kits/Grooves, Presets were Divided up by BFD Engine Version and Not Authorized and nothing would load.
There isn’t more info on what exactly wasn’t Authorized…only the Drive Letter name for some folders while others showed the Path.Originally I scanned the entire Ext HDD…then scanned Individual Folders.
I had different results as far as folders showing.

After checking/comparing all of the info’s (BFD3.5 vs BFD3) for various components…a Minimum requirement…"MinimumRequiredEngineVersion=“3.5” has been added to the Core and Expansions Kit pieces and all Kits,Grooves,Presets,Palettes etc etc

I then uninstalled/removed everything…Did a “New” Full Install on Ext HDD…everything was Authorized and Everything loaded.

So…as suggest by ggmanestraki It might be taking longer during the scanning if you are working with Pre-3.5 Content.It took a long time just for the Core Library
Your experience may vary as “unexpected behavior” is kind of Broad.

I haven’t proceeded any farther as I don’t want to lose/destroy all of the detailed info including Recording Studio Info (some of the expansions were recorded at the same Studio under similar conditions) I did for the Core Library and all of the Expansions as I prefer proper definitions.
The update is not Critical for my use which is the Standalone and Primarily E-Kits.
I only have the InMusic Version on one machine.
If the InMusic BFD3 Version dies after 90 days I still have the FXpansion Version on a couple machines…It’s a lot of work to re-do all the edits and add the new minimum version requirement and then have BFD4 or whatever it may be called…come out and back to square one yet again.

For Example:

I lost all of the Custom/Edits and back to the Original Default Kit Piece names/info in 3.5

Bottom Line…and to say the quiet part out loud…

BFD3.5 requires a NEW Install… including All Expansions…

[BCy2k]

Thanks for this info CHASER, much appreciated. Not exactly what I was hoping for solution-wise, but if it’ll eventually lead to a better overall BFD experience, I’m game.

It would have been extra helpful if this info were included with an actual announcement regarding the launch of the 3.5 update. Which I learned of purely by accident. It’s a little baffling that neither was offered for current users. I really don’t get that.

More importantly, it would have been a really good, critical thing for users to know that this update requires a total uninstall and reinstall of ALL CONTENT. Imagine being right in the middle of a time sensitive project and having to deal with a surprise such as this?

At least I know which way is the path forward now. Thanks again CHASER (and you beat BFD support by 24 hours and counting)!

One last question, is there an uninstaller, or will that need to be done manually? Any step by step instructions? This is going to take a chunl of time to sort out.

[ggmanestraki]

@BCy2k

reinstall of ALL CONTENT

Personally, I wouldn’t bet that all content needs redownloading, just what is sold/supported by InMusic. Personally, I didn’t have to redownload Dark Farm yet (I was leaving that for last due to the ~100 GB size). It was probably other expansions that were failing to authorize. So if you have lots of 3rd party stuff (Platinum Samples, Sonic Reality etc), I wouldn’t start the process of redownloading from those, just the core stuff that shows up in the Inmusic Software Center.

@CHASER

There isn’t more info on what exactly wasn’t Authorized…

That would help a lot though. If the spinning Authorizing thingy would spare some letters about what it is that’s being authorized at the moment of the scan. So that people can pinpoint exactly which pack gives them trouble. Because you can’t really know how many expansions a user kept installed before 3.5, right? Others have tons, others just one or two.

[SoundMILL]

BFD3.5 continues to be unusable here. working on a 3rd pass atm, but the inability to authorize content that has worked fine for years (albeit for random intervals) is more than an ‘inconvenience’. having to download/reinstall the core library has been taking 2-3 hrs each time (InMusic server load…?) and frankly makes makes no sense wrt to any expansions. having to re-download 450GB+ of expansions is just not worth the effort given there is no guarantee anything will work.

@CHASER

After checking/comparing all of the info’s (BFD3.5 vs BFD3) for various components…a Minimum requirement…"MinimumRequiredEngineVersion=“3.5” has been added to the Core and Expansions Kit pieces and all Kits,Grooves,Presets,Palettes etc etc

this could be a move to get as much of their potential user base on the latest release in order to limit support issues but there are better ways to “tag” content than re-download such heavy files. can’t imagine they’ve done anything to the actual samples.
…
other former BFD users in my network are reporting similar issues and holding off until things get worked out. i’m sticking with it for one more pass, hoping for the best.

[CHASER]

NOTE:
replies were made while post was waiting for Approval.
It appears there isn’t a Moderator 24/7…so those of us in the US have a longer approval period.

The exact procedure for a New “Clean” Install will vary…
Those that went from FXpansion BFD3 > InMusic BFD3 Migration > InMusic BFD3.4 (New LM) >InMusic BFD3.5 IM Software Center…it might be quite a mess.
The InMusic Updates did not remove the FXpansion Folders so many remain thoughout the system.
This causes doubles,triples etc etc for Kits/Presets.
Some of the Expansions had the Grooves folder in the Audio Folder and not the System Folder.

The New BFD3.5 Core Library Installer places the DATA…Grooves,Kits,Presets,Processed Drums,Resources into the Core Library Folder.

Previously they were All placed into the System Folder.
I would Presume the New Expansion Installers will do the same.
The 3.5 scan did not show doubles , if it indeed scans the system folder along with the Core Library Folder.

There are “Compatibility Patches”…in the Main BFD3 Folder.
These patches are not in the Installer Payload so they must be installed during the Scan.

The compatibility patches are for Groove Palettes similar to the image posted by BCy2k (Scrambled Groove names)…Artic Tweaks,Presets,Kits etc and add the Minimum Requirement 3.5 add on I mentioned previously and possibly the New ‘Mics’ control.
I show almost 11,000 Compatibility patches in the Folder and after checking files at random I ran across multiple Expansions.

Unknown when or how these are applied…perhaps during the initial scanning it is determined what is needed based on the expansion/Grooves you have.
It may be contributing to the long initial scanning time.

There are also Trigger/Sets files (.JSON) for the New Alesis Strata Drum Modules…in the System Folder.

It appears the Modules may have USB Trigger Interface,maybe some Editing or something along those lines…pure speculation.
Drum Modules typically just require MIDI maps.
There is No reference for these in the manual.

As far as “Housekeeping” and removing everything unnecessary prior to v3.5
I would imagine …worse case scenario… for those who migrated and still have the FXpansion Folder/remnants…(unless you still have BFD2.) would be to locate/Remove all of those…make copies of all User Kits…Presets…Palettes/grooves/User Samples etc etc.
Open the License manager and take a screenshot of All products/Expansions/Serial Numbers , especially if you don’t see them in the InMusic Software Center or your InMusic profile.

The InMusic 3.4 Expansion Installers placed Uninstallers for each expansion in the Program Folder(Win).
I would presume something similar for macOS…maybe in the Applications Folder.

In the Software Center…do the expansions show as Activated/Installed…or just available for Download?

I would probably Deactivate (If shown as activated) the Expansions…in case there is a download limit now like the program (2 or 3 machines?)

Then use the InMusic Uninstallers for each Expansion to make sure everything is cleared out properly.

Then download/Install/Authorize the Expansions in BFD3.5…One by One to shorten the initial scan.
After the Initial scan I went through for the Proper 3.5 Core Library,on startup it checks Login Staus and Product Registrations and is done in under 10 sec.

User saved Kits Presets etc still go to the Documents Folder…so you can place all User back to that location or add all of the User Content to the Core Library Folder (this way everything is in one place)…I believe some are initially required to be saved in the Documents Folder upon creation unless it changed in this version…you can then move them over.
Then rescan .

[Phileosophos]

BFD3.5 requires a NEW Install… including All Expansions…

Does that mean any presets and such I’ve created on my own from older content will no longer work properly? Because that would be a burden I simply cannot tolerate. I’d like to update, but I’m not doing so if it means I throw away years of work.

[CHASER]

I haven’t proceeded any farther than what I posted above…

The Information I am going on is what is posted on the Support Page..

BFD3.5 is a major update for existing BFD3 users - BFD3, the Core Library and all Expansion content has received an update. This means BFD3 users must update all content/installers upon use with BFD 3.5.

Use of old content with BFD 3.5 will result in unexpected behaviour and is not compatible with this update.

The BFD Core Library had Library info changes as did the Audio Content, Grooves,Kits,Presets etc.

The Library info are the Paths for the Content.

OLD
info_library=“BFD3” info_librarylong=“BFD 3”

NEW
info_library=“BFD30” info_librarylong=“BFD3 Core Library”>

info_library= Is the Path used for actions such as..changing drums in Kit View..Right Click you’ll see the Codes.

info_librarylong= is the Path to the Audio Folder/Content.
This info are at the beginning of the Kits/Presets etc with the slots and Kit Piece assignments next in the order.
The Info_library will change to “User” when anything is created by a User
The info_library long will change to User..or Folder name it is saved in (Typically “User”)

The Expansion I Tested BFD Crush (small expansion under 5GB) did Not Authorize…Audio,Presets Kits etc.
I copied (without thinking) from a FXpansion Machine so I copied a Library with an OLD library info.
I have yet to add one to the ext HDD from the InMusic (3.4) Machine (other than the Core Library Test) as I am sure I would have to “Install” it as the New 3.4 Installers added more requirements for the New Licensing,probably additional Registry Entries,Uninstallers etc.

OLD (FXpansion)
info_library=“FXCRU” info_librarylong=“BFD Crush”

OLD (InMusic 3.4)
info_library=“BFCRU” info_librarylong=“BFD Crush”

NEW (3.5)..Unknown
info_library=“____” info_librarylong=“________”

I don’t know if any of the Library Info changed for the Expansions..
You would have see if a User Kit,Preset etc loads correctly..with all correct Content/Kit Pieces etc and re-save it.

I haven’t seen a post yet from any members with issues loading User Kits/Presets etc and BFD3.5.
Unknown if there is a “Compatibility Patch” for User Grooves/Kits/Presets/ etc or how it would be applied if a user attempted a Batch Import.
I don’t know if a Batch Import will correct anything other than perhaps add 3.5 minimum requirement,especially if there are User files from multiple Expansions.

There has been little participation or direction ..one way or the other..Yay..Nay etc..from a Beta Team member so I presume the NDA is still on…
Currently it seems to be trial and error…

[Phileosophos]

Thanks for the additional context. I won’t be updating until it’s clear all this stuff has been sorted.

[otalgia-2000]

That was the case for me too, but “Authorizing…” kept spinning. For me it was fixed when I redownloaded the content. Either re-downloading had something to do with it, or it was a complete fluke.

My guess: I think that while the packs are recognized by the authorization thingy, minor changes made to them recently throws it off and leaves it hanging. So, for me maybe it was hanging at Wooden Snares for example? Because my (already installed) content was two folders; one strings on and one strings off? Whereas the “new content” available for download - the “Wooden Snares” you download from the inMusic Software Center is just one folder?

I don’t know. But it seems plausible.

If you really hate having to go through redownloading all the content again, I’d say wait and see what support has to say. Otherwise it’s worth a shot.

I’m jumping into this thread somewhat belatedly in hopes that my admittedly lower-density perspective is of use to it:

Having today DL’d 2 expansions new to me and then launching the standalone to complete their installation, I too encountered a loop during the “AUTHORIZING” process.

A mere five minutes of that hangup seemed kinda too long for me, so I (verrrry reluctantly) quit the standalone with AUTHORIZING still going on. I really hate doing that, but needed to get on with my day.

At this point I need to point out some ignorance of my own: I had launched the standalone because I was under the impression that I would need to then go to the Content Locations screen and do a re-scan. (…And maybe I should do that, but…)

…I then re-launched the BFD 3.5 standalone and, allowing a moment for the “CHECKING REGISTRATIONS” process, BFD just jumped right up and barked with both new expansions now on board.

Those of you already on the thread have clearly been doing a much deeper dive under the hood than I’m qualified for. And I can also see that you’re discussing installs with many more expansions and user-customizations than mine.

But I wanted offer both my Eternal Authorization experience of (again, reluctant) “oh just quit it in the middle and try again,” and also mention one additional aspect which might be of significance: that I’m on Mac OS.

I confess that I haven’t read the thread super-closely, but some of the screenshots in it appear to come from the Windows environment, and perhaps there’s a detail that might be worth noting.