This issue has stalled without even a single interaction with an engineer. Hope for an improvement.
@Erin_Finnegan I appear to be experiencing a very similar issue, and I believe it may be directly related to an account-side flag or classification.
I first noticed the problem around the middle of September 2025.
There are two symptoms that appear to be connected.
With my main Adobe account:
Adobe Exchange does not work correctly and produces an error.
In the Creative Cloud Desktop application, the plugin-related section and the Features section are missing.
However, if I create or sign in with a new Adobe account on the same computer, same Windows installation, same network, and same Creative Cloud Desktop installation, Adobe Exchange immediately works correctly, and Creative Cloud Desktop shows all three sections normally.
In other words, the problem follows the Adobe account rather than the computer, operating system, network, or Creative Cloud installation.
I previously spent a considerable amount of time troubleshooting this issue, including trying to diagnose it together with ChatGPT and testing different possible local causes. None of those attempts resolved the problem.
Simply changing the Adobe account does resolve it.
This makes me suspect that my main account has some server-side flag, organization attribute, market segment, EDU/K-12 classification, or another account property that causes Exchange and certain parts of Creative Cloud Desktop to behave differently.
The investigation described in this thread regarding ownerOrg, market subsegments, K-12 classification, and account flags therefore looks particularly relevant to my case.
There is also another reason why I think this issue may affect considerably more users than just my own account.
I publish a popular free plugin on Adobe Exchange which has been listed among the popular free plugins on the first page of the Marketplace.
During the six months immediately preceding October 2025, the plugin had the following number of acquisitions:
April 2025: 9,552
May 2025: 9,158
June 2025: 8,983
July 2025: 10,643
August 2025: 9,477
September 2025: 10,786
The average for these six months was approximately 9,767 acquisitions per month.
In October 2025, immediately after I had noticed the Exchange / Creative Cloud account issue in September, acquisitions suddenly dropped to 6,966.
This represents a decline of approximately 28.7% compared with the average of the previous six months.
I have attached a screenshot of the acquisition statistics showing this change.
What makes this especially noticeable is that acquisitions had remained relatively stable for many months before this. The October result is a clear deviation from the previous range.
Around the same period, I also observed a noticeable decline in sales of my commercial products.
Of course, the acquisition statistics alone do not prove that the Exchange issue caused the decline. However, considering that this is a high-visibility free plugin that receives substantial organic discovery through Adobe Exchange, the timing raises the possibility that the problem may have affected more users than just my own account.
If some Adobe accounts were incorrectly assigned a server-side flag, organization attribute, EDU/K-12 classification, market subsegment, or similar restriction, affected users might simply lose access to the plugin Marketplace or related Creative Cloud sections without understanding what happened.
This could potentially reduce Marketplace discovery and plugin installations without developers being aware of the underlying cause.
I think comparing my affected Adobe account with a newly created account could be particularly useful for the engineering team because the testing environment is identical and only the Adobe account changes:
Main account → Adobe Exchange error + missing Creative Cloud sections
New account → Adobe Exchange works correctly + all Creative Cloud sections are present
Whatever is causing the problem therefore appears to be tied directly to the account.
I can provide the ownerOrg, output from adobeIMS.getProfile(), or any other account/profile information privately if the engineering team would like to compare the affected account with the working one.
@Alexandr_Stroganov I saw a decline in the same window, and I think I’ve now found the probable cause in my case, a different one from the account issue being discussed here.
First, for context: I’m not affected by the symptom you describe. I confirmed earlier in this thread that I see all three sections in the Creative Cloud desktop app, and Exchange works normally for me.
What I did was stop looking at my portfolio total and break the numbers out per listing. That made it obvious. One of my plugins, which had been sitting in a Creative Cloud desktop app collection for about four years, drops off a cliff in October 2025 and has stayed at a small fraction of its previous level ever since, nine months with no recovery. In the very same month, a different listing of mine rises sharply and has held at the higher level since. Two curves, same account, same month, opposite directions.
That window is when the plugin collections in the Creative Cloud desktop app and the featured plugins on Exchange were rebuilt. I’ve since checked: the first plugin no longer appears in the featured plugins at all, and the second one now appears in Editor’s choice.
So for my case this looks like a lost collection placement rather than an account classification problem, which also explains the shape. A bug tends to get fixed; a placement that’s gone stays gone, and the numbers never come back.
This doesn’t contradict what @sttk3 is dealing with, that EDU flag is confirmed and produces real Exchange errors. Two separate problems can be running at the same time.
Hi @Alexandr_Stroganov ,
This is somewhat lucky for @sttk3, as another afflicted developer proves a pattern.
Please follow the instructions from early in the thread and DM me a screenshot as described: https://forums.creativeclouddeveloper.com/t/can-uxp-cep-be-installed-from-the-creative-cloud-app/11934/19?u=erin_finnegan
I disagree; the engineers offered to do a support call with you and you refused. They did investigate your problem and couldn’t reproduce it.
@Alexandr_Stroganov I’m sure the engineers will offer you a similar support call to investigate. It’s OK if there is a language barrier, even a real-time chat on an MS Teams call can be translated.
I also can confirm with @tomzag that the collections were updated around that time.
Let me point out that, even though I suggested communicating via private messages on this forum instead of making a support call, and @Erin_Finnegan accepted that and created a thread for that purpose, not even one engineer participated in it or posted even a single character.
That said, it’s good to see things moving in the positive direction. Here’s hoping this trend continues.