This problem might be related to a Windows 10 change in local group policy to no longer allow “insecure guest logins” to SMB servers, in which case it’s also related to the type of SMB connection. When you mounted the original network drive, it was probably created as a SMB1-type (unsecure) mount and your username and password were cached and stored with it (when you make the mount persistent with stored user credentials). After the upgrade, Windows will try to re-use this cached network connection, but it will fail. As I understand it, you can work around this in a few ways:
- Re-enable insecure guest logins. See here
- Delete the network connection and create a new one e.g. using the device name \device-name. Since Windows 10 will no longer allow insecure guest logins, it will now be a SMB2+ mount. The challenge here is to make sure there are no (legacy) stored connections/automatic logins left over/stored Probably also good to ensure no credentials are saved/left over in the Credential store for the old mount.
