It's a bug: https://bugs.launchpad.net/gvfs/+bug/1828107
It's actually a bug that was created when they tried to fix another bug: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322
In short: Browsing for smb hosts relies on the smb1 dialect to do the discovery. But the samba client is designed to go all the way up to smb3 and when it does host discovery doesn't work. They tried to fix that by forcing the file manager down to smb1 to do the discovery but then it gets stuck there.
Windows 10 disables smb1 on the server side so access is impossible. smbclient works because to can use the defaults and access Win10 via smb3.
So there are really only 2 workarounds for this problem:
Force Win10 back to smb1 on the server side which Microsoft does not recommend.
Or do a cifs mount of each individual share which will by default use a more current smb dialect. Something like this:
sudo mount -t cifs //192.168.0.100/share-name /mount-point -o username=username,password=some-password,uid=your-ubuntu-user-name
You can set this up in /etc/fstab - with a different syntax - if you choose to go this route.
EDIT: For the credentials in plain text issue you can create a credentials file and make it accessible only to root:
[1] Create a file say at /etc/samba/credentials
[2] Make it accessible only to root: sudo chmod 0600 /etc/samba/credentials
[3] Then add your credentials to it in this form:
username=user-name
password=user-password
Then an fstab statement would look something like this:
//192.168.0.100/share-name /mount-point cifs credentials=/etc/samba/credentials,uid=your-ubuntu-user-name 0 0