1.5.3 Re-Activation

[BSS_Sniper]

I'm just now seeing this thread after this reactivations happening many times to me, even last night. I'm trying the registry fix and I hope it works. It happens a lot.

[Spectrum Legacy]

Found out that changing C6 state of cpu in bios upsets the Mig at least on my system, which will then ask to reactivate.

 

Maybe the info will be of some use...

[Yuya6104]

My re-actvation Mig-21 Report

txtD7CB.rar

[slicker55]

I hope someone at LEATHERNECK will read this and reply...

 

I have been getting the re-current activation error messages outlined in this and other similar threads and I'm losing my quota of activations unnecessarily - now down to 8 in just 48hrs.

 

There has been no significant hardware added to my system but this issue appears to have started since reverting an overclock on my ram in the bios.

 

I tried following the advice and used the deactivation .exe method which I thought had worked. The PC remained in constant use for over 12 hours solid and everything was ok but next day, rebooted and booom... it wasn't :(

 

I have tried deactivation via DCS and reinstalling the module but with same result. This module is only installed on DCS 1.5 which is bang up-to-date.

 

I have generated a full error report and submitted it via the LN web site - no reply so far.

 

I have emailed Nicholas Dackard directly - no reply to date

 

I have posted a PM on the LN Facebook page - no response.

 

Is there any way that I can continue using this module without losing more activations?

 

I have reached an advanced stage of developing a Helios profile for this aircraft and therefore have to have it running for constant test purposes,

 

Hoping someone will reply!

Edited March 24, 2016 by slicker55

[Cobra847]

I hope someone at LEATHERNECK will read this and reply...

 

I have been getting the re-current activation error messages outlined in this and other similar threads and I'm losing my quota of activations unnecessarily - now down to 8 in just 48hrs.

 

There has been no significant hardware added to my system but this issue appears to have started since reverting an overclock on my ram in the bios.

 

I tried following the advice and used the deactivation .exe method which I thought had worked. The PC remained in constant use for over 12 hours solid and everything was ok but next day, rebooted and booom... it wasn't :(

 

I have tried deactivation via DCS and reinstalling the module but with same result. This module is only installed on DCS 1.5 which is bang up-to-date.

 

I have generated a full error report and submitted it via the LN web site - no reply so far.

 

I have emailed Nicholas Dackard directly - no reply to date

 

I have posted a PM on the LN Facebook page - no response.

 

Is there any way that I can continue using this module without losing more activations?

 

I am at an advance stage of developing a Helios profile for this aircraft and therefore have to have it running for constant test purposes,

 

Hoping someone will reply!

 

Heya,

 

We've been swamped lately so support has been slow. We just hadn't gotten to your e-mail yet!

 

I've just replied. :)

[slicker55]

Hi Nicholas,

 

I bet you are swamped from what I've read and it must be so time consuming dealing with such issues when you could use the time in better ways I'm sure.

 

That said, it is a right PITA when things don't work as they should. We all get a bit frustrated when our toys ain't working right.

 

You may have read that I have already followed the available advice but running the 'delete deactivation data' tool has not fixed the issue for me.

 

I can confirm the relevant fields in my registry are cleared after using the tool. I then try to reinstall the MiG-21bis via the DCS module manger and re-enter the serial number. It goes through the motions and then confirms activation has been successful

 

However, seconds later another message says the serial number is invalid and away we go again (minus another activation point)

 

Sometimes activation is successful leading one to think it's now ok but the next time the computer is rebooted the activation error message reappears.

 

Thanks for sending the tool but I'm reluctant to try that method again as I'm running out of activations and can't afford to risk getting locked out of the plane altogether.

 

Is the tool you kindly sent in your email the same version as the one available on page one of the following thread?

 

http://forums.eagle.ru/showthread.php?t=136153

 

 

.

Edited March 31, 2016 by slicker55

[BitMaster]

I am also still suffering activation loss.

 

Also Microsoft's new strategy to swop the Win10 built under your feet causes to loose 1 activation every time my Windows 10 Pro 64-bit Evalution-Preview FAST-RING legal copy

of windows renews itself to another built....costing 1 lic each time.

 

Time to get this sorted imho. I have tried multiple times the de-activate regkey thing to no luck... I have meanwhile consumed like 25 activations..or was it 35....

[badaboom]

^^BINGO^^Lost an activation with Win10 update

[Cobra847]

