Windows 10 is deprecating SMB protocol version 1, not installing server components for it by default anymore, and automatically disabling the client components for it if it does not seem to be needed. Since SMBv1 has a critical design flaw that enabled the spread of the original WannaCry ransomware worm, this is a good thing.
You should verify that your Samba configuration does not have a
server max protocol = setting (either as explicit configuration or as an implicit default setting) that will restrict Samba from using SMBv2 or SMBv3.
testparm -s --parameter-name "server max protocol" /etc/samba/smb.conf 2>/dev/null. If the response is anything that doesn't begin with either
SMB3, your Samba configuration is currently restricted to SMBv1 only.
With up-to-date versions of Samba, fixing this typically requires only removing any explicit
server max protocol restrictions from the configuration. If you have an old version of Samba that defaults to using SMBv1 only, you can probably add a
server max protocol = SMB2 or
server max protocol = SMB3 to explicitly enable the newer protocol versions. If your version of Samba does not support these configuration options, it is a really old version that should be updated as soon as practical.