Share via

Folder sharing with Microsoft accounts doesn't work reliably Windows 10 onwards

Anonymous
2022-12-18T16:38:33+00:00

Hello everyone,

I have a desktop PC running Windows 10 Pro 22H2 (let's call it the server). I am logged into the server with a Microsoft account and sharing a folder. I access this folder from a 11 Pro 22H2 (aka client) where I am logged in with the same Microsoft account.

I mapped a persistent network drive on the client with "net use * \server\share /persistent:yes". I expect this mapping to work all the time however it is flaky. The share works fine when I first set it up and enter my credentials (Microsoft account and password). However it fails with authorization error when the client PC wakes up from sleep. Then I have to delete and remap the drive. I don't believe even manual credentials entry should be needed because I am logged into the same Microsoft account.

  • The Microsoft account has full access to this folder in the folder sharing settings.
  • The network is set to "Private" on the server.
  • Password protected sharing is disabled on the server.

I have been using SMB file sharing for 20 years going back to Windows XP with local accounts and NTLM auth, and it was always rock solid when the user name and password were the same on both the client on the server. However I don't find the SMB integration with Microsoft accounts to be as reliable. Is anyone else seeing the same?

Windows for home | Windows 10 | Files, folders, and storage

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2022-12-18T17:19:52+00:00

    Hi there
    This is Tamal trying to help you with the issue.
    You may turn on the password protected sharing and use your profile name of the server as username (not Ms account user name) & MS account password in the client to access the folder. Save your credential in the client PC to save time during subsequent use.

    Was this answer helpful?

    0 comments No comments