{"id":5874,"date":"2018-06-10T22:29:01","date_gmt":"2018-06-10T20:29:01","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=5874"},"modified":"2022-06-27T09:17:29","modified_gmt":"2022-06-27T07:17:29","slug":"microsoft-plans-a-windows-10-v1803-smbv1-fix-on-june-2018","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2018\/06\/10\/microsoft-plans-a-windows-10-v1803-smbv1-fix-on-june-2018\/","title":{"rendered":"Microsoft plans a Windows 10 V1803 SMBv1 fix on June 2018"},"content":{"rendered":"

[German<\/a>]Just a brief information for users of the Windows 10 April Update who runs into network issues with and possibly with multi-function devices (scanners using a scan to network shares). It seems that Microsoft is working on a fix for the 'SMBv1 isses' and plans to release a patch in June (patchday would be June 12, 2018). Microsoft has fixed this issue – see my addendum.<\/p>\n

<\/p>\n

Some background about the network SMBv1 issue<\/h2>\n

\"\"Microsoft had already announced since summer 2017 that support for the SMBv1 protocol in Windows 10 will expire. The abbreviation SMB<\/a> stands for Server Message Block (former names are LAN Manager or NetBIOS protocol), a network protocol for file, print and other server services in computer networks. Version 1 (SMBv1) of the network protocol designed over 30 years ago, and especially the Microsoft implementation, is considered very error-prone and security-critical (see Microsoft plans to deactivate SMBv1 in\u00a0 Windows 10 V1709<\/a> and StopUsingSMB1<\/a>).<\/p>\n

In the meantime there are SMBv2 and SMBv3, so that the use of SMBv1 in Windows networks is no longer absolutely necessary. For example, Windows Vista is no longer dependent on SMBv1 because SMBv2 is used there.<\/p>\n

What's the problem?<\/h2>\n

For new installations of Windows 10 it was at least since Windows 10 V1709 that SMBv1 was deactivated. If devices required SMBv1, the administrator had to activate SMBv1 again via Windows features (see also<\/a>).<\/p>\n

\"Windows<\/p>\n

With Windows 10 V1803, however, the 'missing SMBv1' problem has probably hit a lot of people, because this build also brings a change after upgrade. If the SMBv1 client is not used for a total of 15 days (except when the computer is turned off), Windows 10 April Update automatically uninstalls the SMBv1 client (see this Microsoft article<\/a> and my blog post Windows 10: Scanner fails after update<\/a>). But re-enabling SMBv1 in Windows 10 V1803 doesn't fix all network issues.<\/p>\n

Some changes in KB4103721, KB4100403<\/h2>\n

In May 2018 Microsoft released the updates KB4103721<\/a> (05\/08\/2018) and KB4100403<\/a> (05\/23\/2018) for Windows 10 V1803. However, after upgrading to Windows 10 V1803 or installing these updates, users of Windows 10 April Update seem to experience issues when using the SMBv1 protocol. I noticed postings in the Microsoft-Answers forums, where my hint to try to activate SMBv1 once did not bring a success. I couldn't figure it out at first. Now Microsoft has added the following paragraph in the 'Known issues' section to the two KB articles mentioned above.<\/p>\n

Some users running Windows 10 version 1803 may receive an error \"An invalid argument was supplied\" when accessing files or running programs from a shared folder using the SMBv1 protocol.<\/p><\/blockquote>\n

The site The Register<\/a> noticed that, and Microsoft wrote about the know issue within the kb articles:<\/p>\n

Enable SMBv2 or SMBv3 on both the SMB server and the SMB client, as described in KB2696547<\/a>. Microsoft is working on a resolution that will be available later in June.<\/p><\/blockquote>\n

It is correct to switch to SMBv2 or SMBv3 in your environment (clients and servers) to solve the security problem associated with SMBv1. But there are also scenarios where SMBv1 is mandatory (if a client or server, like a NAS drive, an All-in-One printer etc., which supports only SMBv1 from the firmware). Then you need to activate SMBv1 for a transition time.<\/p>\n

Some background about the SMBv1 bug<\/h3>\n

So Microsoft says, that there is an issue in SMBv1 for Windows 10 V1803. Let's see, whether we can get more details. The Register<\/a> has a possible hint, pointing to a MSDN forum discussion. Within the thread RS4:1803]Windows 10 1803 won't run ODBC SQL connected application from network<\/a>, there are more details. The thread creator wrote:<\/p>\n