Unable to save a corrupted project

It’s the classic:

The project could not be saved, because:
The project is corrupted!
The previous version of the project has been left unchanged.

I know this happens now and then, but now I have a situation where I can’t even save a new project under a new name (“No new project could be created”).

I also can’t seem to get the import tracks into a new project to work as any media files do not seem to carry over.

I can’t even save a new backup of the project.

(To add more insult to injury, it asks me whether I should save when I close it.)

If push comes to shove, I guess I have to manually do whatever changes I wanted to have saved every time I open up that project.

I’d be looking to make sure a disk wasn’t going bad.

1 Like

And if you try to open the most recent bak file and create a new version from it?

Did several scans and in the middle of a chkdsk /r as we speak. So far, so good. Other files seem to be fine.

I normally delete the backup files just to decluter/save space. But even if I did, I don’t think I would have had a more recent backup to use. (Good point though.)

This is no help for the OP, but…
I have a gaming mouse, which, among other things, has app-aware programmable buttons. There is a button betwixt the (left and right buttons) which I have assigned to ctrl+S. I click this every 3 or 4 edits, whatever the edits are.
I also delete bak files, but I also do a ctrl+alt+S save every half-hour or so. By the time a project is finished I could have 80 or 90 indexed backups, most of which get deleted, once I’m happy with the results.
Bottom line - I’m never more than a couple of minutes away from the last save Galling as it may be, I can afford a couple of minutes lost work.
Adopted this method for similar reasons as the OP, in other programs, as well as Cubase.

can you try to disable all plugins and save?

Well, the bak files are there to save you, so deleting them It is not a good practice. Let at least the most recent bak file (they are small, why delete?).

Agree. I have a Windows script that sets all the .bak files to be ‘hidden’. It runs at Windows startup, so the only .bak files I see are the ones created while working that day - which happens to be the only .bak files I’m likely to need.

Just to get the known cause for such behavior checked: Was your last saved project file of this project anywhere close to being 2GBytes in size?

My computer, my choice, and yes I live with the consequences

It’s definitely not that because of the project size (it’s 7.69 MB) and I know that was an issue in general.

Can you please let us know your OS with version number and your edition and version of Cubase?

I like to ping @Armand as I think this is a most serious issue. If Cubase can prevent you from saving your project and therefore make you lose all your work done since the last succesful save why would anybody, who relies on Cubase for making a living, trust this software?


Hi everyone,

Sorry to hear about your issue. I am no longer on the Sequencer project until further notice. Therefore thank you for not mentioning my name for anything related to this matter as I will not be able to address it as I used to be. I have informed the relevant persons nonetheless.

Crossing my fingers…



Cubase Pro 13.0.30. Windows 11 Home - 21H2

So even importing the tracks into a new project - and I finally got that one to work for me - will not allow me to save the new project because it’s corrupted.

Auto Save also fails, but that was implied.

Do you have another computer you can install Cubase on, or a friend who also uses it. I wonder if the Track Importing might work on a different computer.