What is going on with Studio One v7.2.3 - just opened it and ALL settings have been wiped???

[Vocalpoint]

All

Early this morning - I was simply a spectator - chiming in on a few posts where a user was saying his Studio One V7 layout had complete reverted to a default install.

5 mins ago - I am getting the same thing. Just fired up S1 v7.23 to see this:

Which I know is never a good thing. So I did not Accept or Decline - just hit the X in the upper right

Then - I immediately went to the Studio One v7 AppDate folder and saw this:

As barebones as it gets. Everything - gone

Luckily - a backup ran this morning at 8:45am - preserving my last known good v7 state - which is this:

Does anyone have ANY idea just what is going on here? This is Danger with a capitol "D" for anyone who is unprepared.

Might need to contact support as well - as this is a disaster.

VP

 

[lokeyfly]

TY for the heads-up, VP.
I had no issue this morning editing in a few songs. I will back up though, hearing this. What the ____!
You're one that covers all the precautions.

I lIve close to Baton Rouge now, so if you need me to roll some heads, I will.

 

[Vocalpoint]

Yeah - just chatted with a few Presonus/Fender resources on the FB group - apparently - this CAN happen.

Been told that your config can suddenly get "corrupted" (reasons unknown) and this is the default action. Was also told it is NOT a bug.

Not sure how to feel about that explanation - but I am VERY glad I have daily imaging going on.

Was able to restore the directory from last nights backup and all good now.

VP

 

[parityflux]

IMO this should never happen. I write software. This is bullshit.
-j

 

[Vocalpoint]

The language in your post aside - I do agree.

This a major oversight - if the only solution to a "supposed" (unknown/unannounced/unplanned) "corruption" problem is to ice the entire installation - including the ENTIRE set of application files, customizations - basically anything a guy need to run Studio One/SP and present to user with an empty config - is about as ridiculous a solution as I can fathom.

The user gets no chance to do anything - except watch their entire installation directory disappear and have the app starts over as if it has never been run - ever.

This needs an explanation at multiple levels - especially for whoever decided this "recovery" (and I use that term VERY lightly) method has any value in any way.

Would like to get some insight from Arne Kaiser or Lukas or Ari or anyone who is closer to the development bench than we are.

VP

 

[Stuart Welwood]

MO this should never happen.

I'm a retired software engineer, and I agree. Destruction of user data is considered to be one of the biggest no-nos in software development. Inexcusable IMNSHO.

 

[Craig Anderton]

Does anyone know whether this can affect FSP8 as well?

 

[Vocalpoint]

Does anyone know whether this can affect FSP8 as well?

Until someone can explain why I saw i in the first place in S1v7 - I would have to assume it can (and will) occur in SPv8 as well.

VP

 

[parityflux]

Hey,
Apologies for my small outburst. I can do better with prose than that.

I will be taking note and writing some scripts to backup and restore my settings to hedge against any future corruptions. I had done this with S6, but S7 was working so well I didn't bother. I'll do it for both S7 and FSP8. I mentioned the issue to support (inside another ticket) and they asked me to copy my "settings" from FSP8 to S7. I was a little skeptical but gave it a shot since my S7 settings were toast. I used the Win path %USERPROFILE%\AppData\Roaming\Fender\Studio Pro 8 to copy from. It largely worked, with a bit of barking about being unable to use the FSP8 manual and resetting the license again (blank slate like the OP). It was also only effective because the initial FSP8 installation migrated my S7 settings. My devices were there and that's really the biggest relief.
-j

 

[lokeyfly]

The user gets no chance to do anything - except watch their entire installation directory disappear and have the app starts over as if it has never been run - ever.

This needs an explanation at multiple levels - especially for whoever decided this "recovery" (and I use that term VERY lightly) method has any value in any way.

Would like to get some insight from Arne Kaiser or Lukas or Ari or anyone who is closer to the development bench than we are.

VP

I think the current head count is one or two on this issue?
Would be great to hear an immediate response.
They might ask you VP for your songs path, and such before providing a fix. Dunno.

 

[ennbr]

There are quite a few people having this problem we just don't spend time posting or talking about it
Saving the folder is a simple fix
I've been seeing this happen for years now not often but it happens since v5 from what I recall

I wish the developers would fix whatever is getting corrupted without whipping the folder
taking the shotgun approach to fixing this is not the answer but I don't expect it will ever be addressed
so i'll just save the folder and put it back whenever this happens

 

[Vocalpoint]

I wrote a very deep backup routine using SyncBack Pro - years ago and it saved my bacon - again.

I make sure this thing runs at 5:40am every day - to ensure I have a valid set of system files before starting any day of activity.

VP

 

[lokeyfly]

There are quite a few people having this problem we just don't spend time posting or talking about it

That I havent seen, and it would likely be a huge flash if it were. I suspect its cropping up in some early cases. Yet, I dont see this issue elsewhere (as noted, here).

