Recently, I found myself troubleshooting an issue with SMB connections from an Android application that connects to a Windows 10 file share via SMB. The issue I was chasing was related to the first major upgrade for Windows 10 that Microsoft has been releasing to customers over the last month. Apparently, unpublished changes in that Windows 10 upgrade are causing file sharing problems in a multitude of situations.
During the course of my troubleshooting I thought it would be useful to “fallback” to exclusively using SMBv1 on Windows 10. While Microsoft has been slowly trying to bury the v1 dialect of SMB, it’s still nice to have around for troubleshooting situations when you suspect an unpublished change to a newer dialect (e.g., v2 or v3).
Without further ado, here is a Microsoft Support article that gives you the commands needed to flip the proverbial switches of SMB in Windows.