Update Error: "Couldn't resolve host name"

[341-Ces]

And also

 

 

 

PS C:\> Get-NetFireWallRule -Displayname "dcs"

 

 

Name : UDP Query User{F2F25A42-EBA1-48A8-B213-82F1D63F6700}F:\dcs world\bin\dcs.exe

DisplayName : DCS

Description : DCS

DisplayGroup :

Group :

Enabled : True

Profile : Private, Public

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : DeferToUser

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : TCP Query User{1FD791C2-E2C9-42E2-9676-902FAD98136B}F:\dcs world\bin\dcs.exe

DisplayName : DCS

Description : DCS

DisplayGroup :

Group :

Enabled : True

Profile : Private, Public

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : DeferToUser

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : UDP Query User{149E085D-3E28-4678-8523-01A1308B8516}C:\dcs world\bin\dcs.exe

DisplayName : DCS

Description : DCS

DisplayGroup :

Group :

Enabled : True

Profile : Private, Public

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : DeferToUser

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : TCP Query User{A0B0E768-59BF-4E4E-8F8A-15B7FCF75040}C:\dcs world\bin\dcs.exe

DisplayName : DCS

Description : DCS

DisplayGroup :

Group :

Enabled : True

Profile : Private, Public

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : DeferToUser

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : {5C0BB100-7A13-46B5-88D2-90B66CDD33D1}

DisplayName : DCS

Description :

DisplayGroup :

Group :

Enabled : True

Profile : Any

Platform : {}

Direction : Outbound

Action : Allow

EdgeTraversalPolicy : Block

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

[Flappie]

Good! So it seems that you simply need to allow the openbeta executable to fix your issue (well, I hope so).

 

 

I'll tell you how to do it in a couple of hours.

[Flappie]

EDIT: Wow. I don't know how I did it, but now I have your exact same problem: openbeta won't reach the update server... :cry::megalol: Standby...

Edited September 8, 2020 by Flappie

[Flappie]

Hey, I've just fixed my issue and I think you can fix yours. I simply reset my firewall settings. It was a bit scary but now I can update openbeta again. :)

 

Press Win key, type "firewall" and hit Enter.

Click "Restore defaults"

Click "Restore defaults" (again).

Click "Yes".

 

Now, everytime an app will need access through the firewall, it will ask you so, just like if you'd have just reinstalled Windows.

 

Let us know if it works for you like it worked for me.

[341-Ces]

Hey, I've just fixed my issue and I think you can fix yours. I simply reset my firewall settings. It was a bit scary but now I can update openbeta again. :)

 

Press Win key, type "firewall" and hit Enter.

Click "Restore defaults"

Click "Restore defaults" (again).

Click "Yes".

 

Now, everytime an app will need access through the firewall, it will ask you so, just like if you'd have just reinstalled Windows.

 

Let us know if it works for you like it worked for me.

 

LOL, if you were stucked with the same problem I would have felt sorry.

 

Unfortunately, reseting the firewall settings didn't change anything.

 

Now the situation is the same as previous one:

PS C:\> Get-NetFireWallRule -Displayname "dcs"

 

 

Name : {13444A44-4444-4F0E-950A-FC01D922AFCB}

DisplayName : DCS

Description :

DisplayGroup :

Group :

Enabled : True

Profile : Private

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : Block

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : {7E1E1F1E-720B-44D6-AF1E-37F6B2B7A20D}

DisplayName : DCS

Description :

DisplayGroup :

Group :

Enabled : True

Profile : Private

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : Block

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : {670E175D-ED3F-46DE-A562-9EDB2FCA1C9F}

DisplayName : DCS

Description :

DisplayGroup :

Group :

Enabled : False

Profile : Domain

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : Block

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

 

Name : {BEC8FF0E-9FB3-47D5-A024-830508264B27}

DisplayName : DCS

Description :

DisplayGroup :

Group :

Enabled : False

Profile : Domain

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : Block

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

[Flappie]

You're not supposed to have custom firewall rules once you reset. How come these keep showing up?

 

You can try resetting your firewall to default using one of these 5 methods.

[341-Ces]

Ok, I tried all of the methods in sequence (yes I know just one is enough - just to make sure)

 

Still update is not possible with the same error.

 

PS C:\WINDOWS\system32> Get-NetFireWallRule -Displayname "dcs"

Get-NetFireWallRule : No MSFT_NetFirewallRule objects found with property 'DisplayName' equal to 'dcs'. Verify the

value of the property and retry.

At line:1 char:1

+ Get-NetFireWallRule -Displayname "dcs"

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : ObjectNotFound: (dcs:String) [Get-NetFirewallRule], CimJobException

+ FullyQualifiedErrorId : CmdletizationQuery_NotFound_DisplayName,Get-NetFirewallRule

 

 

