resolved Authorisation failed for odd modules

[schurem]

Hi, I just started the sim and got this message:

 

nullI already did the ipconfig /flushdns thing and tried logging in and out again. It logs in but throws the same error. I can assure you I should be authorised to use both

 

Cheers.

[razo+r]

1 hour ago, schurem said:

Hi, I just started the sim and got this message:

 

nullI already did the ipconfig /flushdns thing and tried logging in and out again. It logs in but throws the same error. I can assure you I should be authorised to use both

 

Cheers.

Check your anti virus, perhaps it removed some necessary files from DCS into quarantine. Restore them and add the files as an exception and run a repair for good measures.

[schurem]

I exempted the DCS folder from the protection thingamibob a long time ago. It helps with the stutters, load times and general bugginess of things. Anyway.

I ran a full repair. On the wrong install (dedicated server) which has its mods folder symlinked to the main install. So that got mauled because the repair cleaned out the mods folder.

There are not enough hands in this house for the amount of facepalm this situation warrants

Edited April 26 by schurem

[schurem]

So, after 15 hours, the main install was repaired. And yes, the error is gone. 

Turns out there's a bunch of manifest.bin files in the /backup001 folder.

Edited April 30 by schurem

[RodentMaster]

I have this problem, and it updated with a new patch, but the problem persists.

[rob10]

11 hours ago, RodentMaster said:

I have this problem, and it updated with a new patch, but the problem persists.

90+% of the time this is due to your anti-virus blocking files.  You may get it to work once after a repair but it will keep coming back if it's antivirus related.

Currently you've given no details on "what" is happening and/or any steps you might have tried to fix it.  There are a few other things it could be, but suggestions at this point would be purely guesses without more info.

[RodentMaster]

On 6/1/2025 at 2:24 PM, rob10 said:

90+% of the time this is due to your anti-virus blocking files.  You may get it to work once after a repair but it will keep coming back if it's antivirus related.

Currently you've given no details on "what" is happening and/or any steps you might have tried to fix it.  There are a few other things it could be, but suggestions at this point would be purely guesses without more info.

Nope. I can assure you it is not the AV, because it worked fine through windows defender and the firewall before the update, and the same executables afterwards gave errors. Remember, it's not crashing. It's RUNNING. It just doesn't let me have my modules. If it was firewall or quarantine related it would be manifesting other problems and they would have come out before this update. I may have found the solution but not the cause. Will reply to another post with it.

[rob10]

53 minutes ago, RodentMaster said:

Nope. I can assure you it is not the AV, because it worked fine through windows defender and the firewall before the update, and the same executables afterwards gave errors. Remember, it's not crashing. It's RUNNING. It just doesn't let me have my modules. If it was firewall or quarantine related it would be manifesting other problems and they would have come out before this update. I may have found the solution but not the cause. Will reply to another post with it.

Sorry, but you're wrong on your assumptions.  There are many posts here of people that lost authorization for modules after an update due to their AV solution deciding it suddenly didn't like a file (often a .dll).

[RodentMaster]

I'm not wrong on my assessments, and not on my machine. I went through all the hoops. I tested everything. I opened up every DCS executable and major folder in my firewall and added defender exceptions to those folders. Nothing was impacted by any AV/Firewall. I was not wrong. I never said it wasn't SOME peoples' issue. 

  EDIT: Also see my workaround. It had nothing to do with firewall or AV. 

 

EDIT2: Oh, I'm sorry. I thought I quoted you on it. I neglected to. Here's the link:

 

Edited June 3 by RodentMaster

[razo+r]

21 minutes ago, RodentMaster said:

I'm not wrong on my assessments, and not on my machine. I went through all the hoops. I tested everything. I opened up every DCS executable and major folder in my firewall and added defender exceptions to those folders. Nothing was impacted by any AV/Firewall. I was not wrong. I never said it wasn't SOME peoples' issue. 

  EDIT: Also see my workaround. It had nothing to do with firewall or AV. 

 

EDIT2: Oh, I'm sorry. I thought I quoted you on it. I neglected to. Here's the link:

 

Reading your workaround, it does 99% sound like your AV removed that one file necessary, which is why you saw "install" in the module manager and not "installed", and also why it didn't download anything (or not a lot). I strongly recommend you to check the logs of your AV to see if that is the case or not.

Also worth to check if the solution of OP would help your case.

And btw, the firewall has nothing to do with any of this.

Edited June 3 by razo+r

[RodentMaster]

When Windows Defender nixes a file (and it has  happened before) you get a log, a list of quarantined files, a history of what it did. I've dug into it. That did not happen here. Rather, and this is also not the first time it has happened, ED released a launcher/updater version that screwed something up as it updated itself. Repair, update, and file check, all within the updater version itself that ED just updated, failed to catch this, but "install" on one specific tab worked. Note that the AV did not stop the workaround. Note that AV does not have any logs, quarantined files noted, nothing. As I said, I jumped through every hoop I could. This was not AV related. I know it's an easy scapegoat, but I hate when people keep blaming the AV when the first thing everybody does is make sure the AV wasn't the problem, and then ask for help.

[rob10]

7 hours ago, RodentMaster said:

This was not AV related. I know it's an easy scapegoat, but I hate when people keep blaming the AV when the first thing everybody does is make sure the AV wasn't the problem, and then ask for help.

That is not the 1st thing everyone does.  That's why it's always the 1st thing that is going be suggested to anyone with this problem.  As has been proven on the forums it is quite often (definitely not always) the reason for the issue, and in those cases people HAD NOT checked that their AV was or was not the problem)

[MAXsenna]

On 6/3/2025 at 3:06 AM, RodentMaster said:

major folder in my firewall

Why? The firewall has nothing to do with this. 

Cheers!