UDPBind Failing when running apps from network share after Win10 1803 Update!

[evanevery]

An AUTOIT app just stopped running on several machines in our office after applying the recent Win10 1803 update.

Here are the details:

1.  The App is now failing the UDPBIND call with a 10022 error.

2.  The App runs fine on machines which have NOT YET applied the 1803 Win10 update just released

3.  The App fails on all machines to which the 1803 has been applied - but only if the app is loaded from a network share!

4.  If the app is run from a LOCAL drive, it continues to run fine even after the 1803 update

In summary:

Something has changed with the Win10 1803 update which now prevents AutoIT apps from opening UDP ports (UDPBIND) if the Apps are being loaded/run off a network share!

I have confirmed this by manually updating a workstation to 1803 and confirming this is what is causing the failure.  (Worked fine immediately before - now fails immediately after)

Also, I am not having issues running other Autoit network apps from network shares which DON'T use the UDPBIND call. (i.e. "DriveMapAdd" is still working under the same conditions)

The share which we have been loading/running our apps from is running SMB v1.5 protocols (via Linux/Samba)

[BrewManNH]

Is there a question?

[evanevery]

1 hour ago, BrewManNH said:

Is there a question?

No...  I'm providing this info in the event that the UDPBIND function could be updated to resolve this problem and so other folks can be aware of the issue if they too notice their network apps stop working. 

K?

[evanevery]

Another piece of information:

- While the compiled executable fails if run from a network share, the same code will run fine if run through the interpreter ("Go")...

[mLipok]

Using go... you are using exe from local drive, not from network share

[TheXman]

Windows 10 1803 added several new features to Windows Defender.  I doubt the issue has anything to do with AutoIt.  If you are using Windows Defender, it would be the first thing I would look at in trying to find the root cause.  If you are using it, I would try temporarily disabling it or at least temporarily excluding whatever folders are involved to see if it may be the culprit.

https://docs.microsoft.com/en-us/windows/whats-new/whats-new-windows-10-version-1803

Edited July 2, 2018 by TheXman
Added reference to what's new in 1803

[mLipok]

I talked about the same problem here:

 

[orbs]

and a recent Windows update is reported to have fixed the issue. i updated the details in the post linked above by @mLipok.