Any idea how to fix this Exception Error?
2022 worked OK but now for 2023 it says I can continue working but may not (?) save it.
See screenshot attached
I tried sending the error report to PG but I can't get the click tab that sends it to latch.
Bests
Ian

I've had this in the past and found I could ignore it. Not had it with 2023 yet

I'd email that error screenshot to support@ as an attachment then.
It goes to the same place I'd think

//I have not experienced this error
///permissions on the folder maybe?

I don't recognise the small print but when I got the error msg I found I could simply continue as usual

Mine's a total crash and have to use Task Manager to close it down.
I've sent the details to Support.
It has to be some weird anomaly as RB works fine in my Win10. Its the Win7 drive DL that isn't working.
Bests
Ian

Do you know how to duplicate this? Can you get the crash to happen on your Windows 7 computer by doing something specific?

Hi Andrew
Note - I sent the info off crash log (?) to Tech Support.
Basically I start up RB2023 Build 2 (current) via desktop icon as usual. I get the No-No message come up and nothing works. It won't let me close it down - I have to use Task Manager.
Hope that helps.
Bests
Ian

Does the file C:\RealBand\Data\BootupLog.txt exist ?

What about C:\RealBand\Data\FlashMessageLog.txt ?

Andrew
Both files are there BUT WITHOUT the .txt.
Should I rename them?
Bests
Ian

The file extensions are just hidden on your system. With RealBand closed, try deleting BootupLog, and see what happens. If it is deleted successfully, run RealBand again and see if the same error happens.

Seems odd the originally posted error shows the error in C:Realband\
instead of
C:\Realband_X64\ folder (for both where the error occurred and the application that caused the error)

Just noticing ..
Are you sure you are launching the new RB?
The error (to me) implies you are actually launching an older version

This gets curiouser and curiouser..
Andrew - i deleted that bootlog file and RB then fires up. However, an SGU opened thus pays zero attention to any of the F5 commands within it.
If I then shut down the PC and restart it, the boot up problem returns - and round and round we go.

Strange thing - I think Rharv may be on to something - the opening Splash screen says 2023 build 2 and so does the 'about' menu. BUT if I look at Activated Tickets it only shows up to 2020. Nothing for 2021, 2022 or this new update.
So, could RB actually be trying to work as 2020 not 2023?

No idea why that should be.

What would be the best and safest way of reinstalling RB completely afresh without disturhing a working fine BB2023?
Bests
Ian

Yes, that would be strange.

Do you have a Realband_X64 folder on that C: drive?
It could be an errant error message I suppose, but exception errors are usually pretty accurate about what happened and in which application.

RealBand 2020 and earlier used a separate activation from Band-in-a-Box so there is nothing abnormal about that.
To reinstall you could delete the RealBand folder, then run the Band-in-a-Box and RealBand installer, and uncheck all components except RealBand.

Would he need to delete (or rename) the Realband folder and the Realband_X64 folder as well?

There is no RealBand_x64 folder. That must be something you created. RealBand64.exe is included in the RealBand folder.

Resolved after advice from Tech Support (thanks Chantelle/Jerry) to delete the RealBand folder entirely and reinstall that folder only.
It worked. No crash.
Many thanks
Ian

Ian. (from a fellow english bloke).

just wanted to say your guitar playing never ceases to amaze me.
imho pg should hire you to do guitar real tracks.

its not just your guitar sound but also the 'taste' you display.
knocks me out.

let me say also ive seen/heard some very talented session guitarists wield their mojo in studios and you are right up there with the best imho.
you should be in the shads

have a fantastic 2023 ian.

om