For server 2008R2 and windows 7, I'm afraid you could only change in the registry. This version supports AES-128 GCM encryption in addition to AES-128 CCM encryption added in SMB3, and implements pre-authentication integrity check using SHA-512 hash. SMB 3.1.1 was introduced with Windows 10 and Windows Server 2016. Windows NT 4.0 Service Pack 3 provides an updated version of the Server Message Block (SMB) authentication protocol, also known as the Common Internet File System (CIFS) file sharing protocol. For all supported IA-64-based versions of Windows Server 2008 R2 File name File version File size Date Time Platform Ntfs.sys 6.1.7600.20884 3,552,640 20-Jan-2011 07:06 IA-64 Ntfs.sys 6.1.7601.21645 3,553,152 20-Jan-2011 These worm viruses exploit a vulnerability in Windows Server Message Block (SMB) version 1 (SMBv1), and spread like wildfire. Tip: To quickly check the That way you can configure your Windows Servers to see if disabling SMB1 For more information on SMB In server 2012 and later you may use get-smbconnection to do a check. In addition, version 3 of the SMB protocol and at least Windows Server 2012 were required. We provide SMB1 usage auditing in Windows 10, Windows Server 2016, and Windows Server 2012 R2/Windows 8.1 via an update , just to be sure. protocol and block its components from loading. In server 2008R2/windows 7, the SMB connection version is SMB2.1. But with Windows Server 2019 and Windows 10 v.1809 you can now force the "direct write" from the client side. A new version of SMB 3 protocol was introduced since Windows Server 2012 R2 (technically, it is SMB 3.02, since SMB 3.0 appeared in Windows Server 2012).Now you can disable the driver of the legacy SMB 1.0 protocol and block its components from loading. It is urged you disable SMBv1 in your Windows variant (Windows 10, 8.1, Server 2016, 2012 R2), and here is how if you haven’t done so yet.