Skip to main content
Participating Frequently
March 22, 2022
Question

Audition 2022 - Not Responding during Launch

  • March 22, 2022
  • 1 reply
  • 1626 views

Hello, All.

I used Audition a few weeks ago and did not have any issues.
However, I had to change my subscription plan, and when I logged back in, Audition, when launched, gives the spinning wheel of death, with "Not Responding" in the title bar.
I've left it running for about 10 minutes, without change.
I uninstalled and reinstalled and still have the same issue.

I used Resource Monitor.
When opening the "Analyze Wait Chain"
It just says:
Adobe Audition.exe is not responding.
There is no other information included and no chain.

What has happened?

Specs
Dell M6800
Windows 10 Pro (Latest)
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz 2.40 GHz
20gb Memory
(Dual Graphics)
Intel HD 4600
Nvidia Quadro K3100M

All Adobe products and their cache are running from an SSD drive.
Plenty of drive space remaining.

This topic has been closed for replies.

1 reply

SteveG_AudioMasters_
Community Expert
Community Expert
March 22, 2022

Chances are that the credendials for your installation aren't being recognised by the CC app. Probably the only solution to this is to uninstall Audition using the CC-Cleaner tool and then reinstall it from your updated CC app. The Cleaner tool does a more comprehensive uninstallation, leaving far fewer traces behind.

Participating Frequently
March 22, 2022

Tried the CC-Cleaner, and it uninstalled everything. No big deal.
After a reboot, I reinstalled everything again.
And still, Audition is Not Responding.
CPU - 14.2%
Memory 152.1 MB
Disk - 4.9 MB/s
Power usage - Very high


Participating Frequently
March 23, 2022

I logged out of Adobe and had to log back in.
When I opened Audition, it showed me the
Start Screen & Login Screen.
I signed in, authorized through the mobile app.
And then it froze on me again with Not Responding.

The Start Screen window may be trying to launch and is not loading and is causing the program to freeze.

This seems to be a BUG.
I will post this link to the Adobe FB page, have them read it, and see what they have to say.