Internal error at projectwindows.cpp line 75 20 Mar 25

I think this may be a bug but unsure. I’m aware that an update has been released recently but skipped past this as I was running low on battery and needed to make a few tweaks to the project while I remembered. Laptop has since been charged and after moving my unfinished project over to my usb just for sakekeeping and opening to check everything was okay (it lagged, stopped responding, and then said the disk was full [possibly being very stupid here as I’m not techy, but the usb has like 80% more capacity - this can’t be the disk, right?]). So, went back to the original file and tried to open it.

I now can’t get into the file, it just keeps giving me this internal error code. What can I do without losing all of my work?

This is very time-sensitive.

  1. Audacity doesn’t work very well on USB drives.
  2. Every time you make an edit, you increase the size of the project file by the size of the original audio source, which would use up a USB very quickly.

Resolved.

Noted, I’ll just save the finished copy to the USB in that case and make sure to only edit the original file. I just don’t understand why it had a full on tantrum with me when I did try to access the original file after the full-disk comment and it blocked all access – even to the actual software. All the crash reports from the software and individual file constantly bounced back anyway. I feel like the other half of a woman scorned because it’s working perfectly fine now after I let the laptop sleep and charge. Maybe she was hangry, who knows. All I know is my girl ain’t mad at me anymore and I’m still none the wiser to why all around. My life story.

It sounds like there may have been an issue with the transfer or file corruption. First, try opening the file directly from your original location (not the USB). If that doesn’t work, copy it back from the USB to your laptop and attempt to open it again. You could also try opening it on another device or with a different program. If you’re still getting the error, checking for updates or running a disk check might help. Let me know what error code you’re seeing—I’ll try to assist further.

This topic was automatically closed after 30 days. New replies are no longer allowed.