Skip to main content
Adobe Photoshop Family

32 Messages

 • 

702 Points

Fri, Oct 23, 2015 5:07 AM

Solved

Photoshop: Don't open an annoying Explorer window after "Quick export as PNG"

When I use "quick export as PNG", it saves the file, but then opens a file explorer window for some reason. No other save-as/export feature in PS or anything else does this in Windows. Maybe this was implemented by an OSX developer (some applications do this there), but this is really annoying in Windows.

Responses

Official Solution

Adobe Administrator

 • 

14.9K Messages

 • 

286.1K Points

4 years ago

An Explorer/Finder window will no longer pop open after quick export in CC 2017: http://blogs.adobe.com/photoshop/2016/11/keep-creating-a-guided-tour-through-the-latest-photoshop-updates.html

Sr. Product Manager, Adobe Digital Imaging

7 Messages

 • 

160 Points

5 years ago

Exactly! Additionally, upon some experimentation, I believe this is the cause for Quick Export as PNG not working in Actions.

Details: As already reported the now Quick Export and Export As in Photohop CC 2015 cannot be used in Actions. I have found that Quick Export can be used in Actions IF it is the last item. If you put any other item after that it will not perform the Quick Export. I have now come to believe it is because the Quick Export is trying to change focus and open an Explorer window and having another action triggering at the same time causes the failure.

Fix would be to NOT OPEN THE EXTERNAL WINDOW. I would like to have Quick Export in an action but I need an additional step after it.

10 Messages

 • 

172 Points

5 years ago

Bump this topic. Really annoying.

1 Message

 • 

60 Points

5 years ago

@LeKoArts?? 

The annoying behavior of PS CC needs to be resolved. Someone has a fix? 

22 Messages

 • 

316 Points

4 years ago

Fix this please! :'( it's annoying! When I open PS for one session, and hit quick export PNG, it opens the folder where the PNG was saved, it's annoying!!! Ugh!!!

And I'm in Windows 8.1, 64bit

2K Messages

 • 

35K Points

4 years ago

Not just a Windows issue. It's annoying on the Mac, too.

3 Messages

 • 

104 Points

4 years ago

This reply was created from a merged topic originally titled PHOTOSHOP - Quick Export As JPG / PNG keeps trying to open folder that doesn't e....

Hello,

After using Quick Export As JPG / PNG on my windows 7 machine, I always keep getting error shown below. It looks like a non existing folder keeps trying to open.
When I actually export it, it opens up the correct folder just fine on its own. It's only after minutes of using it that that ghost window issue happens.

In this example the correct folder is : C:\Users\XXXXXX\Desktop\GEM\MY16\hero

But it keeps trying to open to C:\Users\XXXXXX\Desktop\hero even with Photoshop closed.

2 Messages

 • 

102 Points

4 years ago

This reply was created from a merged topic originally titled Photoshop Export Feature Alters Windows Registry.

There is a known bug that has affected several Windows users regarding Photoshop CC's export feature. When an image is exported, Photoshop opens a new window of the File Explorer application, but that action changes a key in the Windows registry. Because of that, every time we go into our file manager and open a folder in the Pictures folder, our computers open up one or two extra windows. We have found a fix for the problem, in which we delete and recreate the NavPane key in the registry editor, but many of us would prefer the option of Photoshop not opening a new window every time we export an image.
Thank you!

22 Messages

 • 

316 Points

This is a bug. No other program in my whole life has done this. It's not practical having that annoying window appear every time we do a Quick export.

7 Messages

 • 

208 Points

4 years ago

