Adobe CC Desktop Login Fails with Federated ID – Browser Not Launching Despite Correct Setup
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
- Added iAcroLoginType as DWORD with value 5 at
- 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
