// OFFICE FILE SHARING
Windows 11 keeps asking for network credentials to access a shared folder
You click the shared folder, the same grey box appears, you type the same password, and tomorrow morning it asks again. It is one of the most common jobs we get called about in small Dorset offices, and it is almost never a fault with the network. It is Windows failing to work out who you are on the other computer, or failing to hold on to the answer once you have given it. Here is what the box is really asking, what to type in it, and how to make it stop coming back without weakening your office network. Rated 4.9 on Google.
- ● No fix, no fee
- ● Rated 4.9 on Google
- ● Trading since 1995
/01 — WHY IT ASKS
What the Enter network credentials box is actually asking for
The box marked Enter network credentials is not an error message. It is Windows telling you, fairly politely, that it does not know who you are on the other computer.
When you open a shared folder, your PC connects to the machine hosting it and has to prove you are allowed in. It offers the details you are already signed in with — your username and password on your own computer. If the hosting machine has an account with exactly the same username and the same password, you are let straight through and no prompt ever appears. If it does not, there is nothing sensible to fall back on, so Windows stops and asks you.
Older versions of Windows would quietly drop to a guest connection at that point, which is why a folder that opened without any fuss on an old office PC now demands a login. Current Windows will not do that by default, because guest access means anyone who can reach the network can read the files.
Two useful things follow. First, this is a question about accounts, not about cables, WiFi or the folder itself — if the machine were genuinely unreachable you would get a very different message. Second, typing the right details once should be the end of it. If you are typing them every morning, either what you are typing is not quite right, or Windows is not keeping it. The rest of this page deals with both.
/02 — THE USERNAME BOX
The username format that trips almost everyone up
Most repeat prompts come down to the username box. Windows accepts whatever you type, sends it, gets refused, and puts the box back in front of you. The message you get back is usually no more helpful than ‘the user name or password is incorrect’, which does not tell you that the username was in the wrong format rather than simply wrong.
A bare name like sarah is ambiguous. Windows may send it qualified with your own computer’s name, which the machine at the other end has no way to authenticate, so it is refused. Naming the machine explicitly removes the guesswork. In a small office with no server, the account you need exists only on the machine that owns the share, so that is the one to name. The format is the computer name, a backslash, then the username on that computer — for example OFFICE-PC\sarah.
Getting that name exactly right matters more than it sounds. The name on the sign-in screen is a display name, and the folder under C:\Users is often a shortened version of it, so neither is reliable evidence. On the computer hosting the share, sign in as the account you intend to use over the network, open Command Prompt from the Start menu and type whoami. It prints the computer name and the local account name in precisely the form the credentials box wants — but only for whoever is signed in at that moment, so on a machine signed in as someone else it hands you the wrong account. If the computer name is all you need, hostname prints that on its own.
There is one big exception. If the hosting computer is signed in with a Microsoft account rather than a local account, the name it expects is normally the Microsoft account email address with that account’s password, and some setups want it written as MicrosoftAccount\ followed by the email. whoami will not show you that email either; it prints the shortened local profile name instead. That mismatch catches out a great many people, and it is the main reason we suggest keeping a plain local account on whichever machine holds the shared files. One last detail: an account with no password at all cannot normally be used over the network, because by default Windows only lets a blank-password account sign in at the keyboard, never over the network.
/03 — CREDENTIAL MANAGER
Saving the login properly so Windows stops asking
The prompt has a tick box marked Remember my credentials. Leave it unticked and the details only survive until you sign out or restart, which is why a folder that behaved all Tuesday afternoon asks again on Wednesday morning.
Ticking it writes an entry into Credential Manager, the small vault Windows keeps for each user profile. You can also add the entry yourself before you go anywhere near the folder, which is often cleaner: open Start, type Credential Manager, choose Windows Credentials, then Add a Windows credential. Fill in the network address (the name of the computer holding the share), the username in the PCNAME\user form covered above, and the password.
The part people miss is that the entry is matched against the address you connect with. A credential saved for OFFICE-PC is not used when you type an address like \\192.168.1.20 into File Explorer, and the other way round, because as far as Windows is concerned those are two different places. If you sometimes use a mapped drive and sometimes browse by name, either save an entry for each form you genuinely use or, better, settle on one and use it everywhere.
Two more things worth knowing. The vault belongs to your Windows profile, so if two people share a PC and sign in separately, each needs their own saved entry. And if you want to see what is already stored, cmdkey /list in Command Prompt shows the lot in one go, which is far quicker than scrolling through Control Panel.
/04 — WHEN IT GOES STALE
Why a saved credential that worked for months suddenly stops
A saved credential is a copy of a password taken at one moment in time. Nothing keeps it in step with the machine at the other end, so it fails quietly and the prompt returns as if nothing had ever been saved. These are the causes we see most often:
- The password changed on the hosting computer and the saved copy did not. Windows keeps offering the old one, so you are prompted every time, and on a machine with lockout settings all those wrong attempts can lock the account out completely.
- Someone changed their PIN and assumed that changed the password. It does not. A PIN only unlocks that one device; network sign-in still uses the account password.
- A Microsoft account password was changed online, on a phone or another PC, which instantly makes every saved copy elsewhere wrong.
- The host was renamed, or its address changed because the router handed out a different one, so the stored entry no longer matches what you are connecting to.
- The account was deleted and recreated with the same name. Windows treats that as an entirely different account underneath, so permissions granted to the old one no longer apply.
The repair is the same in every case and is worth doing thoroughly rather than tidily. Delete every stored entry mentioning that machine, including near-duplicates saved against the IP address and anything left over from an old mapped drive. Restart, open the share once, enter the correct details and tick the box. One clean entry beats three competing ones, and competing entries are the usual reason a saved credential seems to be ignored.
/05 — THE PERMANENT FIX
Matching accounts, and the shortcuts that are not worth taking
If you would rather never see the box again, the tidiest arrangement in a small office without a server is to make the accounts match. Create an account on the computer holding the shared folder using the same username and the same password as the person who needs access, give that account permission on the folder, and Windows passes the details through on its own. No prompt, nothing saved, nothing to go stale — until someone changes a password, and then you change it in both places.
Where several people need the same folder, one dedicated account on the host machine, something like officefiles with a proper password, is easier to look after. Save it once in Credential Manager on each PC and you are finished. Keep it a local account rather than a Microsoft one, simply because local accounts behave predictably over a network.
What we would ask you not to do is take the advice that appears first in most forums: switch off password protected sharing, allow insecure guest logons, or turn SMB1 back on. Those do make the prompt vanish, but only by removing the check rather than answering it. On a business network that means anything connected — a visitor’s laptop, a phone on the office WiFi, an infected device — can reach files that should be private, and SMB1 in particular is the route several well-known ransomware outbreaks travelled. The prompt is doing its job; it just needs the right answer.
There is also a point where saving credentials machine by machine stops being sensible. Once more than a handful of PCs need the same files, shared storage with its own user list, or moving the files into Microsoft 365, removes the problem instead of managing it.
FAMILY-RUN SINCE 1995 · ★ 4.9 ON GOOGLE · 200+ COMPUTERS UNDER OUR CARE · NO FIX, NO FEE · SAME-DAY REMOTE SUPPORT
// GOOD QUESTIONS
Frequently asked
What username should I type in the Windows 11 network credentials box?
Not just the person name. A bare name is ambiguous: Windows may send it qualified with your own computer name, which the machine at the other end cannot authenticate, so it is refused. Name the machine holding the folder too, in the form PCNAME\username. On that computer, sign in as the account you intend to use over the network, open Command Prompt and type whoami. It prints both names in the right format, but only for whoever is signed in at the time; hostname gives the computer name alone. With a Microsoft account, the email address is usually what it wants.
Why does Windows 11 keep asking even after I tick Remember my credentials?
Usually because there are competing entries. Windows matches a saved login against the exact address you connect with, so an entry saved for the computer name is ignored when you connect by IP address, and an old mapped drive can leave a third entry behind. Open Credential Manager, remove every entry mentioning that machine, restart, then connect once and save it again. A single clean entry is far more reliable than several near-duplicates.
Where do I find Credential Manager in Windows 11?
Open the Start menu and type Credential Manager, then choose Windows Credentials. From there you can see what is stored, remove entries that are out of date, and use Add a Windows credential to create one yourself. Enter the network address as the computer name of the machine holding the share, the username in the PCNAME\user form, and the password. To list everything quickly instead, type cmdkey /list in Command Prompt.
Should I turn off password protected sharing to stop the prompt?
We would not recommend it on a business network. It stops the prompt by removing the check rather than answering it, which means any device that can reach your network can reach those files, including a visitor laptop or a phone on the office WiFi. The same applies to advice about allowing insecure guest logons or switching SMB1 back on, which is worse still given its history with ransomware. Matching the accounts up properly is a small job on a couple of machines and leaves the files protected.
Why has the saved network password suddenly stopped working?
Something changed at the other end. The most common cause is a password change on the machine hosting the folder, or a Microsoft account password changed on a phone or another PC. Changing a Windows PIN is a common red herring, because the PIN only unlocks that device while network access still uses the account password. A renamed computer, a new address from the router, or an account deleted and recreated will all do it too.
Still getting the credentials box?
We fix office file sharing for businesses across Bournemouth, Poole and Dorset, usually remotely without anyone leaving their desk. Call 01202 775566.
01202 775566 · help@365techies.co.uk · MON–FRI 9AM–5PM