ClientMaxProtocol=smb2
ServerMaxProtocol=smb2
These two settings were suggested as possible solutions to the ongoing issue with samba shares and windows 10 from the windows updates in late 2017 and early 2018 that borked win10.
I tried them and plenty of others
the above didn't work and I removed them from my smb.conf
If you read the bug quoted the latest update actually fixed a misnamed config entry that enforced the above settings IF they were present.
However they had to be present and the only way for them to be present was for them to have been added manually with, notice the case, lowercase is/was not correct:
config setprop smb ServerMaxProtocol SMB2
config setprop smb ClientMaxProtocol SMB2
The latest update does what its supposed to do, enforces the smb settings
and as to what Mister MS does, mate win10 users, me, have just spent almost 12 months chasing updates to fix an issue that Mr MS introduced with one of his feature updates late last year
it has only been the most recent one that has returned the functionality that we already had !!!
Added after hitting enter: They are valid smb.conf settings for any app that needs those protocols