Non-primary windows disappear after exporting in 23.5

I don't understand
each of us pays adobe monthly to receive the programs
This discussion began at least in June 2023
In a couple more months it will be a year
and Adobe still can't solve this?
Adobe can run a script in the program that closes and opens the project after exporting
or have the script run control alt 0
to reset the workspace
but why continue suffering and work unprofessionally?
Isn't it time to put the engineers to work on some of these basic solutions?

Very annoying. The only way for me to go back to my workspace is to exit and then open the program again.

@engineeringfilmmaker Thank you for taking the time to report this. The problem you described is the same as on we've been hearing from some users for a while. So I'm merging your post into the existing one so that we can hopefully work together to find a common repro case that could lead to a fix for the root problem.

Last thing first ...

"Please delete that useless import and export mode windows. The whole community will thank you for that.

Not ... hardly. You'd have a lot of people howling over removing that Import page at this time.  As rather a lot of users, including many high end professionals, use that import page heavily and love it, for certain things. Even though many of us don't use it at all.

On the Facebook pro editors group, I just learned that it actually is one of the more solid ways of importing additional spanned footage to a current project. Which has always been a MediaBrowser panel thing only, right? Yea ... so a lot of folks using spanned media are now very into that Import page. Because it actually can be faster and just as good to flip to the import page for heavy spanned media.

Huh. Learn something every day, right?

As to your issue: I'm one of those, btw, who's been arguing their entire UI relationship with monitors needs to be rebuilt from the ground up. It's so 1994 ... rather than based on the physical monitors, it's really seems to be coded more by relative relationship to the upper left pixel, of whichever the OS thinks is the "main" monitor. Most everything other pixel is calculated from that pixel, something like "+1080-1920" or something like that.  And it all goes wonky if the 'main' Pr window, with the top menu system, isn't on that 'main' monitor. Or if the Program monitor is moved to a different screen than the main window. And other things.

As to that issue you're having, where panels can flipping disappear ... yea, agreed that's annoying.  And you have all my sympathy too. As ... there are some annoying things with color processes especially using control surfaces. Which ... in general ... is a ton better in Premiere than in Resolve, as BlackMagic barely allows non-BM kit to function and you can't change their intentionally limited mappings.

That said ... there' some things that are clearly 'bug' behavior, but as they affect only a very few users, I've been told (very politely) that ... realistically ... even though it's acknowledged, fixing a couple issues high on my list is gonna be so low on any user-requested dev's list, that it might just be a long, long time before they get to a couple things. As in a ... LONG ... time.

Annoying? Oh Hades, yes. But actually, I do understand the reasoning on the prioritization of dev's time. Sadly, for me, but ... Life is what it is. And I've had to be practical about working through the annoyances. 

All this to say, I live with, to me, a painful issue, but recognize most of you don't give crud about my painful issue, because ... it doesn't affect you at freaking all. Which is totally normal human behavior. Right?

Your issue affects undoubtedly more than mine does. Thankfully for you! 

But ... most users hit by this have found practical ways around at least some of the annoyance. Typically by changing their custom workspaces and panel practices some.

I think "we" can find a way to at least mitigate most of the pain. As that's probably the most practical suggestion at this time.

And as thee and me can't change the devs work schedules. at least, for practical use, we users can probably help you find a less annoying way to get around this. IF we know enough about how you setup your monitors in the OS, and how you use panels in Premiere.

And again ... I totally want the devs to rebuild the entire monitor using UI ... please Dear Deity, please?

One year and several versions later, same problem persist on CC2024.

When i send my timeline to media enconder to export, whatever premiere window i have on my second screen just disapear when the export mode window is enabled.

The only way to bring it back is pressing Alt + shift + 0 (Window>Workspace>Reset Current Workspace).

Reseting my workspace whenever i'm exporting anything IT'S A WASTE OF TIME.

Please delete that useless import and export mode windows. The whole community will thank you for that.

Hello Adobe / Jstrawn, since around one year we also experience this problem, on several Windows 10 computers.

Our workaround was always closing Premiere after export, and restarting. Or changing workspaces.

And hoping for an update.

Now with Premiere 2024 we're still experiencing the problem, and I came across this topic.

We also recreated the problem by starting a new Premiere project, creating a timelime, assets, and exporting it.

YouTube link: https://youtu.be/Jvhrh9jmZsk

In this example, the first export at timecode 1:50 doesn't have the problem. But at the second export, at 2:20, the second screen stays away. At 3:50 and 4:30 the problem also happens.

Is there a fix on the way?

Kind regards, Joren

@gideonmuzy Sadly that doesn't work, the only thing that fixes it is to switch to another workspace and then back. It's almost like the program forgets I have a second window at all so any changes to the workspace is like "Oh, well that doesn't exist so I didn't do anything". The only thing that works is swapping workspaces or restarting the program. 

di you try ctrl+shift+0  ??

is no the big solution but reset your workspace

@jstrawn Go for it, anything that can help this annoying bug bite the dust is a positive.

@KarthXLR That video was a decent documentation of what you saw, although it was a little hard to follow exactly what you were doing the whole time. More importantly, it did not give me any clues to what, if any, steps I can take to make that happen on my own systems.
@R Neil Haugen  here is a video of the problem happening on Karth's system:
https://www.youtube.com/watch?v=CY57RAwMuwI