"Ambiguous" Reactivation After Hardware Change

[Frogisis]

A couple weeks ago my computer basically had an aneurysm and most of it needed to be replaced before it would even start again. Had to replace the processor, but because the mobo was old and incompatible with new ones, I had to replace that and the RAM as well.

 

After the latest patch (the one with the Starforce fix), I got around to DCS, and it notices the change and asks me to hit "retry" in the little Starforce window that pops up, where the serial number is still right there in the text box. I do this, and it runs and says it worked and I have 8 activations left, so I press OK, but the window won't disappear ("OK" just becomes grayed out).

 

It does this for each installed module (some of them more than once), and when I get about 5 windows deep, DCS crashes.

 

If I deactivate all modules but one or two, I can get into the sim world itself, but can't "be" anything, only watch. The "instant action" missions will load, but I can't enter the cockpit, and the plane or helo just flies its waypoints under AI control (the Su-25T being the exception, naturally).

 

I tried deactivation of the licenses, but that wouldn't go through because of the hardware change, and tried the web registration where you input the hardware code and serial and they give you an activation code, but that had the same results as just hitting "retry" in Starforce. Clicking on the Starforce icon in "bin" doesn't seem to get me anywhere either, though if I toggle the window's single option and press "go" or "run" or whatever, I get an error window with a bunch of alphanumerics I don't understand.

 

I thought I'd ask if anyone had any other ideas before I just bite the bullet and do a fresh install, since I'm not even sure that would fix the issue.

[Flagrum]

Clicking on the Starforce icon in "bin" doesn't seem to get me anywhere either, though if I toggle the window's single option and press "go" or "run" or whatever, I get an error window with a bunch of alphanumerics I don't understand.

What is that single option that you can toggle? And please post the content of that error window - or post a screen shot of it.

[Frogisis]

What is that single option that you can toggle? And please post the content of that error window - or post a screen shot of it.

 

dcs_protect.exe (in "bin") was the file, and when I run it there's a single button saying "register event log" under the single category "Miscellaneous." It's unchecked by default, but when I check it, the "next" button becomes active. When I click on that, however...:

[Flagrum]

dcs_protect.exe (in "bin") was the file, and when I run it there's a single button saying "register event log" under the single category "Miscellaneous." It's unchecked by default, but when I check it, the "next" button becomes active. When I click on that, however...:

Ok, whatever that is, I am pretty sure it is not directly related to your problem. That dcs_protect.exe is not meant to be run by us mere users, afaik. At least I have never ever read something about it here on the forums when it came to serials and activation problems.

 

What I would try in your position would be something like:

- check your status of your serials at the dcs webshop

- if that does not reveal anything new, I would deactivate all installed modules (probably in game via module manager) so I would not unnecessarily lose activations when I ...

- ... deinstall all modules

- check that DCS world without modules (re-check via module manager?) runs properly

- install ONE module, start a mission with the corresponding a/c, and see how things go with the serials and activation

- if things go well, repeat the last step with the next module

- if things still don't work out, I'd try to appy the registry patch (after deinstallation of all modules) that removes all serials from the computers serials so it looks like a totally fresh install of DCS world

 

But check the customer support forum first, perhaps something catches your eye. http://forums.eagle.ru/forumdisplay.php?f=38

[MadDog-IC]

A couple weeks ago my computer basically had an aneurysm and most of it needed to be replaced before it would even start again. Had to replace the processor, but because the mobo was old and incompatible with new ones, I had to replace that and the RAM as well.

 

After the latest patch (the one with the Starforce fix), I got around to DCS, and it notices the change and asks me to hit "retry" in the little Starforce window that pops up, where the serial number is still right there in the text box. I do this, and it runs and says it worked and I have 8 activations left, so I press OK, but the window won't disappear ("OK" just becomes grayed out).

 

 

Had similar issue recently after flashing the M/B Bios and forgetting about the ramifications with DCS starforce protection, you end up not being able to reactivate or deactivate most modules.

 

 

Solution:

----------

 

1. Before you do anything, make sure you have all Serial Numbers for your modules, written down, you will need to re-enter them later on in this fix.
   
2. You need to delete the old DCS module keys stored in the Windows registry. I have attached some of them to this message for you.
   
3. If all of your modules will not reactivate - run "delete_all_DCS and DCSW_activation_data.reg". (by running delete all, it will also affect standalone versions of DCS A-10 and DCS Blackshark 2)
   
4. If only some modules don't activate - run "only the necessary individual .reg files for that module".
   
5. Once all of the old Registry keys are deleted, re-run the activation window, via running DCSW it self or the Protect.exe in each module directory.
   
6. Re-Enter Your Serial Numbers and re-activate, You will lose an activation for each module done this way, that is just the way it is.
   
7. Problem should now be fixed.
   

Cheers, Ian.

Delete A-10C Warthog_Reg_Keys.zip

Delete Combined Arms_Reg_Keys.zip

Delete Flaming_Cliffs 3_Reg_Keys.zip

Delete KA-50 BlackShark 2_Reg_Keys.zip

Delete P51-D Mustang_Reg_Keys.zip

Delete UH-1H Huey_Reg_Keys.zip

Delete_All_DCS and DCSW_activations_Keys.zip

[Frogisis]

Had similar issue recently after flashing the M/B Bios and forgetting about the ramifications with DCS starforce protection, you end up not being able to reactivate or deactivate most modules.

 

 

