Organizer 2022 causing black screen

Forum|Forum|3 years ago
February 25, 2022
4 replies
767 views

Dell XPS 8940 running Windows 11

I had PS Elements 15. Organizer had about 10,000 pictures cataloged and was working fine. I installed PS Elements 2022 and it asked if I wanted to convert my exiting '15' files to '2022'. I said yes.

Now when I open Organizer, I see one of my photos briefly. Then, the entire screen goes black. It occasionally flickers for a split second. I have to use Task Manager to shutdown Organizer. Photoshop Elements and Premiere Element both work fine.

This topic has been closed for replies.

M

Mario29864803re6e

Participant

Same thing is happening with Organizer 2023. Practically is useless. Every command you click turns the screen black. Elements and Premier work fine.

Greg_S.

Community Expert

@Mario29864803re6e, try the following:

press the Shift key while opening the Organizer. This will open the Catalog Manager.
Create and Open a new catalog.
If the program opens OK, go to Edit>Preferences>Media Analysis and uncheck all the boxes.
Close the Organizer and relaunch it.
If the program opens, go to File>Manage Catalogs and open your old catalog and see if there is any difference with the black screen.

S

sangsoft@verizon.net

Participant

Update:

After a complete gut of ALL Adobe products and a fresh download and re-install of the same, the 2022 Organizer now launches fine. Now the long (boring) task of reorganizing the Catalog begins yet again. I have come to expect this as normal behavior for Adobe product upgrades. Oh well back to work.

S

sangsoft@verizon.net

Participant

Update to the Update:

Its Back. After launching fine at least 3 times without issue, the black screen is back. I really hate opening support tickets. Such a life drain.

Granted, I have a lot going on. But this was working fine before 2022 version. So....

S

sangsoft@verizon.net

Participant

More updates.

I re-installed Version 2020 of the Elements suite, and it is aslo having issues. So I suspect this is more than an Adobe issue. I work for a company that is a big Adobe product house so this is a bit concerning.

I'll have to look into if this if being reported in the corproate production environment also.