I might try reinstalling all network adapter drivers ... I dont know. I am out of energy.

 

By the way.. anyone here knows Anatoly Zhavoronkov from Eagle Dynamics Support Team?

He is not responding the ticket I created since 12th August. I am worrying about his health and I hope he is doing okay.

[Flappie]

Ok, I tried all of the methods in sequence (yes I know just one is enough - just to make sure)

 

Still update is not possible with the same error.

This error message is normal. It means you were able to purge all "dcs" labeled rules. It's a good thing.

 

But I thought you would then be able to download open beta updates...

I'm running out of ideas... :huh:

 

 

Can you please retry logging the firewall when trying to update?

If the firewall keeps dropping packets, you can try this procedure to know which rule it is.

Edited September 9, 2020 by Flappie

[341-Ces]

This error message is normal. It means you were able to purge all "dcs" labeled rules. It's a good thing.

 

But I thought you would then be able to download open beta updates...

I'm running out of ideas... :huh:

 

 

Can you please retry logging the firewall when trying to update?

If the firewall keeps dropping packets, you can try this procedure to know which rule it is.

 

OHH

MY

GOD!

 

First of all, thank you for the guidance above.

 

I am getting close to the end.

 

1) I checked if there are still dropped packages? YES THERE ARE!

 

2) I enabled audit for windows filtering platform (after some struggling I managed it - link here for future references)

 

3) I found out that:

a. The Windows Filtering Platform has blocked a packet.

b. The Windows Filtering Platform has blocked a connection.

c. The Windows Filtering Platform has blocked a packet.

d. The Windows Filtering Platform has blocked a connection.

e. ...and so on...

 

4) Checked the filterID. It was: 69575

 

5) I was like `I HATE YOU ID:69575, I`M GONNA GET YOU IN A MINUTE ID:69575 !!!!`

 

6) I searched for that ID in the log file (wfpstate.xml)

 

7) Whaaaaat!?!?! Item name is Avast! WFP Filter: FWPM_LAYER_ALE_AUTH_RECV_ACCEPT_V4

 

8 ) My fingertips were pounding my keyboard searching if I really have Avast installed?

 

9) (My LCD was shaking) open search bar, entered AVAST - got nothing?! But how?

 

10) open add/remove programs menu, searched for AVAST - got nothing?

 

11) A software was blocking my DCS Openbeta which I LITERALLY didn't installed.

 

12) Is it possible? Ok I remember installing AVAST once, but I DID uninstall it, because of reasons....

 

13) But after some time that software returned for revenge!

 

14) Now my mission is to remove, to delete, to disintegrate each and every little part of AVAST out of my computer.

 

I hope my next post in this topic would include a screenshot of me flying gently over Syria with my up to date flying simulator.

[Flappie]

Excellent, and thank you for the link! Now, all you need to do is remove all Avast rules. I thought they would have be gone after the firewall resetting though. :huh:

 

Here's how to hunt down Avast rules, in Powershell:

Get-NetFirewallRule -DisplayName "*avast*"

And if you find them, here's how to delete them:

Remove-NetFirewallRule -DisplayName "*avast*"

[341-Ces]

Excellent, and thank you for the link! Now, all you need to do is remove all Avast rules. I thought they would have be gone after the firewall resetting though. :huh:

 

Here's how to hunt down Avast rules, in Powershell:

And if you find them, here's how to delete them:

 

search returns nothing, it is not within the firewall rules. It is somewhere else.

[Flappie]

You can try this official Avast uninstall tool.

[SkateZilla]

Always

Turn off AV Suites on Game Drives and Directories.

[341-Ces]

Yes Yes Yes Yes!

 

Avastcleaner did the work properly and now I have got rid of all the remainings.

 

Now it's time to fly and chill :pilotfly:

 

Thank you @silverdevil

Thank you @MadDog-1C

Thank you @c0ff

Thank you @SkateZilla

And biggest thanks to you @Flappie

:thumbup:

[Flappie]

Yeepee!!! Fly safe.:smilewink:

[fibola]

hi,

ive just finished installed new windows 64bit on my pc and since then im tring to install new copy of DCS .

my machine is not new and im running DCS for years, and it just couple of crushing issues i had lately i decicded to reinstall everything from scratch.

 

since then DCS installation stuck all the time and i getting the same error. 

i tried to installed the module by slices and all the modules where eventually installed but i cant get the maps to installed without this error to pop up.

i still didnt install any antivirus or other security software and since i notice that in this thread the remaining avast was the issue i disable windows defender but with not luck.

 

anyone can help in here ?

 

many thanx.

 

attached is the log file i got. 

autoupdate_log.txt

[silverdevil]

@fibola try this

 

https://forums.eagle.ru/topic/240409-curl-error-6-couldnt-resolve-host-name/