This issue has been aknowledge as being a bug for more than a year now (see here https://forums.adobe.com/thread/1982720) yet after 2 updates this extremely annoying bug is still present.

I personally don't have a problem with the possibility of an explorer window opening after an export with 2 conditions:

1.Make it a regular explorer window and not a bugged explorer instance that you can't use to navigate and that spaws new windows all the time.
2.Make it optional.

considering how much we pay for this, I can't help but being extremely disapointed by the quality of the support we are getting.

Can we have a status as When is this going to be fixed ?
Thank you.

22 Messages

 • 

316 Points

Adobe only cares about receiving millions. They don't care about us. Otherwise, this issue would have been fixed already. It's so annoying...

2 Messages

 • 

70 Points

4 years ago

I am afraid Adobe thinks that is a feature. With every update the program becomes less usable.

I have the feeling there is a product owner at place that is just an occasional user. For the amateur, spawning the window is a service.

For the professional this feature becomes a drag and is avoided under all circumstances.


I have no hope of a fix though, newer versions are removing more and more widely used features , adding a flat UI that hinders me in work speed and hence, when I want something get done, I revert to an older PS installation.

Can't be the future. I bet the app market will sooner or later put PS into oblivion if they keep on doing as is.

3 Messages

 • 

122 Points

4 years ago

This reply was created from a merged topic originally titled PHOTOSHOP - Give us an option NOT to open a Window on Export > Export As.

Please provide an option to NOT open a window on Export > Export As when the file is exported.

127 Messages

 • 

2K Points

4 years ago

Please Adobe, kill this pop up. Its so distracting our workflow!

952 Messages

 • 

15.3K Points

4 years ago

Could this feature respect default windows file browser? I have redirected everything into Total Comander via registry in Windows, but this doesn't respects my settings.

Adobe Administrator

 • 

14.9K Messages

 • 

286.1K Points

4 years ago

This is on the Export As team's list to investigate/change.

Sr. Product Manager, Adobe Digital Imaging

952 Messages

 • 

15.3K Points

4 years ago

I think I found solution:
1) open: 
c:\Program Files\Adobe\Adobe Photoshop CC 2015.5\Required\Plug-Ins\Generator\crema.generate\lib\file-utils\index.js (or path where you have Installed Photoshop)

2) find
var openFolderOnceInOS = function (destFolder) {
        if (!gFolderShownInOS[destFolder]) {
            gFolderShownInOS[destFolder] = true;
            return exports.openFolderInOS(destFolder);
        }
        return Q.resolve();
    };
3) and replace it with
 var openFolderOnceInOS = function (destFolder) {
        /*if (!gFolderShownInOS[destFolder]) {
            gFolderShownInOS[destFolder] = true;
            return exports.openFolderInOS(destFolder);
        }*/
        return Q.resolve();
    };
4) Restart Photoshop
5) Repeat after each bigger update of Photoshop
This means that you commented part of code which opens window.

22 Messages

 • 

316 Points

Thanks for this workaround, but for someone like me who changes harddisk drives and refresh/format windows repeatedly, this isn't  practical, having to modify that script everytime I install PS...

952 Messages

 • 

15.3K Points

Sure, it really is. But this is best solution before adobe will fix it. (And it could takes years.) I am thinking about making tweaker for Photoshop. But it's still same... you need to something install after Windows reinstalling.

22 Messages

 • 

316 Points

True that. Well it worked, so thanks. No more annoying Window Explorer windows after quick export. Blessings!

127 Messages

 • 

2K Points

I am wondering, what prevented adobe in the last 10 months to release a simple code fix like that in the last updates.

They should pay their costumers like Jaroslav for doing their job.

Ridiculous.

2K Messages

 • 

35K Points

> I am wondering, what prevented adobe in the last 10 months to release a simple code fix like that in the last updates.>

I'll guess a couple things. They're a very big company, so not as inclined to respond quickly to a few requests to change a "feature." It's us saying we don't like the feature, and having enough of us is what gets them to (eventually) maybe move to change it.

Also, they're a very big company (did I say that?<G>) with very big apps. I don't think the individual programmers, or possibly even the individual product managers, get to simply say "write a script and stick it in." It's got to get enough internal approval for whatever they do that actually affects the code. That means a study of responses to a feature, reaching out to find out who likes/dislikes it and why, and doing that takes time, so change is even slower.  They're not going to get that approval just because it only takes someone a day to write it, and many others time to make sure it's not breaking something else, or breaking a lot of workflows that have been established around the "feature."

You know that using Jaroslav's script is at your own risk. But what is "easy" for Jaroslav to do (if anyone could call script-writing easy), isn't so easy for a big company to do. Mavericks usually aren't kept on in big corporations because they're telling all their customers to take the risk without knowing there is a risk.

It could be a preference so it works both ways. Everything could be a preference, and we'd spend 100 hours just filling out our preferences, so even that isn't the simple solution to an issue that I'd like it to be when a feature like this is annoying me.

We may be the squeaky wheel on this issue, but there could be even more squawks if they simply disable the feature. Those people don't have a tendency to complain until what they like gets eliminated. I have no clue why anyone thought this particular feature was a blessing, but some people obviously did, and if we can ignore them, I doubt Adobe can.