Non-primary windows disappear after exporting in 23.5

As of 10/15/24 I'm still having the problem as well.

Iv'e also meesage the recommended rep here with no response.

What can't they replicate? There's several other users that are having the exact same issue and I've even been on with Adobe reps who have seen it. It would be different if I was the only one this is happening too.

I have run at least three, normally four monitors in Premiere for a decade now. I've never had this. I know the devs are having a devil of a time replicating it in-house.

So ... it's a pretty small percentage of the users getting this, and yea, it's gonna be annoying as Hades if that's you. But it's not because they don't care, it's just they can't replicate.

What you can't replicate, you can't fix. 

What's even crazier is they just releasead the 2025 update and the issue still persisits. At this point, I don't think Adobe cares to address the problem and all of us having to deal with it are out of luck.

Oh by no means is it a fix, but the OP was talking about relaunching the program. This is merely annoyance mitigation.

I replied to @jstrawn but still have no reply. I'm still dealing with this same issue almost a year later and control, shift 0 is not a fix. It's reseting workspace which only gets rid of the problem, until you have to export again. Could someone please reach out to me from Adobe?

Still present in 24.6.1 October 2024.

Alt+Shift+0 (Windows) / Opt+Shift+) (Mac) is a quick shortcutr to reset windows to your saved layout but it is annoying.

"Adobe" can speak for itself. I know and like some of the staffers, but I don't care pigs about corporations per se.

Personally, I've known Kevin for years. He's long experienced as an editor and colorist prior to working for Adobe. And has been tireless advocating for users in his time with that firm. His knowledge and advice are worth listening to in professional workflows. 

Apparently, you may not have great knowledge of software versus hardware these days. There is absolutely no way to guarantee that any software will work perfectly on all systems with all media and workflows across several million daily users. It's an absurd thought even.

And yes, "local" things can jump up that the devs don't ever see. Such as the infamous onedrive.dll incident a few years back.

Some of us started get really weird behaviors, and couldn't work at all. For about a month or two, there were a ton of posts here ... and I was one of the ones who spent most of that time trying to help troubleshoot meaning asking detailed questions. You have to find the differences between no-problem and problem, of course.

But then a couple weeks in, my system went nuts if I tried to use Premiere. And one amazing, wondrous, awesome user finally went through his system and started one by one deleting those dll "library" files in Windows. There's a few thousand or so, rather a daunting task. All required for operation of one program or another.

He'd delete a dll, reboot, check it was still gone, then launch Premiere. Over and over.

He was working alphabetically, and of course, hand-writing each dll as he removed it. Around several hundred dll's later, he got to onedrive.dll, rebooted, launched Premiere ... and it was working fine.

So he came are reported that on this forum. Like many others, I immediately deleted onedrive.dll, and voila! ... functional Premiere again.

I don't think anyone ever figured out why this was an issue for maybe at most 1% of the PCs with onedrive.dll on them. Or why that would be fine for weeks, as with my computer, then one day, bork me too.

Because on the vast majority of Windows PCs, onedrive.dll was never a problem.

And this is why I often get mad with Adobe's team. It's much easier to blame a random thing than to try to find a satisfying answer.

I'll tell why your answer is completely faulty. My Premiere Pro was working just fine until the day you released an update and from that day forward everything went to hell. I think I don't need to point out that updating a software doesn't cause misalignment in hardware. And if it is a driver thing I also don't think I need to say that it is also your fault. Your comment would make sense if I had replace something on my hardware or if I had replaced my pc. It's not the case! 

So once again we're back to square one. And your customers are here saying to Adobe: We need this fixed ASAP! Or you can freeze my payment until the day this bug gets fixed. How about that?