What Is Security Accounts Manager

If you’ve ever wondered how Windows remembers “who you are” and lets you log in with a password, you’re already circling the right topic. Security Accounts Manager (usually shortened to SAM) is the part of Windows that keeps the local user account credentials needed for that login process. It’s basically the local account store Windows uses to support authentication on your PC.

Security Accounts Manager (SAM): what it is in Windows

In plain terms, Windows Security Accounts Manager is a Windows database file used for local authentication. It’s often described as a critical Windows operating system database that holds user credential information for the accounts on that specific computer.

You’ll also see it referred to as:

• Security Account Manager (SAM) file (the file/database itself)
• SAM database (the data inside)
• Security Accounts Manager service (the Windows service role that handles or administers it)

Even if the names sound different, they’re pointing to the same core idea: Windows needs a local place to store account info, and SAM is that place.

What does a security account manager do?

SAM helps Windows log in by working with the local accounts on your machine.

At a high level, SAM administers the database of user and group account information stored on the computer. It also supports authentication for those local accounts, which means it helps confirm that a username and password attempt matches what Windows has stored for that account.

So when you log in to a local account on your Windows 10/11 PC, SAM is part of what makes that possible.

SAM database vs. SAM file: what the terms mean

These terms get mixed up because they’re closely connected.

• SAM database usually means the whole set of stored account data Windows uses for local authentication.
• Security Account Manager (SAM) file usually means the actual stored file on disk that contains that data.

In short:

• one is the *data* (database),
• the other is the *file* where Windows keeps it (the SAM file).

What information SAM stores (usernames and passwords / password hashes)

The big takeaway: SAM stores users’ password-related data and usernames for local accounts.

SAM is commonly described as storing password information in a protected form. Instead of keeping your password in readable text, it’s typically described as storing password hashes. A password hash is a scrambled “fingerprint” of the password that Windows can check during login.

So when people say “SAM stores passwords,” what they usually mean is:

• usernames for local accounts, and
• password-related information (often described as password hashes) used to authenticate you.

Security Accounts Manager service: how it fits in

Windows doesn’t just have a database file sitting there. There’s also a related Windows component that runs to manage and support it.

That’s the Security Accounts Manager service. It’s described as the service that administers the database of user and group account information stored on the computer.

In other words:

• SAM file / SAM database = the data store
• Security Accounts Manager service = the Windows service that handles administering that store and supporting authentication

Where is the SAM file stored?

People often search “Where is the SAM file stored” because they want to locate or understand the file inside Windows.

What the material you have supports is this: the SAM file is part of Windows’ local authentication system, meaning it’s tied to local user credential storage. However, it doesn’t provide the exact path or location.

So the safest way to think about it is:

• it’s stored as part of Windows’ internal local authentication database, and
• you don’t normally need to find it to understand how login works.

Security Account Manager (SAM) Remote Protocol: what it supports

You’ll also hear about the SAM Remote Protocol. In simple terms, it’s about how Windows can support account or credential management over a network for an account store or directory that includes users and groups.

Instead of being only “local-only,” this remote protocol topic connects SAM to the bigger idea of accounts and groups, especially how systems can communicate about account data when a network is involved.

If your goal is just “what is SAM,” you don’t need this detail. It’s mainly why search results sometimes mention the remote protocol alongside “SAM database/file/service.”

Security Accounts Manager on Windows 10 vs Windows 11 (what changes, what doesn’t)

If you’re specifically searching for Security Account Manager Windows 11, it helps to know what’s likely the same and what might differ.

What usually doesn’t change:

• The core idea stays the same: SAM is the local authentication database/file that stores username and password-related credential information for local accounts.
• SAM’s general role stays the same: it supports authentication and is tied to local user and group account data.

What might change:

• the way Windows looks around account features, the wording you see in settings, or how components are wired internally across Windows versions.

But the overall concept—Windows uses SAM to keep local credential data—remains consistent. On Windows 10 or Windows 11, you can think of SAM as Windows’ local account credential store, along with the service that administers it.

Common questions: seeing users on a PC and related terms

“How can I see all the users on my PC?”

SAM is the store that holds local user account credential information. The exact steps for “seeing all users” aren’t covered in the information you have here.

A useful way to keep it straight:

• SAM relates to *local account credential storage*.
• “Seeing users” is more about Windows’ account and UI tools that list accounts.

You don’t need to open or inspect SAM to understand that users exist on a PC—SAM is the underlying data store that supports authentication.

“Is SAM the same thing as the users I see in Windows?”

Not exactly. The users you see in Windows are “account objects” inside the system. SAM is the underlying local database/file Windows uses for credential storage for those local accounts.

“What’s the difference between SAM and the Security Accounts Manager service?”

• SAM (database/file) = where credential and account-related data is stored.
• Security Accounts Manager service = the Windows service that administers that database of user and group account info and helps support authentication.

“Does SAM relate to passwords directly?”

SAM relates to password authentication. It stores username and password-related credential information for local accounts, often described as password hashes. That’s why it’s considered a critical part of Windows local authentication.

Quick glossary (so the names stop feeling random)

• Windows Security Accounts Manager: the SAM concept inside Windows (local authentication)
• Security Account Manager (SAM) file: the stored database file holding credential info
• SAM database: the set of stored account data
• Security Accounts Manager service: the service that administers the user/group account database on the computer
• SAM Remote Protocol: how SAM-related account support can connect over a network for user/group account directories

If you’re troubleshooting Windows account or authentication questions, bookmark this and explore related Windows account and security basics on our site.