IMPORTANT MiG-21bis StarForce PATCH - MARCH 2017

yes it wont activate in 2.0.5.3521 even with the latest Starforce Protection Malfunction Update any ideas?

 

I have it working fine in 1.5.6

Please wait for the 2.0.5 patch. We will try to patch it next week.

Um, so i patched before reading... got an error in the beta...

Deleted reg keys, re-activated - good to go...

Now there is an error activating in the Alpha - what do i need to do to re-activate the Mig in the Alpha?

yes it wont activate in 2.0.5.3521 even with the latest Starforce Protection Malfunction Update any ideas?

 

I have it working fine in 1.5.6

You need to deactivate because of the new StarForce bindings. If you have done the procedure for openOpen, you wont have to do it again for the stable release or 2.0.5 when the next update occurs.

Until then, do not run the stable release or 2.0.5 if you have updated openBeta with the procedure.

Otherwise, you will need to deactivate/activate between versions.

You need to deactivate because of the new StarForce bindings. If you have done the procedure for openOpen, you wont have to do it again for the stable release or 2.0.5 when the next update occurs.

 

Until then, do not run the stable release or 2.0.5 if you have updated openBeta with the procedure.

 

Otherwise, you will need to deactivate/activate between versions.

Actually, it doesn't seem possible to deactivate the new version from 2.0.5 anymore, so no switching. Or perhaps by messing with the registry.

EDIT: nevermind, the new pcnsl.exe has to be used to deactivate the new version, and the old to deactivate the old, it's different, makes sense.

followed the process, no issues... said I had 13 activation's after I patched and re-activated. :-)

So can we reactivate our Mig for 1.5.6 users?

I've followed the process. The first automatic activation failed, second was fine but the activation's quantity didn't increase.

I've followed the process. The first automatic activation failed, second was fine but the activation's quantity didn't increase.

Server side needs some time to refresh the data. It's there - don't worry. Confirmed.

So, I missed the message and updated before deactivating. What can I do to fix? I get the following when I try to run DCS:

Unable to run the application due to integrity fault of the Activation Key. Re-enter a valid Activation Key or re-activate the application.

If the error recurs, click "Error report" and send the report to product technical support.

This is my bad, but I'd appreciate any help you can give. Thanks!

Server side needs some time to refresh the data. It's there - don't worry. Confirmed.

Great! Thx for the info :thumbup:

So, I missed the message and updated before deactivating. What can I do to fix? I get the following when I try to run DCS:

 

Unable to run the application due to integrity fault of the Activation Key. Re-enter a valid Activation Key or re-activate the application.

If the error recurs, click "Error report" and send the report to product technical support.

 

This is my bad, but I'd appreciate any help you can give. Thanks!

Please send support request on support@leatherneck-sim.com in order to keep this thread clean from individual instructions.

Let us know which DCSs you have on your PC along with Beta.

You'll get your answer in minutes.

I run three copies of DCS, Stable, OpenBETA and 2.0 Alpha (NTTR).

I followed the instructions and deactivated my MIG21 in DCS BETA before applying the update to BETA today.

I reactivated the MIG in BETA and all was well.

I then tried the MIG in the Stable and Alpha versions and in both received and "Integrity Check" on (apparently) the activation code for the MIG.

Two things, apparently the deactivation affected all copies of the MIG on my computer,

and I can't fly the MIG now in the stable or the V2-NTTR copies of DCS.

I'm not happy.

What part of this people dont understand:

"You need to deactivate because of the new StarForce bindings. If you have done the procedure for openOpen, you wont have to do it again for the stable release or 2.0.5 when the next update occurs.

Until then, do not run the stable release or 2.0.5 if you have updated openBeta with the procedure."

Follow Rudel and Dolphin´s instructions. People only need to read.

This part.

Until then, do not run

They have apologized for that, and are asking people to be patient until 2.0.5 patch, hopefully next week.

Until then, enjoy Mig-21 in Open Beta, or DONT DO ANYTHING and wait for the 1.5.6 release update and 2.0.5 Update.

You can still enjoy the Mig-21 in Dcs 2.0 and 1.5.6 Stable if you WAIT for the update, doing anything.

What a surprise. I have three installs zero activations left and 1 mig21 on OB. Thank you very much. JEZUS!

Activation problems from day 1 till now! Only on MIG21???

I´m amazed how hard is to read first and do after.

Well it is not clear enough, and we are not all IT specialists. That could be a reason.

What a surprise. I have three installs zero activations left and 1 mig21 on OB. Thank you very much. JEZUS!

 

Activation problems from day 1 till now! Only on MIG21???

Please send your key with this message to support@leatherneck-sim.com

I'll check the status with StarForce server.

Thank you.

Well it is not clear enough, and we are not all IT specialists. That could be a reason.

I don't think you need to be an IT specialist to understand the words DO NOT RUN.

If you read the PDF attached at the first post i think honestly is crystal clear, but even if it´s not for everybody Rudell and Dolphin are answering any question trying to help everybody with the process.

If anyone has doubts about how to do this steps DONT DO ANYTHING, ask first and they will help you.

I´m still waiting for the Stable 1.5.6 update to run the fix step by step, so i´m still enjoying the MIg-21 in both 1.5 an 2.0.

A little patience is always good.

What a surprise. I have three installs zero activations left and 1 mig21 on OB. Thank you very much. JEZUS!

 

Activation problems from day 1 till now! Only on MIG21???

Yeah, I'm not going to pretend to understand how a SF update applied to a BETA module aircraft affects the Stable and 2.0 releases.

I don't care what was said or apologies offered, the fact the there were possibly three installations to consider was well known and it was decided to let customer deal with it.

So be it. There won't be another Star Force aircraft in my future.

So you are going to stop playing DCS as a whole.

Everything is running with Starfore protection.

Please send your key with this message to support@leatherneck-sim.com

 

I'll check the status with StarForce server.

 

Thank you.

I have mailed. I don't know what to do. I removed the MIG 21's from branch and 2.0. When i installed them over the starforce protection say activation error.

If you have patched the Open Beta to the latest update AFTER deactivating the Mig-21, and then reactivated, the only DCS version that must work now for the Mig-21 is DCS Open Beta.

DONT RUN 2.0 or Stable 1.5 BEFORE they are updated. Mig-21 is not going to work until that.

When the 2.0 and Stable DCS 1.5 are updated the Mig-21 would work without repeating the process again.

I have mailed. I don't know what to do. I removed the MIG 21's from branch and 2.0. When i installed them over the starforce protection say activation error.

Please check your mail. Once you fix the problem in Beta, please don't try to activate/deactivate MiG in Public or Alpha. You can still use any other aircraft you have there.

Thank you.