P: Export As not working after updating to MacOS 11.6.2

sorry you're still seeing this issue. Have you tried deleting prefs.txt file and restart PS? 

file should be here: C:\Users\[USERNAME]\AppData\Roaming\Adobe\UXP\PluginsStorage\PHSP\23\Internal\com.adobe.photoshop.exportAs/PluginData

if it still doesn't work after, could you send us log files so we can take a look? On Win, file should be located here:

I don't know why my issue has been merged with this as I am using Windows not MAC. And the final straw today, I now cannot even do a quick export. I will be canceling all my adobe subscriptions and moving to other software. 

Path for the prefs.txt file on Windows:

C:\Users\[USERNAME]\AppData\Roaming\Adobe\UXP\PluginsStorage\PHSP\23\Internal\com.adobe.photoshop.exportAs/PluginData

BretN's solution worked for me, I wasn't able to use the Export As function for a month.

Thank you so much.

This morning I was able to export, after an update, I am now no longer to export and I am completely locked from doing my work. 

I get no valid asset to export

Yes, that is the correct path, I forgot to include the Application Support folder. 

I can confirm that Brentt solution worked for me.

the path is slightly different on my OSX.

/Users/[UserName]/Library/Application Support/Adobe/UXP/PluginsStorage/PHSP/23/Internal/com.adobe.photoshop.exportAs/PluginData

Depuis quelques semaines, lorsque je veux exporter une image via la fonction "Exporter sous", un écran gris apparaît mais pas l'image (cf image ci-dessous). Lorsque je passe la souris sur le bouton exporter, un message mentionnant qu'aucun fichier valide est à exporter alors que mon fichier est du simple JPEG.

Je suis obligé de créer une copie de la photo pour l'exporter au même format.

Je suis sur Windows 11 avec un PC Gamer.

Est-ce le système d'exploitation qui est encore pas du tout optimisé ou est-ce les nouvelles mises à jour de Photoshop qui ne sont pas du tout fonctionnelles ?

@Yona5E7C Unfortunately, we don't have enough information on the issue to make any progress. At this point we are only speculating that Sophos may be involved, but haven't been able to prove that is the case. It is very likely that a third-party component is the cause of the behavior because we have very few people encountering the issue (that we know of) and have not seen the behavior on our end.

You mentioned that disabling Sophos did not change the behavior, so that doesn't seem to indicate it is the source of the issue. However, another test would be to uninstall Sophos and test (you may wish to remain offline while performing such a test, then you can reinstall once you are done verifying). If the behavior goes away during this test and comes back after reinstalling, that would prove Sophos is the source of the issue (disabling anti-virus usually means only some portions are actually turned off while some safey measures remain running and can still cause conflicts). If removing Sophos doesn't resolve the issue, that pretty much removes it as a suspect and we are back to square one. 

any updates?