Microsoft decided to discontinue the use of the network protocol SMBv1 (Server Message Block Version 1) back in 2014. This protocol was replaced by newer and more secure versions, namely SMBv2 and SMBv3. In line with this, Microsoft has gradually removed SMBv1 from its current operating systems with updates like Windows Server 2016 and Windows 10 (Fall Creators Update).
While SMBv1 is considered outdated and less secure, some specific environments still require it. If you are in such a scenario and need to enable SMBv1 on your Windows 10 system, I will guide you.
It’s important to note that enabling SMBv1 should be done cautiously and only if necessary, as it poses potential security risks. With that in mind, let’s enable SMBv1 in Windows 10, ensuring you take the appropriate precautions.
Re-enable SMB1 in Windows 10
Despite Microsoft’s recommendation to discontinue using SMBv1 for security reasons, the reality is often quite different. Many situations arise where older NAS systems or printer/scanner combinations rely solely on SMBv1. These devices may not have been updated to support the newer SMBv2 protocol.
As an administrator, you understand the importance of security. However, it can be challenging to convince others to replace these devices. The common phrases “It still works…” or “It’s only 10 years old…” are often heard, disregarding the potential security risks associated with using outdated protocols.
In this case, unfortunately, you have no choice but to SMB1 to activate in Windows 10. Fortunately, the whole thing works quite quickly via PowerShell:
Enable-WindowsOptionalFeature -Online -FeatureName smb1protocolAnswer the subsequent question with “Yes” and restart the computer – SMBv1 is already available on the system again (client and server version).
Notes on SMBv1 in Windows 10 / Server 2016
If SMB1 is re-enabled in Windows 10, you should always be aware that the protocol is outdated and malware already exists that exploits security holes in this protocol (e.g. Cryptotrojan Petya 2).
On Windows 10, the SMBv1 client is still activated when upgrading to the Fall Creators Update or when performing a fresh installation. However, Windows will uninstall the log if it has not been used for 15 days. In Windows Server 2016, neither the SMBv1 client nor the SMBv1 server is installed by default after a fresh installation. Whether client or server, the SMBv1 protocol can also be reactivated later in all Windows versions using the above command.
Error messages indicating missing SMBv1 support:
- The specified network name is no longer available.
- Unknown error 0x80004005
- System error 64
- The specified server cannot perform the requested operation.
- Error 58 (e.g. Kyocera devices with SMB scan)
Additional information from Microsoft Is there … here.
