Jump to content

Some modules fail to reactivate after mainboard change


kungfoo

Recommended Posts

I've changed my mainboard and my CPU to much faster ones. Now when I start 2.0 beta, it want to reactivate all of my modules. So far so good.

Some of the modules worked to reactivate, such as F5-E and the Gazelle. However, Nevada terrain and the Mig-21 and the UH-1 module always fail after the reactivation actually seems to have worked.

Is there any way I can fix this?

Link to comment
Share on other sites

I've tried to use the .reg files from the page that has instructions to deal with activation problems.

 

This is on Windows 10, btw. The first module that fails to activate is Mig-21 and it is the first one that claims, it needs admin rights to do so. After that the OS dialog that asks for those privileges is opened and then, after actually doing the activation (it seems) it fails.

This is 2.0.3 (the newest version available via the updater) and the error code displayed is:

 

Internal error (error code: 0xC000001D). Close all applications and try again.

Edited by kungfoo
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...