Search the Community
Showing results for tags '1803'.
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)