Obviously that is less than optimal. Seems like Windows 10 updates trigger an exceedingly large HardwareID change.

 

We'll have to install Win10 and debug.

[BadHabit]

^^BINGO^^Lost an activation with Win10 update

Same here i am down to 5 left, even some BIOS modifications reduce the key's..

[slicker55]

Nicholas,

 

Can I have an answer to my post #81 (above) and my email dated 24/03/16 please?

[slicker55]

No MiG-21Bis for 10 days since reporting the activation issue (post # 79) and nothing constructive from LN which is even more annoying!

 

LN has a great product (MiG-21Bis) but a fair share of complaints in relation to this pesky activation issue.

 

The lack of customer support is something which may have an adverse impact on the success of future modules which would be a great loss to us all.

 

Please LN... answer your emails, PM's, FB messages etc etc...

[slicker55]

Nicholas,

 

Thank you for replying - mysteriously, the 'activation' message has now stopped! (fingers crossed)

[slicker55]

Hi Everyone,

 

My Mig activation issues have settled down - fingers crossed.

 

This next question may have been answered elsewhere but there's so much to read and not enough time for anything else.

 

Can anyone recall reading whether the Mig can be installed on both DCS 1.5 and DCS 2.0 simultaneously or will this lead to further activation issues?

[tflash]

Well, I had no problems until the latest 2.02 patch. I new the Mig-21bis wouldn't be working in 2.02 as advertised, but to my surprise - and disappointment - I got the activation error on my 1.5.3 installation, that before worked flawlessly. End of story: I can't fly the Mig-21bis anymore on either 1.5.3 and 2.02.

[slicker55]

tflash,

 

Sorry to hear that - you must be very disappointed.

 

Here's an idea...

 

Go into the DCS 1.5 Module Manager and de-activate the MiG-21Bis module and uninstall it.

 

Then go into DCS 2.0 Module Manager and repeat.

 

Then run the Registration Fix

 

Then reinstall the MiG-21Bis module to DCS 1.5 only and reactivate.

 

This may, at least get you back up and running in DCS 1.5 but still leaves my question as to 'whether the activation issues will reoccur if the module is installed in DCS 2.0 simultaneously' unanswered?

 

With a bit of luck Nicholas Dackard will spot this post and let us know?

 

 

.

Edited April 17, 2016 by slicker55

[Cobra847]

Well, I had no problems until the latest 2.02 patch. I new the Mig-21bis wouldn't be working in 2.02 as advertised, but to my surprise - and disappointment - I got the activation error on my 1.5.3 installation, that before worked flawlessly. End of story: I can't fly the Mig-21bis anymore on either 1.5.3 and 2.02.

 

run the .reg fix here: http://forums.eagle.ru/showthread.php?t=136153

 

Thanks,

Nick

[slicker55]

Nick,

 

Thanks for fixing my MiG21 activation issue - it's been fine since applying the reg fix method but I only have the module installed in DCS 1.5 and would also like to have it running in DCS 2

 

Is it possible to have this module installed on both versions simultaneously or will this result in further activation issues?

 

If the module can be installed on both systems simultaneously - is there a recommended way to do this.

 

I know there are others asking the same questions and I'm sure your advice will be very much appreciated.

[Art-J]

I know it's possible to have it working in both versions, as I've just checked it in stable 1.5.3 and reverted 2.0.1.

 

Don't know about recommended installation procedure though. Whenever I have any activation error issues with the -21, I don't bother with de-activating, repairing, uninstalling and whatnot, I just run the registry fix, enter the key again and I'm set.

[tflash]

run the .reg fix here: http://forums.eagle.ru/showthread.php?t=136153

 

Thanks,

Nick

 

Fixed! Thanks Nick!

[Rapier1]

Still can't get this to work. Won't allow me to deactivate due to significant changes in hardware.

[Rapier1]

Never mind. I got it to work. In related news, I am an idiot :)

Very glad to have my Mig back.

[slicker55]

Never mind. I got it to work. In related news, I am an idiot :)

Very glad to have my Mig back.

 

For the benefit of others- how?

[slicker55]

I spoke too soon (post #93) - absolutely no changes to hardware or windows updates and got the activation message twice last night. I noticed the Warty HOTAS hadn't been 'found' during the warm re-start immediately prior to the message appearing. I was later able to replicate this response. In the both instances I chose to ignore the activation message, allow DCS to load, exit DCS and perform a full computer shutdown. Upon switching the computer back on, the activation message did not reappear.