Adobe CC Desktop Login Fails with Federated ID – Browser Not Launching Despite Correct Setup

[loyal_student2739]

Hi everyone,
I’m currently facing an issue with signing in to the Adobe Creative Cloud Desktop App (version 6.6.0.611) on Windows 11 (build 22631) in combination with a Federated ID and Conditional Access setup. When trying to log in via the menu “Help > Sign in using your browser”, nothing happens—the default browser (Microsoft Edge) does not open. All other options under the Help menu work fine, but this particular login entry is completely unresponsive. I have this problem since the 2nd may.

The only way the login works is by manually deleting all Adobe-related Windows Credentials from the Credential Manager. After that, the browser opens once for login, but this behavior is not reliably reproducible.

What I’ve already tried (unsuccessfully):

• Full uninstallation of Creative Cloud including Adobe Cleaner Tool
• Deleted all leftover registry entries and temp data
• Enabled devtools in the app — IMS or Jump URLs do not appear in the Network tab
• Registry settings verified:
  • Added iAcroLoginType as DWORD with value 5 at
    Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown
  • Also tried iNGLCEFWorkflowEnabled (value 0) at the same path — no effect
• Created EnableIEBrowserWF.CONFIG under
  C:\ProgramData\Adobe\OperatingConfigs — no change
• Tested and switched default browsers (Edge, Chrome, Firefox) multiple times

I also receive a Conditional Access-related error stating that “switching from here to there is not allowed” because the device does not comply with the required access policy. It prompts me to install a Chrome extension, which is already installed.

In the app’s event log, I see this error:

imsBridge :: updateAccessToken - Error fetching IMS token: IMS Error : Jump url handling required

The Creative Cloud Desktop App installation has not changed (no update), and the login process has worked flawlessly for years with this exact setup.

Have you encountered a similar issue or found a workaround?
Could it be related to the CCXProcess component or a blocked protocol?

Any help would be appreciated!

Best regards,
Nico

[kglad]

are you the admin of a teams or enterprise subscription?

[loyal_student2739]

Yes, I am the admin of an Enterprise subscription using Federated ID and Conditional Access via Azure AD.

[kglad]

in the future, to find the best place to post your message, use the list here, https://community.adobe.com/

p.s. i don't think the adobe website, and forums in particular, are easy to navigate, so don't spend a lot of time searching that forum list. do your best and we'll move the post (like this one has already been moved) if it helps you get responses.

<"moved from download & install">

[loyal_student2739]

alright thank you for the advice!

[kglad]

use your console to ask for help, https://helpx.adobe.com/enterprise/using/support-for-enterprise.html

[loyal_student2739]

I submitted an urgent support request over a week ago. Despite escalating the issue, I haven't received a response yet. I guess I'll just have to be patient.

[Anshul_Nautiyal]

Hi @loyal_student2739,

Thank you for reaching out.

Have you had a chance to try the steps I shared in my previous message? Additionally, I was unable to locate any support case raised under the Adobe ID you used to post this query.

To assist you further, could you please share the Adobe ID or case ID used to open the support case? You may send it to me via private message to ensure your information remains secure. For instructions on how to send a personal message in the Adobe Community, please refer to the following guide:
How to send a personal message in the community

Looking forward to your response.

Regards,
^AN

[Anshul_Nautiyal]

Hi @loyal_student2739,

Thank you for reaching out. Based on your query, it seems that you're unable to sign in to the Adobe Creative Cloud Desktop App via Federated ID on Windows 11, and the "Sign in using your browser" option is unresponsive. Please confirm if this is the issue you're experiencing.

Here are some steps you can follow to address the issue:

1. Check AdobeCCXProcess Permissions: Ensure that both AdobeCCXProcess.exe and Adobe Desktop Service.exe are not being blocked by endpoint security tools or a firewall.

2. Clear Browser Cache and Cookies: Sometimes, residual data in the browser can cause authentication issues. Clear your browser's cache, cookies, and history, and then try logging in again.

3. Ensure Device Compliance in Azure AD: Confirm that the device is marked as compliant in Azure Active Directory (Azure AD) and that the login flow is permitted for third-party applications using embedded browsers or jump URLs. Also, verify that named locations, network restrictions, or app control policies (such as those enforced by Microsoft Defender for Cloud Apps - MCAS) are not blocking redirects or authentication flows. If you're prompted to install a Chrome extension, this indicates that your Conditional Access policy is enforcing session control via the MCAS proxy. In this case, check that Adobe applications are excluded from cloud app proxy and session control to avoid authentication conflicts.

4. As you’ve seen, deleting Windows Credentials gives a temporary fix, which suggests a token caching or SSO corruption issue. To resolve Adobe login issues, first clear Adobe-related credentials in Control Panel > Credential Manager by deleting all Adobe entries. Then, delete cached data from %appdata%\Adobe, %localappdata%\Adobe, and %programdata%\Adobe. Reset stored tokens by deleting registry keys in Regedit under HKEY_CURRENT_USER\Software\Adobe\AIM and HKEY_CURRENT_USER\Software\Adobe\OOBE.  

5. Try a Different Profile: Since deleting Windows Credentials helps, it suggests that the issue could be related to cached credentials. Create a new Windows user profile, sign in with your Adobe Federated ID, and check if the issue persists.

6. Network Configuration and Proxy: If your organization uses a proxy or VPN, ensure the network settings aren't interfering with the browser launch for sign-in. Try temporarily disabling the proxy and attempt the sign-in again.

7. Enable Browser-Based Login (Testing): You can try configuring your users to sign in via the browser rather than the desktop app. Please refer to this documentation for guidance: https://adobe.ly/4mcKa3i

   Additionally, please let me know if this issue is occurring for only a few users, or if it is widespread across your organization.

   After testing these steps, please let me know if the issue is resolved. If it persists, I recommend opening a support case as suggested by kglad.

Regards,

^AN