UI freezes with "Export Mixdown" after installing Fender Studio Pro 8

[Bruh]

Since installing Fender Studio Pro 8, I’m seeing a reproducible freeze in Studio One on Windows.

After exporting larger sessions, Studio One finishes the export and opens the target folder in Explorer — but then the GUI becomes completely unresponsive (export modal seems not released). The app isn’t crashed (CPU/RAM still active, even autosaves), but the UI thread is blocked and only Task Manager can close it.

Smaller exports often work. Happens across Studio One 6 / 7 / Pro 8. Not plugin-specific.

Important clue: while Studio One is stuck and Explorer is open, I cannot drag & drop the exported WAV from that specific folder window into RX or other apps. The moment I kill Studio One, drag & drop works again — which strongly suggests a Windows Shell / OLE deadlock triggered by opening Explorer. It also works if I open the folder from a second explorer window.

Another observation: exports that only take a few seconds usually work, regardless of plugin count. It seems more related to how long the export runs — the longer it takes, the more likely the freeze becomes, possibly because it gives background sync/shell processes time to kick in. (But this is just a guess)

What I already tried / ruled out:

• Happens across multiple Studio One versions
• Reinstalled all Studio One versions
• Not plugin-specific
• Not admin rights (normally non-elevated; also tested elevated, same result)
• Fresh Windows user account (no pCloud / background apps) → still freezes
• Fully uninstalled pCloud after a recent update
• Disabled non-Microsoft shell extensions
• No recent Windows Updates

Only recent system changes:

• Fender Studio Pro install broke VEGAS 21 → forced VC++ redistributable reinstall
• pCloud update shortly before this started

At this point it looks like a system-level shell interaction issue rather than a Studio One project or plugin problem.

Has anyone else seen this behavior or found a fix? Right now, it is literally blocking my work and I am thankful for any suggestion.

Thread based on:

Fender Studio Pro 8 - Discussion Thread

My point is, it is very typical that when one company buys another, they start screwing with the original product that was working just fine and eventually it stops working to the satisfaction of many of the original loyal customers who end up with a product that they don't want! Where - does...

studiooneforum.com

Previous conversation:

Anyone else has problems with freezes with "Export Mixdown" after installing Fender Studio Pro 8?

On Windows: After exporting larger sessions, Studio Pro finishes the export and opens the target folder in Explorer, but then the GUI becomes completely unresponsive (export modal seems not released). App isn’t crashed (CPU/RAM still active, even autosaves), but UI thread is blocked and only Task Manager can close it.

Smaller exports often work. Happens across S1 6/7/Pro 8. Not plugin-specific.

Extra clue: While Studio One is stuck and Explorer is open, I cannot drag & drop the exported WAV into RX or other apps. The moment I kill Studio One, drag & drop works again → looks like a Shell/OLE deadlock after opening Explorer.

Only recent system changes: Fender Studio Pro install broke VEGAS Pro 21, so I had to reinstall/update VC++ redistributables. No recent Windows Updates.

Did anyone else see this or find a fix?

Quick check, are you running any of your apps as administrator, if so,.don't.

By default, neither Studio One nor RX are running elevated on my system. I also tested running Studio One as administrator, but the issue still occurs.

Never run as administrator, unless you have some issue authorising legacy plugins (and only temporarily).

Anyway thanks for clarification.

Drag and drop issues like you specifically explained often points to a permissions issue.

You might try creating a new basic user account and seeing if it works from there. Another thing to try is full reinstall of all the applications you are using which will hopefully refresh file permissions.

 

[Number6]

Please update your hardware and software specs on your signature, Inc your graphic card.

Please confirm windows update is fully up to date.

Please run windows update right now, and install everything outdated. Microsoft has released an emergency update/hotfix very recently, as stuff was broken on patch Tuesday (quite unusual).

Backup before if you like.

For fun also update your display drivers.

 

[Bruh]

Please update your hardware and software specs on your signature, Inc your graphic card.

Please confirm windows update is fully up to date.

Please run windows update right now, and install everything outdated. Microsoft has released an emergency update/hotfix very recently, as stuff was broken on patch Tuesday (quite unusual).

Backup before if you like.

For fun also update your display drivers.

I updated my signature. Right now, everything is up to date.

Edit:
I’ve started migrating my current project to Pro Tools and will finish it there until this issue is resolved.

 

[Number6]

Ok I played around on Studio Pro today and saw no issues like that, which of course is no help to you. Maybe others will chip in.

 

[Bruh]

Today Studio Pro 8 somehow fixed itself, and I was able to work as usual without any crashes. Maybe it got scared of being replaced, since I’m getting faster and faster in Pro Tools.

But seriously, I’m insanely happy to be back in my favorite DAW. Takes-to-layers recording and multilayer comping, without having to select and duplicate any “playlists.” Comping without fiddling around.

And on top of that, Pro Tools only allows one ARA plugin per track. So if a clip already has Melodyne on it, you can’t put DynAssist on another clip on the same track. Constantly annoying.

Okay, sorry for the short rant. ^^

 

[Number6]

You upgraded to 8.0.1 I assume.

 

[Bruh]

You upgraded to 8.0.1 I assume.

Yes, I did, but the bug wasn’t even listed in the changelog. It might just be a coincidence. Anyway.