Windows 10: Computers can't see each other after upgrade to 1803 Solved

Page 10 of 10 FirstFirst ... 8910

  1. Posts : 5,857
    Windows 10 Pro X64 16299.192
       4 Weeks Ago #91

    Prefer IPv4 over IPv6 doesn't help with the connectivity problem, at least not for me. SO far nothing has helped.
      My ComputersSystem Spec

  2.    1 Week Ago #92

    For everyone's information

    Just had a client that got back to me with this from the accounting software people he uses acknowledging that microsoft have a problem

    Finally some answers

    Hope this info can help people get to the bottom of this issue.... apologies if this info is already available I haven't got time to go through the whole thread

    With regards to your re-occurring data corruption issues you have encountered recently, we've found that Microsoft have confirmed that they have received multiple reports of problems accessing database servers from within applications after updating Windows 10 to the latest version 1803. This same issue is being reported in DataFlex, VB6, VB.NET, Delphi, and other languages as well.

    The Version 1803 issue in detail

    It appears that Microsoft has introduced a bug or security feature that prevents applications started from SMB v1.x network shares from making network connections. This means that applications started from these environments can’t open a connection to a database server. In fact, they can’t perform any other types of network calls either.

    This problem most commonly occurs when Windows 10 clients access a custom application from a mapped drive on Windows Server 2003. Unfortunately, there doesn’t appear to be a way to upgrade Windows Server 2003 to use a newer version of the SMB protocol. The only workaround in this environment is to copy the application executable to a local disk and run it from there.

    We’ve also seen this occur where clients have a Linux-based NAS that they use via a mapped drive to start their application. On most of these devices, it’s possible to upgrade the version of the SMB protocol that is served by the NAS.

    There are also some reports that in this same scenario (executable started from SMBv1 share), command line parameters are not always accessible within the application. We haven’t yet confirmed this ourselves, but we’re closely watching these issues and will update this post if and when more information becomes available.

    How to fix the issue

    Update 2018-05-15: There have been multiple reports that installing Avast Free Antivirus seems to fix the issue points to the issue being related to a Windows Defender engine update that was pushed out with Version 1803. By installing an alternate antivirus, Windows Defender is disabled, resolving the issue. This might be a stopgap measure for companies stuck on a Windows Server 2003 setup.

    For newer versions of Windows Server or Linux, upgrading from SMB v1.x to SMB v2.x or v3.x also fixes the issue. There's been no official word on the reason for this change, so it's still possible that it is a bug rather than a new security measure.

    Update 2018-06-04: Microsoft has acknowledged this issue. They haven’t outright called it a bug, but it is being treated as a “hot issue”. This is a term Microsoft has used for over a decade to refer to breaking issues that are not yet rectified. Most people being affected by this issue have settled on upgrading the version of SMB used on their system. Unfortunately, many are stuck on Windows Server 2003 for a variety of reasons. For these, running their software locally seems to be the easiest solution. A powershell script can be used that copies the executable locally and then runs it and cleans up after the app has closed (you’ll need to adjust the network path and executable name to make this work for you):

    powershell -Command "Copy-Item '\\vmxp\test\putty.exe' $env:TEMP ; Start-Process -FilePath ($env:TEMP + '\\putty.exe') -WorkingDirectory '\\vmxp\test\' -Wait ; Remove-Item ($env:TEMP + '\\putty.exe')"

    This only works where there is a single monolithic executable though, and can cause issues in some applications. YMMV. We will continue to update this blog post as new information, workarounds, or finally a solution becomes available.

    Update 2018-06-13: User Murray3 has discovered how AVG/Avast! fixes the issue. Apparently it’s related a File System Filter Driver which is part of the mechanism that antivirus applications use to do realtime scanning of files. The workaround that Murray3 has developed unfortunately requires making use of copyright protected files from the Avast! installer, so we can’t advise this workaround as a permanent solution, but if you’re in a pinch…

    But even more encouraging is that Microsoft has now acknowledged that a fix is currently in the works:

    Hopefully we’ll have a permanent fix from Microsoft in the next few weeks.

    Update 2018-06-26: As promised, Microsoft has released an update to fix this issue. In our internal testing it completely rectifies the issue.

    Based on the above this suggests that the following Windows update should correct this issue,

    Further to the above, can you please answer the following points:
      My ComputerSystem Spec

Page 10 of 10 FirstFirst ... 8910

Related Threads
Hi Guys, I've had many problems with sharing since the 1709 update - was fine before that. Now I've upgraded my PCs to 1803, more issues (Thanks MS)... I've shared the "D:" data partitions on my three PCs, with full access for everyone,...
I have a Hauppauge WintTV-HVR-2255 that was working fine before the Windows 10 1803 update. The digital ATSC tuners work fine, but the analog tuners (and the analog inputs) have stopped working. When I scan for the inputs using NextPVR I get an...
After upgrade to 1803 my microphone is not working properly. I googeld and found many times this answer: Hit Windows key and search for "microphone privacy settings" Hit "Allow access to the microphone on this device" Switch "Allow apps to...
After upgrade, my computer is unusable. I have the same problem as here: /installation-upgrade/109176-1803-upgrade-fault-c-windows-system32-config-systemprofile-destop.html#post1360304. Nothing works, just the run...
Found problems The apple airport printer can't print Network Center can't click out 'Change adapter settings', so you can't disable a connection
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 02:28.
Find Us