Solution:

----------

 

1. Before you do anything, make sure you have all Serial Numbers for your modules, written down, you will need to re-enter them later on in this fix.
   
2. You need to delete the old DCS module keys stored in the Windows registry. I have attached some of them to this message for you.
   
3. If all of your modules will not reactivate - run "delete_all_DCS and DCSW_activation_data.reg". (by running delete all, it will also affect standalone versions of DCS A-10 and DCS Blackshark 2)
   
4. If only some modules don't activate - run "only the necessary individual .reg files for that module".
   
5. Once all of the old Registry keys are deleted, re-run the activation window, via running DCSW it self or the Protect.exe in each module directory.
   
6. Re-Enter Your Serial Numbers and re-activate, You will lose an activation for each module done this way, that is just the way it is.
   
7. Problem should now be fixed.
   

Cheers, Ian.

 

Thanks a ton, I'm going to try this right now. I seem to have plenty of activations left, and don't anticipate another CPU sudden death, so that shouldn't be a problem.

 

...Aaaaaand it worked. Awesome, thank you. Guess who's back, you stupid tanks!

 

Replacing the CPU, Motherboard and RAM makes it a whole new, different computer.

You did not mention reinstalling the OS/drivers, etc.

I would not even attempt running a boot HDD/SSD from one motherboard to another, without a complete partition/format/OS install.

Most certainly, when you do that and install DCS, it will just activate and work.

Well, like I said, I didn't plan for this at all. My cheap, obsolete CPU suddenly crapped out and I had to get parts stores still actually carry and get everything working again or else miss a looming deadline for work. I'd have been in a heap of trouble even getting those parts if my car-owning friend hadn't coincidentally called me right then to come hang out.

 

I didn't think it was worth mentioning, but I did have to reactivate Windows, and did reinstall a bunch of drivers (I even had to go back to the store to buy a new CD drive for the files because the big-ass ribbon on the old one didn't have anything to plug into) but I'm not reinstalling Windows if it would erase all my painstakingly crafted reference material folder organization and other tedious effort I put in customizing everything for my workflow and tastes. This computer is already a total Ship of Theseus (I've had it since 2006, but not even the case is original - At least I bought quality this time).

 

Do you have a link with any info about why I would want to reinstall, how to do it without losing everything, what might happen if I don't do it, and maybe how to do the most important restructuring manually if I decide not to?

Edited November 27, 2013 by Frogisis

[ShuRugal]

Do you have a link with any info about why I would want to reinstall, how to do it without losing everything, what might happen if I don't do it, and maybe how to do the most important restructuring manually if I decide not to?

 

The biggest problem with changing all your core hardware and not re-installing windows is going to be the exact one you are facing now: Registry conflicts. When the OS is installed, it will adapt itself to the hardware it is running on (mobo and CPU) and store that information in the registry. When programs are installed, many of them make notes of the hardware running them for various reasons, and store those notes in the registry.

 

Now, a modern OS is theoretically smart enough to recognize new hardware when it sees it, and not completely gibber itself to pieces in response. But none of your installed software is going to work right if it relies on knowing what hardware it is running on. DCS, in this case, thinks that it has been installed on a mobile drive and moved to another computer in an attempt to bypass S/N Registration. As you continue with new core hardware, you are going to run in to problems like this with any program which tracks hardware present at time of install.

 

Depending on what version of windows you run, it may or may not be possible to do a non-destructive reinstall. The simplest thing would be to boot up windows self-repair function and let that run. That will, among other things, check for registry discrepencies and correct any it recognizes.

[Frogisis]

The biggest problem with changing all your core hardware and not re-installing windows is going to be the exact one you are facing now: Registry conflicts. When the OS is installed, it will adapt itself to the hardware it is running on (mobo and CPU) and store that information in the registry. When programs are installed, many of them make notes of the hardware running them for various reasons, and store those notes in the registry.

 

Now, a modern OS is theoretically smart enough to recognize new hardware when it sees it, and not completely gibber itself to pieces in response. But none of your installed software is going to work right if it relies on knowing what hardware it is running on. DCS, in this case, thinks that it has been installed on a mobile drive and moved to another computer in an attempt to bypass S/N Registration. As you continue with new core hardware, you are going to run in to problems like this with any program which tracks hardware present at time of install.

 

Depending on what version of windows you run, it may or may not be possible to do a non-destructive reinstall. The simplest thing would be to boot up windows self-repair function and let that run. That will, among other things, check for registry discrepencies and correct any it recognizes.

 

Thanks for the quick reply. That's kind of a relief, actually - My imagination was going crazy with a perfect storm of miscalibrated drivers and feedback loops unwittingly increasing voltages until something fries again.

 

Yeah, I fully expect to be clearing stuff up like this for a while yet. The graphics programs I use are stable and running better than ever, though, so it doesn't seem like anything is seriously jamming up the works, but I'm sure it could be made more stable and efficient still.

 

I'll do the Windows self-repair, though, for sure, and do my homework on whether I can do a non-destructive reinstall (it's Win7 Home Premium x64). Thanks again for the info. :thumbup:

[AtaliaA1]

Wow.............An adventure it was too!!!

 

You may want to get an SSD. One reason is speed, the other is a form of backup. I held on to my HDD after adding the SSD just in case I have the same type of adventure you did.

 

I laughed when I read your, "Car owning friend" statement. It is a pain to own a car in the big city. Chi-town is cold about now.