Band-in-a-Box Pro 2024. Fresh install on Windows 11.
Every time I start BIAB, I get an access violation in bbw64.exe. NONAME.SGU is in the title bar.
BIAB seems to work after the crash, but just ignoring this serious problem doesn't seem right.
Any suggestions ?
You should definitely send the error log report to PG Music as suggested. An Access Violation is a serious unhandled error, and should be managed effectively by the program.
BIAB & RB2026 Win.(Audiophile), Windows 10 Pro & Windows 11, Cakewalk Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Session Keys Grand S & Electric R, Kontakt, Focusrite 18i20, KetronSD2, NS40M, Pioneer Active Monitors.
1. Make sure Band-in-a-Box is not running 2. In the Preferences sub-folder, create a file named safemode.txt It can be an empty file, it's only the file name that's important. 3. Start Band-in-a-Box. You will see a text message confirming that it is in "safe mode". 4. This forces the program to start using factory settings. 5. Test to see if the problem still occurs using this method. 6. Afterwards, you can close Band-in-a-Box and delete or rename the file.
This method means that you won't have made any changes to your overall settings.
(Also, welcome to the forums)
Last edited by AudioTrack; 05/07/2402:27 AM.
BIAB & RB2026 Win.(Audiophile), Windows 10 Pro & Windows 11, Cakewalk Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Session Keys Grand S & Electric R, Kontakt, Focusrite 18i20, KetronSD2, NS40M, Pioneer Active Monitors.
I just started getting this same error. None of the things PG support asked me to try had any effect. I still get the error.
I'm on the latest version of Win11 Pro.
Question to those of you also experiencing this access violation: are you on the latest version of Win11? Is it possible that a recent Windows update is responsible?
I don't mean to suggest that I'm happy about the situation, but I'm happy that I'm not the only one. That tells me that there's a real problem.
Now, after doing a full reset to factory defaults, I've got to try to remember how I got my BiaB UI set up the way I did. Sigh.
Last edited by TheMaartian; 05/10/2411:23 PM.
ThinkPad i9 32GB RAM 7TB SSD; Win11 Pro; RME Fireface UCX II; BiaB 2026 Ultra Studio Pro 8; Tonalic Studio 1; Reaper v7; Bitwig Studio 6; Melodyne Studio 5 Gig Performer 5; NI S61 MK3; Focal Shape 65; Beyerdynamic DT 880 & 770
It's absolutely a minor problem. I don't even report it.
2024 Crash on Startup is a minor problem? How so?
BIAB & RB2026 Win.(Audiophile), Windows 10 Pro & Windows 11, Cakewalk Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Session Keys Grand S & Electric R, Kontakt, Focusrite 18i20, KetronSD2, NS40M, Pioneer Active Monitors.
Here are some thoughts that occurred to me as I read your post.
Where have you installed BIAB. Is it in C:\Program Files" by any chance? If it is, this is not a good location for the program.
Also, it would be worthwhile right-clicking on the shortcut and then choose "Run as administrator" when you start it to see if that makes a difference.
Lastly... Go to \bb\Prefences and rename intrface.bbw to intrface.bbw.old and MySetup.DK to MySetup.DK.old ... Doing this forces BIAB to create new versions of these start-up files. If that doesn't solve the problem, you can always go to \bb\Preferences and delete the new versions of these files and return to the old versions by removing the .old from the extension.
If any program my company developed crashed with an A/V after first startup, I would make it a priority to resolve and fix. Others may have a different approach, but that's what I would do, without exception.
BIAB & RB2026 Win.(Audiophile), Windows 10 Pro & Windows 11, Cakewalk Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Session Keys Grand S & Electric R, Kontakt, Focusrite 18i20, KetronSD2, NS40M, Pioneer Active Monitors.
I just started getting this same error. None of the things PG support asked me to try had any effect. I still get the error.
I'm on the latest version of Win11 Pro.
Question to those of you also experiencing this access violation: are you on the latest version of Win11?
I'm using Windows 11 Home version 23H2 build 22631.3447.
Originally Posted by Noel96
Where have you installed BIAB. Is it in C:\Program Files" by any chance? If it is, this is not a good location for the program.
It's in C:\Band-in-a-Box Except one folder, which I didn't choose : C:\Program Files\PG Music Inc\Band-in-a-Box Sounds
Why would Program Files be a bad location for a program ? That's where programs are supposed to be installed, and it has been for almost 30 years.
Originally Posted by Noel96
Also, it would be worthwhile right-clicking on the shortcut and then choose "Run as administrator" when you start it to see if that makes a difference.
[...] rename intrface.bbw to intrface.bbw.old and MySetup.DK to MySetup.DK.old [...]
PG Support told me to do that and to Reset to factory defaults, it didn't help.
Originally Posted by MoultiPass
If Biab works it's a minor problem.
If a program causes an access violation, it doesn't work. It is not a minor problem, it's a major problem. Anything the program does after the crash is Undefined behavior. This is particularly risky in a program that uses plugins from unknown publishers.
Why would Program Files be a bad location for a program ? That's where programs are supposed to be installed, and it has been for almost 30 years.
Well, that's not right at all. That used to be the desired location, but Windows security changes and more in recent years (the last 15 years at least) have indicated that this is now not to desirable location.
C:\bb\ is the default location (substitute 'C:' for any other drive.)
'Program Files', and 'Program Files (x86)' etc are a big no-no (for many years now).
It's all about security.
BIAB & RB2026 Win.(Audiophile), Windows 10 Pro & Windows 11, Cakewalk Bandlab, Izotope Prod.Bundle, Roland RD-1000, Synthogy Ivory, Session Keys Grand S & Electric R, Kontakt, Focusrite 18i20, KetronSD2, NS40M, Pioneer Active Monitors.
Why would Program Files be a bad location for a program ? That's where programs are supposed to be installed, and it has been for almost 30 years.
Well, that's not right at all. That used to be the desired location, but Windows security changes and more in recent years (the last 15 years at least) have indicated that this is now not to desirable location.
C:\bb\ is the default location (substitute 'C:' for any other drive.)
'Program Files', and 'Program Files (x86)' etc are a big no-no (for many years now).
It's all about security.
The only program installed in a root folder on my system is Band-in-a-box, so if you are right there are a lot of software companies doing this wrong.
Can you point to any information about how Program Files was phased out ?
C:\Band-In-A-Box should be an okay folder to use. While PG Music recommend \bb, it's possible to vary that without issue.
Can you try these couple of things and see what happens.
(1) Go to C:\Band-In-A-Box and then double click on BBW64.EXE. This is simply starting the program without using a shortcut. (Doing this is a check to see if the shortcut might be including some unusual startup instructions.)
(2) Also try starting BIAB in 32-bit mode and see what happens. To do this, go to C:\Band-In-A-Box and double-click on BBW.EXE. Does this version of BIAB start okay or not?
(3) Please have a look under "Help | About Band-In-A-Box" and check that you have the latest update installed. It should say "Version 2024(1111)". This is indicating that you have update #1111 installed (which is the latest update).
1) We know from experience that BIAB will not work if installed into either one of the /Program Files folders. We have known this for decades (I tried it once over twenty years ago) and PG Music has confirmed not to do that.
What we do not know is why. I concur it probably has to do with changes in Windows related to security - the security OF Windows. As I recall, BIAB actually could start to run if it was installed in a /Program Files folder, but would immediately crash when any action took place that tried to save into that folder.
Why other applications install into /Program Files folders and work, when BIAB does not, is unknown to me.
2) The addition of the safemode.txt is an alternative to this: " rename intrface.bbw to intrface.bbw.old and MySetup.DK to MySetup.DK.old ". If one didn't work, it's not a surprise the other did not.
3) I recall reading a comment from Support that you do not HAVE to call the BIAB folder BB. The installer certainly will want to do so, but if you are very careful to change the recommended folders in each step of the install, and each step every upgrade forevermore, then it can go into a different folder. Just not one of the /Program Files folders.
4) What I don't fully understand is exactly what is happening with this: if BIAB crashes on startup, how do you continue to work with it? I think you may be saying something like "BIAB crashes on startup the first time, but then runs normally". Is that correct? That would be quite a different problem statement, requiring a different examination.
EDIT: I like everything Noel just wrote while I was typing my comments.
Last edited by Matt Finley; 05/11/2412:47 PM.
BIAB 2026 Win Audiophile. Software: Fender Studio One 8, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Fender Quantom HD8 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Go to C:\Band-In-A-Box and then double click on BBW64.EXE.
Access violation
Originally Posted by Noel96
go to C:\Band-In-A-Box and double-click on BBW.EXE.
Access violation
Originally Posted by Noel96
Please have a look under "Help | About Band-In-A-Box" and check that you have the latest update installed. It should say "Version 2024(1111)".
It says Version 2024 (1111)
Originally Posted by Noel96
What antivirus software do you use?
Windows Security (Comes with Windows 11)
Originally Posted by Matt Finley
What I don't fully understand is exactly what is happening with this: if BIAB crashes on startup, how do you continue to work with it? I think you may be saying something like "BIAB crashes on startup the first time, but then runs normally". Is that correct? That would be quite a different problem statement, requiring a different examination.
From the first post in this thread : Every time I start BIAB, I get an access violation in bbw64.exe.
Thanks, Sid. This is indeed a strange problem that you have.
Out of curiosity, if you go to "Audio | Audio drivers.settings", what is your Audio Driver Setup? By default, it should be WAS. Try changing this to MME, exit the menu and then restart BIAB. Does this make a difference?
What I don't fully understand is exactly what is happening with this: if BIAB crashes on startup, how do you continue to work with it? I think you may be saying something like "BIAB crashes on startup the first time, but then runs normally". Is that correct? That would be quite a different problem statement, requiring a different examination.
Originally Posted by Sid S
[From the first post in this thread : Every time I start BIAB, I get an access violation in bbw64.exe.
OK. I hope you don't mind that I'm just trying to clarify. Yes, you said that you get an access violation in bbw64.exe every time you start BIAB [my emphasis]. But then you went on to say this "BIAB seems to work after the crash, but just ignoring this serious problem doesn't seem right.". So you do seem to be saying it crashes only the first time, or maybe even most of the time, but then it does not crash.
Please elaborate.
BIAB 2026 Win Audiophile. Software: Fender Studio One 8, Swam horns, Acoustica-7, Notion 6, Song Master Pro, Win 11 Home. Hardware: Intel i9, 32 Gb; Fender Quantom HD8 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
go to "Audio | Audio drivers.settings", what is your Audio Driver Setup? By default, it should be WAS. Try changing this to MME, exit the menu and then restart BIAB. Does this make a difference
It was WAS, changing it to MME does not help.
On a side note, changing it to ASIO causes an immediate access violation, probably because I don't have any ASIO drivers. But that's a different bug.
OK. I hope you don't mind that I'm just trying to clarify. Yes, you said that you get an access violation in bbw64.exe every time you start BIAB [my emphasis]. But then you went on to say this "BIAB seems to work after the crash, but just ignoring this serious problem doesn't seem right.". So you do seem to be saying it crashes only the first time, or maybe even most of the time, but then it does not crash.
Please elaborate.
I don't mind at all, I appreciate that everybody wants to help here.
Every time I start BIAB, I face two message boxes due to an access violation. In my brain, that is a crash.
Now, BIAB detects this serious problem and continues operating. In my book, that's bad practice but anyway - BIAB seems to work after that, until the next time I start it.
Ya, this is not a "crash", but I agree 100% with everything else you are saying. By the way, I have BIAB at c:\BB. And I don't see any access violation message. Good luck.
XPro & Xtra Styles PAK Sets On Sale Now - Until May 15, 2026!
All of our XPro Styles PAKs and Xtra Styles PAKs are on sale until May 15th, 2026!
It's the perfect time to expand your Band-in-a-Box® style library with XPro and Xtra Styles PAKs. These additional styles for Band-in-a-Box® offer a wide range of genres designed to fit seamlessly into your projects. Each style is professionally arranged and mixed, helping enhance your songs while saving you time.
What are XPro Styles and Xtra Styles PAKs?
XPro Styles PAKs are styles that work with any version (Pro, MegaPAK, UltraPAK, UltraPAK+, or Audiophile Edition) of Band-in-a-Box® 2025 (or higher). XPro Styles PAKS 1-10 includes 1,000 styles!
Xtra Styles PAKs are styles that work with the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box® 2025 (or higher). Xtra Styles PAKs 1-21 includes 3,700 styles (and 35 MIDI styles)!
The XPro & Xtra Styles PAKs are not included in any Band-in-a-Box® package.
The XPro Styles PAKs 1-10 are available for only $29 ea (reg. $49 ea), or get them all in the XPro Styles PAK Bundle for only $149 (reg. $299)! Listen to demos and order now! For Mac or for Windows.
The Xtra Styles PAKs 1-21 are available for only $29 ea (reg. $49 ea), or get them all in the Xtra Styles PAK Bundle for only $199 (reg. $349)! Listen to demos and order now! For Mac or for Windows.
Note: XPro Styles PAKs require Band-in-a-Box® 2025 or higher and are compatible with ANY package, including the Pro, MegaPAK, UltraPAK, UltraPAK+, and Audiophile Edition.
The Xtra Styles require the UltraPAK, UltraPAK+, or Audiophile Edition of Band-in-a-Box®. (Xtra Styles PAK 19 requires the 2025 or higher UltraPAK, UltraPAK+, or Audiophile Edition. They will not work with the Pro or MegaPAK version as they require the RealTracks included in the UltraPAK, UltraPAK+, or Audiophile Edition.
Supercharge your Band-in-a-Box today with XPro Styles PAKs and Xtra Styles PAK Sets!
With the release of Band-in-a-Box® 2026 for Mac, we’re rolling out a collection of brand-new videos on our YouTube channel. We’ll keep this forum post updated so you can easily find all the latest videos in one convenient spot.
Whether you're exploring new features, checking out the latest RealTracks or Style PAKs, this is your go-to guide for Band-in-a-Box® 2026.
Band-in-a-Box® 2026 for Mac is here and it is packed with major new features! There’s a new modern look, a GUI redesign to all areas of the program including toolbars, windows, workflow and more. There’s a Multi-view layout for organizing multiple windows. A standout addition is the powerful AI-Notes feature, which uses AI neural-net technology to transcribe polyphonic audio into MIDI—entire mixes or individual instruments—making it easy to study, view, and play parts from any song. And that’s just the beginning—there are over 100 new features in this exciting release.
Along with version 2026, we've released an incredible lineup of new content! There's 202 new RealTracks, brand-new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two new RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
Special Offers
Upgrade to Band-in-a-Box® 2026 for Mac and save up to 50% on most upgrade packages during our special offer—available until May 15, 2026. Visit our Band-in-a-Box® packages page to explore all available upgrade options.
2026 Free Bonus PAK & 49-PAK Add-ons
Our Free Bonus PAK and 49-PAK are loaded with amazing add-ons! The Free Bonus PAK is included with most Band-in-a-Box® 2026 for Mac packages, but you can unlock even more—including 20 unreleased RealTracks—by upgrading to the 2026 49-PAK for just $49.
Band-in-a-Box® 2025 for Mac® users: Build 904 now available!
If you're already using Band-in-a-Box® 2025 for Mac®, make sure to grab the latest update! Build 904 is now available for download and includes the newest additions and enhancements from our team.
One of our representatives will be happy to help you over the phone. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday, and 8:00AM to 4:00PM PST Saturday. We are closed Sunday. You can also send us your questions via email.
One of our representatives will be happy to help you on our Live Chat or by email. Our hours of operation are from
6:00AM to 6:00PM PST (GMT -8) Monday thru Friday; 8:00AM to 4:00PM PST (GMT -8) Saturday; Closed Sunday.
Dansk
Deutsch - Windows
Español
Français - Windows
Italiano - Windows
Nederlands
Polski
Português
Svenskt
русский
Japanese
Simplified Chinese
Traditional Chinese
Korean