Saving the folder is a simple fix

Yep, what I do all the time.

I've been seeing this happen for years now not often but it happens since v5 from what I recall

What ends up "missing" is when people often relocate a song or folder.

what has my concern here is that Vocalpoint knows this, and wouldn't comment on it unless it was valid.

I wish the developers would fix whatever is getting corrupted without whipping the folder
taking the shotgun approach to fixing this is not the answer but I don't expect it will ever be addressed
so i'll just save the folder and put it back whenever this happens

How much developers can fix a corrupted folder doesnt seem possible, unless the re write or override write process itself were currupt. Only, I've personally not ever encountered that.

Which is why as VP mentions, I'd like to see some official response towards this. Until then, lets see.

 

[Vocalpoint]

What has my concern here is that Vocalpoint knows this, and wouldn't comment on it unless it was valid.

While I certainly do not claim to know everything - I know enough. And there is no concept of a "corrupted" folder on this machine.

Whatever caused this - is not a corrupted folder. And without an official explanation as to why any version of Studio One/Pro would have any "smarts" or capability to suddenly decide it's a good time to delete it's entire working folder set (with no warning, backup or any failsafe) and then inexplicably replace everything with new (blank) files - is really beyond me.

This explanation sounds like simply a convenient "out" at this point. AS in - no one has any idea what is going on here.

VP

 

[lokeyfly]

While I certainly do not claim to know everything - I know enough. And there is no concept of a "corrupted" folder on this machine.

Yep, we've spoke on various lost files claims on numerous occasions when helping those wondering why they have lost files. Of course, a different issue. So your posting on this occurrence got my attention. This is therefore a real matter that should be cleared up, once understood.

My comments to ennbr is that I'm not so sure how deep across the pond this issue is, and to deem something as "seeing this for years now" doesn't float well with me. I havent, and that type of blanket statement is what goes on in those extremely vague discussion forums, such as Facebook. Here, (and the old Presonus forum), we are better than that.

I surely am glad you're bringing it to the forefront, though.

Whatever caused this - is not a corrupted folder.

yes, agree.

And without an official explanation as to why any version of Studio One/Pro would have any "smarts" or capability to suddenly decide it's a good time to delete it's entire working folder set (with no warning, backup or any failsafe) and then inexplicably replace everything with new (blank) files - is really beyond me.

Bizzaro (agreed)

This explanation sounds like simply a convenient "out" at this point. AS in - no one has any idea what is going on here.

VP

A response would be helpful Only it has to be understood on their end. Heck, even a "we are looking into it, so until further notice...." would be nice.
Let's see.

 

[ennbr]

The folder is not corrupted however there is a file in the folder that has been corrupted

Sadly the developers fix for a single corrupted file is to delete and recreate the folder

 

[Vocalpoint]

The folder is not corrupted however there is a file in the folder that has been corrupted.

I guess I would need to understand how the system knows this and how it got this way.

Espeically since in my case - I had v7 open and working for hundreds of days previous.

All of a sudden - something is corrupt? Sorry - not buying it.

VP

 

[parityflux]

I've been using this software series since v3 and haven't seen a full wipe of user data until now. I had corruption issue in v6 after memory crashes which I used to get often when using a lot of sample libraries. Most of the time that particular corruption I could assign to settings not being closed out due to the crash (in v5/v6 and probably even v8, a lot of settings aren't saved until the program properly closes).

For the current problem, there isn't an obvious way that anything could have gotten corrupted. I was using SO7 and one clear sunny day I installed SP8 and I did a few minor projects. I went back to SO7 3 months later (this very first time last week) to check on some plugin settings that I couldn't find and SO7 had reset itself. All settings gone: devices, presets, artist info, all of the audio and midi settings. There was no compelling reason for it. No interim software changes or anything like that. Only 3 windows updates since installing SP8: KB5081277, KB5086096 and KB5093447.

 

[Vocalpoint]

I was using SO7 and one clear sunny day I installed SP8 and I did a few minor projects. I went back to SO7 3 months later (this very first time last week) to check on some plugin settings that I couldn't find and SO7 had reset itself.

And I was running S1v7.2.3 (since release day) and last used it approximately 11 hours before I opened it again - only to find myself trapped into a "clean" (non-escapable) install. I too installed SPv8 - but that was back on Jan 20, 2026.

No Windows updates were installed here as that process is tightly controlled - the OS has no say whatsoever when it gets updates - all update mechanisms are disabled.

These two were playing nice for months. Until they weren't

VP

 

[MisterE]

Vocalpoint, have you ruled out mischief following a Win10 update? You're on the borrowed time version, as am I. I haven't been recording recently, but I have noticed a couple of things happening on my PC that are somewhat different, although nothing near as alarming as losing all customization. More like spinning hands of time on movies...which Spectrum said is happening to users on the borrowed time Win10. Not saying this is the cause, but am saying you probably do want to rule it out.