Non-primary windows disappear after exporting in 23.5

"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?

I've worked with four monitors for years in Premiere. On a PC ... and have never had this happen. It isn't all that common across the several million daily users.

For those who have it, it is a ROYAL pain, no question. And I've been there/done that with other things over the years.

I do hope they get this sorted, but the first part required for fixing something is being able to replicate it. As they can't, they can't fix what they can't find. Which is why data from the users having something is so crucial to a timely fix.

Hey Kevin, this issue has been ongoing for months now. I've tried numerous attempts to work with Adobe on this and their troubleshooting has always been the same steps over and over. None of which have ever solved the issue. This is ultimately a bug on Adobe's part and a wider issue when using dual monitors, which is almost every editor's setup. A lot of industry folk and major networks are using Premiere everyday. This really needs to be addressed, so Adobe doesn't go the way of Final Cut and lose customers. By the way, thanks for the quick response.    

Actually, I don't think this is a matter of reproducing the issue. I honestly think it's leaning towards good will or lack of competence. There are numerous comments describing the issue, several videos showing what's going on. But the thing is: The costumers are still paying us every month despite the problems. Why should we bother? But you see, this is a dangerous territory. DaVinci Resolve is getting better by the day, and we only have to pay for it one time. Have you ever asked yourselves why the costumers keeps paying you every month? Maybe this is a question that needs an urgent answer because maybe we are getting tired of excuses... Maybe we're getting tired of losing our time to find workarounds for problems that weren't created by us. 

The problem is actually pretty simple. Just read every comment and see every video, paying attention, and your develop team will find a solution. Deflecting, isn't taking you anywhere. The only thing that is happening is that your subscribers are getting tired. Adobe isn't the only company in the world.

Hello Community,

I'm sorry that some of you are still experiencing this bug. As you've read, the devs cannot reproduce the issue.

If you have time, please message @jstrawn  and work with him one-on-one to resolve this issue.

I'm sorry that the community's information and screen movies have not been enough to reproduce this issue on our side.

Sorry for the frustration.

Thanks,
Kevin

I can confim this is still happening in 2024. I work for a telvision network and this has been a huge pain to deal with. I've had numerous chat sessions with Adobe and it still hasn't been resolved. They've done everything from reinstall Premiere to clean out all my internal folders in windows. Everytime this happens now I have to switch between workspaces to bring back the timeline. I really don't know what else to do it this point and it doesn't seem like Adobe is ever going to properly address the problem.

Soz i forget about may be an important thing... Before all of stuff that i described i was disabled the windows taskbar on second monitor. Leave it only on first monitor.

I don't think the pixel creep is the issue, as I have a pretty clear margin dividing my second window and the edge of the monitor and it's still having the same issue. Sometimes it disappears after using the export window, sometimes it doesn't. I cannot see any differences in the way I'm approaching it.

Sounds like "pixel creep" ... it's been a problem for some time. 

Because if you create a panel group on a second/third/fourth screen, and one line of pixels is actually "on" another monitor's space ... which you often can's see due to the bezels ... madness ensues.

I work on four monitors, and make sure that the panel groups of my custom workspaces are built with a thin line of monitor background showing around all four edges. I wish they'd make this a more modern UI but ... ah well.