Upgraded CPU, now modules won't activate

[SnorreSelmer]

The short version:

I upgraded my i5 6600K to an i7 7700, and DCS wants me to activate the modules again because of hardware changes.

 

This is expected, this is fine.

 

What's NOT fine is that when I go through the activation process, I click "OK" at the end, and the activation application hangs for ~30 seconds and silently dumps to desktop with no error. When I run DCS again, it asks me (again) to activate the modules I just manually ran the activation for.

 

Is my only option to do a clean Windows reinstall to get out of this endless loop of unhelpfulness?

I'm on my last activation on several modules, so I'd like to avoid this in case I need to wait for 30 days to get to fly some modules.

[ApoNOOB]

https://www.digitalcombatsimulator.com/en/support/faq/564/ see registry fixes, sounds like that

 

Also try activation without starting dcs in the relevant module folders under /bin.

[SnorreSelmer]

Also try activation without starting dcs in the relevant module folders under /bin.

 

I already tried that, but I'll try the registry fixes, then do another round of "manual" activations.

[Johnny_Rico]

you are running this as admin ?

[SnorreSelmer]

Thanks ApoNOOB, that fixed it! I had to manually remove the NS430 key as there was no reg-file for that one, but it was an easy job.

Edited October 5, 2017 by SnorreSelmer

[SnorreSelmer]

you are running this as admin ?

 

I NEVER run anything as admin unless it ABSOLUTELY requires it.

[BIGNEWY]

if you upgraded your hardware without deactivating your modules you will need to delete the registry using the keys here https://www.digitalcombatsimulator.com/en/support/faq/564/

 

then reactivate

[BitMaster]

I NEVER run anything as admin unless it ABSOLUTELY requires it.

 

a bit off topic:

 

When you are running Windows there is hardly any way around running the whole box as an administrative user if you want all your apps and games to work. Right clicking "run as admin"

does not mean your account is not administrative. If it was, you could not choose that option or something went completely wrong, ALL THE WAY !

 

Even in a domain environment users often run as local administrative accounts, only their doamin wide rights are limited to "standard" users, or "power" users.

 

 

One of the biggest security issues in Microsoft OS's. They have UAC and other measures deployed with mixed success and results to secure that hole again. An epic strategic failure imho.