Activation issue driving me nuts!

Forum|Forum|6 years ago
March 19, 2019
1 reply
586 views

Since I installed CC2019 one machine continually asks me to activate:

Note the name of the PC is the same as the one it's asking me to activate. AVIDS2W10.

Here is a screen from about this computer.

So I have to reactivate. No big deal right. Except it happens randomly every 5 or 6 times I start an Adobe application. Plus if I'm rendering a Media Encoder job at the time I get an endless loop of are you sure you want to quit. There is an item rendering. Well no I don't want to quit but I don't get another option.

I've tried everything suggested in page about this problem including re-starting the Windows WMI service and uninstalling and re-installing Creative Cloud. Nothing works. I've lodged a bug report. No action. Does anyone have a solution?

Creative Cloud

This topic has been closed for replies.

Vidya Sagar

Adobe Employee

We’re so sorry to hear about the activation issue, John Mondo.

Have you tried all the steps suggested in this article? Adobe Creative Cloud signs you out or asks you to sign in repeatedly

Let me move this thread to Creative Cloud space for more assistance.

Thanks,

Vidya

J

JOHN MONDOAuthor

Inspiring

Thanks Vidya. Yes I tried all the steps on that page. LAN settings were already in auto. I restarted the WMI service (even though it was already running) and rebooted the machine. I uninstalled Creative Cloud using the uninstaller provided and re-installed and rebooted.

As this didn't happen until I installed CC2019 back in December last year or whenever it came out, I think I need to completely uninstall everything and start from scratch. Do you have an uninstaller that will do that? Without removing plug ins and scripts of course. And of course removing any authorisation data that might be corrupted.

I thought Adobe read the machine code embedded in the processor or somewhere and used that as it's authorisation identifier, in which case I fail to understand why it gets confused as nothing has changed on this computer. Well apart from Windows updates which could always be the culprit but you'd think Adobe would have nailed that down by now.