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

[parityflux]

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.

I dig your style, man.

 

[Vocalpoint]

Vocalpoint, have you ruled out mischief following a Win10 update? You're on the borrowed time version, as am I.

As noted in the post prior to yours - I am running WIndows 10 - yes. With Extended Updates - Yes.

However - group policy here does not permit any workstation to engage in what I would call the "normal" Windows update process. Windows Update is fully disabled on all machines.

Example: Here is a screencap from the machine I am typing on - you can't even click Check for Updates here (It is greyed out and disabled):

WU is so disabled that even the "last check" as above (and the one and only time I ever clicked on "Check for Updates) - was on 2/8/2025 when I installed this workstation to bare metal (1).

Now - of course - Windows Updates DO occur - but via Powershell scripting and via a schedule that I created (and control).

The scripts run - when they are scheduled to run - not when MS releases updates (like Patch Tuesday for example)

In this case - and the day this bizarre reset occurred - there were no updates scheduled for deployment to any machine.

VP

 

[MisterE]

As noted in the post prior to yours - I am running WIndows 10 - yes. With Extended Updates - Yes.

However - group policy here does not permit any workstation to engage in what I would call the "normal" Windows update process. Windows Update is fully disabled on all machines.

Example: Here is a screencap from the machine I am typing on - you can't even click Check for Updates here (It is greyed out and disabled):

View attachment 3501

WU is so disabled that even the "last check" as above (and the one and only time I ever clicked on "Check for Updates) - was on 2/8/2025 when I installed this workstation to bare metal (1).

Now - of course - Windows Updates DO occur - but via Powershell scripting and via a schedule that I created (and control).

The scripts run - when they are scheduled to run - not when MS releases updates (like Patch Tuesday for example)

In this case - and the day this bizarre reset occurred - there were no updates scheduled for deployment to any machine.

VP

K, you just checked off one troubleshooting point.

 

[TonalDynamics]

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

Just here for our obligatory 'OLD software is STABLE software' saw, VP. Haha.

I'll probably use 6.6.4 for the next ten years like those guys who made hit records with portastudios back in the day (I hope).

Believe me, I WISH it weren't so! I love new features generally.
Entropy is not to be mocked however... especially in the 'vibe-coding' era.
The more points of failure in a given system, the more failures will present within that system proportional to the QA intensity.
It's simply a cumulative expression of Murphy's Law. Boeing and Lockeed for example have tons of components, but they are only rock solid due to redundancies and relentless QA testing.

I'm not remotely suggesting S1v7 had any of that whatsoever btw, but in general with brands the world over trying to automate away crucial software dev jobs it remains a vital point.


Half the software from the last few years honestly makes me feel like it was hardly beta-tested at all anymore.