Given that we now know that there are other files with the same filename (but different file extension), it may be an audio file that produces the error. You might try renaming the WAV or the MP3 file to something else and testing to see if you get the same error.
Tip: If a file with the same filename but a .WAV extension is in the same folder as the .MGU file, BiaB will try to load that WAV file.
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 don't know where you are finding those "10 additional files", but I am sure they don't belong there. Did you create this files? What is the higher parent document names so we can find where your original folder is:
The original folder name of the original problem song is: 20 Beethoven Allegro (G major)
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
MGX Files: When a MIDI file is loaded onto the Melody (or Soloist) track, the Track Type for the Melody (or Soloist) gets set to Multi-Track. When the file is saved, the extension will be .MGX
The .SIB file is is a Sibelius music notation file.
The .MXL is a compressed music XML file.
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 may do that. First I wanted to see if we are dealing with a corrupt file here. I think it would also be helpful (maybe not in this thread) to hear more about ‘corrupt files’.
Hi again Matt,
The info and tips I got from you and Simon remain at the top of my "to do" list but since my wife and I had to step away for a couple of days I've had to put executing those things off until at least the middle of next week. She insists that it is way past the time that my machine should have been backed up and cloned and I completely agree with her.
She remains out of town for now but I'm back on the Ponderosa alone trying to get caught up on the posts and other correspondence I've missed while I was away.
But getting back to the status of chasing down a solution to this nuisance window problem, I've got some great news! This case is almost over!
The info and 7-step suggestion list I got from Jim Fogle by way of Noel96 put me right on the trail of the culprit! I don't think the problem is with BIAB per se... It has something to do with the other 10 files that are in the same directory. I don't know exactly which file(s) yet but I know what to do to find out but I want to answer all of my correspondence first before I put those 10 suspects in a lineup and isolate the guilty file(s). As soon as I isolate the guilty culprit(s) I'll place the "Resolved" stamp on the thread and hopefully a virtual bottle of champagne!
I have to thank you and everyone here for your patience with me and putting up with the severe case of logorrhea I've developed over the years. Most of the time I contain it very well but when I get really frustrated, starts to get the better of me.
Anyway, thanks again for all of your input... you've been a great help!
If the issues occur on a song file you are actively working on, the song file may be slightly corrupt. If so, I may know of a solution that was originally proposed by forum member Noel96.
Save your existing song file under a new name.
Hi Jim
Although I only did one of the steps you suggested, I'm going to keep that whole process in my BIAB Affairs Folder for any possible future issue where it might be useful.
I'm really appreciative of all the effort and time that everyone spent on making comments and suggestions to help me out with the nuisance pop-up window issue I was experiencing.
Somewhere in this thread I stated that I knew the solution and answer was going to come from someone right here in this Forum community or the Support Team. Knowing how busy the PG Music people are, during this time of year in preparing things for their annual end-of-the-year new product release, I felt in my heart that the answer would come from this Forum Community before they had a chance to get back to me as the said they would.
It was definitely the input I got from you by way of Noel96 that actually put me on the trail of isolating the problem file. With the info that was revealed from doing only the first of the steps you suggested, I had a hunch that the problem was either the MP3 file or the wav file that was in the "problem directory". It turned out to be the wav file.
BAIB makes that wav file and for some reason it got corrupted and when I deleted it, BIAB simply made another one! It's kind of like when we have to sometimes delete the intrface.bbw file in the BB Preferences folder... the program just makes another one, the problem is solved, and the beat goes on!
After it made a new wav file, I pressed the Generate button 25 times in a row and there was no nuisance pop-up windows in sight! So, ding dong, the wicked witch is dead! This problem is solved!
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
I will say it again. This is just not so! There is no "My Song.wav" created when you simply regen a "My Song.mgu" file. I will go even further, if you were to intentionally Render the audio during playback, yes it would create a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point.
And finally where ever and what ever Utility tracks are doing with .wav files, I am the first to admit I have no idea.
Hope I am not hijacking this tread, but I am in a grumpy mood this morning.
sigh...i wish art would post the troublesome biab song file somewhere so the rest of us can test it for him. om
my songs....mixed for good earbuds...(fyi..my vocs on all songs..) https://soundcloud.com/alfsongs (90 songs created useing bb/rb) (lots of tips of mine in pg tips forum.)
... a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point.
It certainly confused the Hell out of me, as that .wav file will/can then be read back into BiaB and plays alongside the normal tracks, causing some very puzzling behaviours.
And if we new users don't know that's what happens, may not either be aware of that, so we may well not mention when reporting those strange behaviours.
Henry Clarke highlights this and some "good practices" to circumvent the problem in one of his (excellent, IMHO) BiaB tutorials. Ah ... here it is, there's an explanation of how he uses utility tracks and how to manage the .wav files.: https://youtu.be/XiPqQjISmb4?list=PLNGYsTA3YLQSZv0fgfcy0ukVF7zW2JSJu&t=320
Jazz relative beginner, starting at a much older age than was helpful. AVL:MXE Linux; Windows 11 BIAB2026 Audiophile, a bunch of other software. Kawai MP6, Ui24R, Focusrite Saffire Pro40 and Scarletts .
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
I will say it again. This is just not so! There is no "My Song.wav" created when you simply regen a "My Song.mgu" file. I will go even further, if you were to intentionally Render the audio during playback, yes it would create a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point.
And finally where ever and what ever Utility tracks are doing with .wav files, I am the first to admit I have no idea.
Hope I am not hijacking this tread, but I am in a grumpy mood this morning.
Just so you fellers know..... it's not a bug. It can be useful to Mac users that don't have RealBand and users of both PC and Mac that have not upgraded to a version with Utility Tracks.
It's the only way for audio to be converted and be placed onto a Legacy Track in the BIAB Mixer. It's also an integral component of user Artist Performance Track process.
Here's a link to a post I made about Performance Tracks feature in February 2020.
From the manual (yes, file names have cryptic meanings):
MGU Files: A Band-in-a-Box song called “My Song.MGU” will have the associated wave file called “My Song.wav.”
I will say it again. This is just not so! There is no "My Song.wav" created when you simply regen a "My Song.mgu" file. I will go even further, if you were to intentionally Render the audio during playback, yes it would create a "My Song.wav" in the same directory, with the same name, but I always considered that a bug - not a feature, since it will confuse the heck out of new users at some point. ... Hope I am not hijacking this tread, but I am in a grumpy mood this morning.
Dear grumpy, you are indeed correct, and the manual (page 497) is indeed misleading. Moreover, I never thought the creation of the same-name WAV file in the background was a good idea especially as once created, it essentially interacts with the BiaB song file.
PS: Don't be grumpy It's not your style.
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.
Interacts means it’s a good feature when intended.
Interferes might be a better description when not intended. The forum often has posts where users don’t understand why they are still hearing something they know they changed.
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; Presonus Quantom HD8 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Interacts means it’s a good feature when intended.
Interferes might be a better description when not intended. The forum often has posts where users don’t understand why they are still hearing something they know they changed.
Correct. 'Interferes' is a more appropriate term in this instance.
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.
Interacts means it’s a good feature when intended.
Interferes might be a better description when not intended. The forum often has posts where users don’t understand why they are still hearing something they know they changed.
Correct. 'Interferes' is a more appropriate term in this instance.
Oh, I know you knew that. I'm more wondering, what do we do about it? Recommend a caution message if an audio file of the same song name exists?
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; Presonus Quantom HD8 & Faderport 8, Royer 121, Adam Sub8 & Neumann 120 monitors.
Oh, I know you knew that. I'm more wondering, what do we do about it? Recommend a caution message if an audio file of the same song name exists?
When anyone renders a wav file to disk he should be asked to name it and its location. Then if he wants to load it onto the audio track it should ask where is the file and what is its name. Once it is loaded and saved on a track it should remember it and load it automatically the next time the file is opened.
Oh, I know you knew that. I'm more wondering, what do we do about it? Recommend a caution message if an audio file of the same song name exists?
When anyone renders a wav file to disk he should be asked to name it and its location. Then if he wants to load it onto the audio track it should ask where is the file and what is its name. Once it is loaded and saved on a track it should remember it and load it automatically the next time the file is opened.
Pretty standard file and track management.
Well, except for the User Artist Performance Track function which does all of that automatically as part of an advanced freeze option as one of the many things it can do.
I suggest educating users to the feature is the best recommendation because knowing what it does solves more issues than it causes and once users are aware of it, there's no longer a problem with an 'unknown' track playing.
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.
PowerTracks 2026 is here—bringing powerful new enhancements designed to make your production workflow faster, smoother, and more intuitive than ever.
The enhanced Mixer now shows Track Type and Instrument icons for instant track recognition, while a new grid option simplifies editing views. Non-floating windows adopt a modern title bar style, replacing the legacy blue bar.
The Master Volume is now applied at the end of the audio chain for consistent levels and full-signal master effects.
Tablature now includes a “Save bends when saving XML” option for improved compatibility with PG Music tools. Plus, you can instantly match all track heights with a simple Ctrl-release after resizing, and Add2 chords from MGU/SGU files are now fully supported... and more!
Get started today—first-time packages start at just $49.
Already using PowerTracks Pro Audio? Upgrade for as little as $29 and enjoy the latest improvements!
Band-in-a-Box 2026 for Windows Special Offers End Tomorrow (January 15th, 2026) at 11:59 PM PST!
Time really is running out! Save up to 50% on Band-in-a-Box® 2026 for Windows® upgrades and receive a FREE Bonus PAK—only when you order by 11:59 PM PST on Thursday, January 15, 2026!
We've added many major new features and new content in a redesigned Band-in-a-Box® 2026 for Windows®!
Version 2026 introduces a modernized GUI redesign across the program, with updated toolbars, refreshed windows, smoother workflows, and a new Dark Mode option. There’s also a new side toolbar for quicker access to commonly used windows, and the new Multi-View feature lets you arrange multiple windows as layered panels without overlap, making it easier to customize your workspace.
Another exciting new addition is the new AI-Notes feature, which can transcribe polyphonic audio into MIDI. You can view the results in notation or play them back as MIDI, and choose whether to process an entire track or focus on specific parts like drums, bass, guitars/piano, or vocals. There's over 100 new features in Band-in-a-Box® 2026 for Windows®.
There's an amazing collection of new content too, including 202 RealTracks, new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
Upgrade your Band-in-a-Box for Windows to save up to 50% on most Band-in-a-Box® 2026 upgrade packages!
Plus, when you order your Band-in-a-Box® 2026 upgrade during our special, you'll receive a Free Bonus PAK of exciting new add-ons.
If you need any help deciding which package is the best option for you, just let us know. We are here to help!
Band-in-a-Box® 2026 for Windows® Special Offers Extended Until January 15, 2026!
Good news! You still have time to upgrade to the latest version of Band-in-a-Box® for Windows® and save. Our Band-in-a-Box® 2026 for Windows® special now runs through January 15, 2025!
We've packed Band-in-a-Box® 2026 with major new features, enhancements, and an incredible lineup of new content! The program now sports a sleek, modern GUI redesign across the entire interface, including updated toolbars, refreshed windows, smoother workflows, a new dark mode option, and more. The brand-new side toolbar provides quicker access to key windows, while the new Multi-View feature lets you arrange multiple windows as layered panels without overlap, creating a flexible, clutter-free workspace. We have an amazing new “AI-Notes” feature. This transcribes polyphonic audio into MIDI so you can view it in notation or play it back as MIDI. You can process an entire track (all pitched instruments and drums) or focus on individual parts like drums, bass, guitars/piano, or vocals. There's an amazing collection of new content too, including 202 RealTracks, new RealStyles, MIDI SuperTracks, Instrumental Studies, “Songs with Vocals” Artist Performance Sets, Playable RealTracks Set 5, two RealDrums Stems sets, XPro Styles PAK 10, Xtra Styles PAK 21, and much more!
There are over 100 new features in Band-in-a-Box® 2026 for Windows®.
When you order purchase Band-in-a-Box® 2026 before 11:59 PM PST on January 15th, you'll also receive a Free Bonus PAK packed with exciting new add-ons.
Upgrade to Band-in-a-Box® 2026 for Windows® today! Check out the Band-in-a-Box® packages page for all the purchase options available.
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