How to Check SMB Signing in Windows 11

Monday, September 28, 2026

Learn how to check SMB signing in Windows 11 using PowerShell and verify SMB client and server security settings.

SMB signing is an important security feature used by Windows to help protect network file-sharing traffic from tampering and certain relay or spoofing attacks. If you regularly access shared folders, NAS devices, Windows file servers, or other SMB-compatible systems, checking SMB signing can help you understand how your connections are protected.

Windows 11 provides several ways to inspect SMB signing behavior, but PowerShell is one of the most useful methods because it exposes the SMB client and server configuration directly. You can also inspect active SMB connections and compare the signing requirements on both sides of a connection.

In this guide, you will learn how to check SMB signing in Windows 11, understand RequireSecuritySignature, inspect client and server settings, check active SMB connections, troubleshoot compatibility problems, and understand how SMB signing relates to SMB dialects, encryption, and other SMB security features.

What Is SMB Signing?

SMB signing is a security mechanism that adds a cryptographic signature to SMB messages exchanged between a client and server. The signature helps the receiving side detect whether SMB data was modified while traveling across the network.

This is different from SMB encryption. SMB signing primarily provides message integrity and helps authenticate the communicating parties, while SMB encryption protects SMB data from being read by unauthorized parties during transmission.

For example, imagine a Windows 11 PC accessing a shared folder on another computer. SMB signing can help the client and server detect tampering with SMB messages during the communication.

SMB signing is therefore particularly relevant when troubleshooting network security, compatibility with older devices, and connections to third-party SMB servers.

Why Should You Check SMB Signing?

Checking SMB signing can be useful for several reasons.

Verify whether SMB signing is required on the client.
Verify whether SMB signing is required on the server.
Troubleshoot connections to older NAS devices.
Investigate SMB compatibility problems after a Windows update.
Understand SMB security settings on a file server.
Verify settings before changing SMB security policies.
Compare SMB configurations between multiple Windows computers.

SMB signing became particularly important with Windows 11 version 24H2. Microsoft documents changes in SMB signing behavior for Windows 11 24H2, making it important to understand the current configuration rather than assuming older Windows behavior still applies.

How SMB Signing Works

When SMB signing is required, SMB messages are signed using security information established during the SMB session. The receiving side can verify the signature to detect whether the message has been altered.

There are two important directions to understand:

Outbound SMB signing: signing traffic sent by an SMB client.
Inbound SMB signing: signing traffic received by an SMB server.

On a Windows computer that acts as both a client and a server, these settings can be relevant at the same time.

This distinction is important when troubleshooting. A computer may be configured to require signing for outgoing SMB connections while its server component has a different requirement for incoming connections.

Before You Start

Most of the commands in this guide use PowerShell and the built-in SMB management cmdlets available in supported Windows editions.

For configuration changes, open PowerShell with administrator privileges. For simply viewing many SMB settings, standard PowerShell may be sufficient, but using an elevated PowerShell window is recommended when following a complete troubleshooting workflow.

To open PowerShell as administrator:

Open the Start menu.
Search for PowerShell.
Right-click Windows PowerShell or Windows Terminal.
Select Run as administrator.
Approve the User Account Control prompt if requested.

How to Check SMB Client Signing in Windows 11

The SMB client controls outbound SMB connections from your Windows 11 computer. You can check whether the client requires SMB signing with the following command:

Get-SmbClientConfiguration | Format-List RequireSecuritySignature

You can also use the shorter form:

Get-SmbClientConfiguration | FL RequireSecuritySignature

A result such as:

RequireSecuritySignature : True

indicates that the SMB client is configured to require security signatures.

If the result is:

RequireSecuritySignature : False

the client is not configured to require SMB signing through that setting.

This setting should not be interpreted as simply meaning that every current SMB connection is unsigned when it is set to False. SMB signing behavior depends on the negotiated connection and the requirements of the client and server.

How to Check SMB Server Signing in Windows 11

If your Windows 11 computer provides shared folders to other computers, it can also act as an SMB server. You can check the server-side signing requirement with:

Get-SmbServerConfiguration | Format-List RequireSecuritySignature

Or:

Get-SmbServerConfiguration | FL RequireSecuritySignature

If you see:

RequireSecuritySignature : True

the SMB server is configured to require signing for inbound SMB communication.

A value of False means the server is not configured to require SMB signing through this setting.

Microsoft documents these PowerShell commands as the supported way to verify SMB signing requirements on the SMB client and server.

Check Both SMB Client and Server Settings

On a Windows 11 computer that is used for both network access and file sharing, it can be useful to check both settings.

Get-SmbClientConfiguration | FL RequireSecuritySignature

Get-SmbServerConfiguration | FL RequireSecuritySignature

This lets you quickly determine whether the computer has different signing requirements for outbound and inbound SMB traffic.

For example:

SMB Client
RequireSecuritySignature : True

SMB Server
RequireSecuritySignature : True

This indicates that both the client and server components require SMB signing.

How to Check the Full SMB Client Configuration

If you want more context, display the complete SMB client configuration:

Get-SmbClientConfiguration

You can then look for properties related to signing, encryption, Multichannel, guest access, caching, and other SMB client behavior.

For a more focused view, use:

Get-SmbClientConfiguration | Select-Object RequireSecuritySignature, EnableSecuritySignature, EnableMultichannel

The exact properties exposed can vary with the Windows version and SMB implementation, so viewing the complete configuration can be useful when troubleshooting a particular system.

How to Check the Full SMB Server Configuration

For a Windows 11 PC that hosts shared folders, use:

Get-SmbServerConfiguration

To focus on security-related settings, you can use:

Get-SmbServerConfiguration | Select-Object RequireSecuritySignature, EnableSecuritySignature, EncryptData, RejectUnencryptedAccess

This provides a useful overview when investigating the relationship between SMB signing and SMB encryption.

How to Check SMB Signing on Active Connections

Checking the configuration tells you what the client or server is configured to require. You may also want to inspect active SMB connections.

First, display current SMB client connections:

Get-SmbConnection

This command retrieves SMB connections established from the SMB client to SMB servers. Microsoft documents fields such as server name, share name, user name, dialect, and the number of open files for SMB connections.

For a more detailed view, use:

Get-SmbConnection | Format-List *

This can expose additional properties available from the SMB connection object on your Windows version.

You can also focus on useful connection information:

Get-SmbConnection | Select-Object ServerName, ShareName, UserName, Dialect, NumOpens

This is especially useful when combined with the SMB dialect information from our guide on How to Check SMB Dialect in Windows 11.

Check SMB Sessions on the Server

If the Windows 11 computer is acting as an SMB server, use:

Get-SmbSession

This command displays SMB sessions currently established between the server and connected clients.

For more information about a specific session, you can use:

Get-SmbSession | Select-Object SessionId, ClientComputerName, ClientUserName, NumOpens

For complete session information:

Get-SmbSession | Format-List *

This is useful when investigating which computers are currently connected to a Windows 11 shared folder.

SMB Signing vs SMB Encryption

SMB signing and SMB encryption are related but serve different purposes.

Feature	Primary Purpose
SMB Signing	Helps protect message integrity and detect tampering.
SMB Encryption	Protects SMB data from being read during transmission.
SMB Dialect	Identifies the SMB protocol version negotiated by client and server.
SMB Multichannel	Allows SMB to use multiple network paths when supported.

These features can work together. For example, a connection can use a modern SMB dialect while also using signing and encryption, depending on the capabilities and requirements of the client and server.

SMB Signing and SMB 3.1.1

SMB 3.1.1 introduced important security capabilities, including pre-authentication integrity. This makes the negotiated SMB dialect relevant when analyzing SMB security.

If you have already checked the SMB dialect of an active connection, you can compare that information with the client and server signing configuration.

Use:

Get-SmbConnection | Select-Object ServerName, ShareName, Dialect

Then check:

Get-SmbClientConfiguration | FL RequireSecuritySignature

This provides two different pieces of information: the protocol dialect being used by the connection and the signing requirement configured on the SMB client.

SMB Signing in Windows 11 24H2

Windows 11 version 24H2 introduced significant SMB security changes. Microsoft documents SMB signing as required by default for Windows 11 24H2, with edition-specific behavior documented for current Windows releases.

This change can affect connections to older NAS devices, third-party SMB servers, workgroup systems, and devices that do not support SMB signing.

If an SMB connection suddenly stops working after a Windows update, do not immediately disable SMB signing. First determine whether the remote device supports modern SMB security requirements.

Microsoft specifically recommends addressing compatibility by enabling SMB signing on the remote server or updating/replacing devices that do not support the required security features rather than disabling SMB security as a workaround.

How to Troubleshoot SMB Signing Problems

If you cannot access a network share, start by checking the client signing requirement:

Get-SmbClientConfiguration | FL RequireSecuritySignature

Then check the active SMB connection:

Get-SmbConnection | Format-List *

If you control the remote Windows server, check its SMB server configuration:

Get-SmbServerConfiguration | FL RequireSecuritySignature

Also verify the SMB dialect:

Get-SmbConnection | Select-Object ServerName, ShareName, Dialect

If the problem involves a NAS or third-party SMB server, check whether the device supports SMB signing and which SMB versions it supports.

You should also verify other parts of the Windows network configuration, including the network profile, Network Discovery, File and Printer Sharing, and firewall settings.

For related troubleshooting, see:

How to Check SMB Client Configuration Together With Signing

Because SMB signing is only one part of SMB security, it can be useful to inspect the complete client configuration.

Get-SmbClientConfiguration | Format-List *

You can also save selected information for comparison:

Get-SmbClientConfiguration |
Select-Object RequireSecuritySignature, EnableMultichannel |
Export-Csv "$env:USERPROFILE\Desktop\smb-client-security.csv" -NoTypeInformation

This can be useful when comparing multiple Windows 11 computers during network troubleshooting.

Should You Disable SMB Signing?

Disabling SMB signing should not be the first troubleshooting step simply because an older device cannot connect.

Microsoft notes that disabling signing can reduce security and recommends addressing compatibility by improving the remote SMB server or replacing outdated devices where appropriate.

Before making a change, identify the affected device, determine which SMB dialect it supports, check whether it supports signing, and determine whether the device can be updated.

If you manage a business network, document any exception before changing SMB security requirements.

How to Enable SMB Signing With PowerShell

If you need to explicitly require SMB signing, Microsoft documents the following PowerShell commands.

For outbound SMB client connections:

Set-SmbClientConfiguration -RequireSecuritySignature $true

For inbound SMB server connections:

Set-SmbServerConfiguration -RequireSecuritySignature $true

These commands change SMB security configuration, so they should be used carefully in environments containing older SMB clients, NAS devices, or third-party servers.

After making a configuration change, verify the resulting setting:

Get-SmbClientConfiguration | FL RequireSecuritySignature

And, if applicable:

Get-SmbServerConfiguration | FL RequireSecuritySignature

Useful SMB Signing Commands

Command	Purpose
`Get-SmbClientConfiguration`	View SMB client settings.
`Get-SmbServerConfiguration`	View SMB server settings.
`Get-SmbConnection`	View active SMB client connections.
`Get-SmbSession`	View active SMB server sessions.
`Set-SmbClientConfiguration`	Modify SMB client configuration.
`Set-SmbServerConfiguration`	Modify SMB server configuration.

Frequently Asked Questions

What does RequireSecuritySignature mean?

RequireSecuritySignature indicates whether the SMB client or server requires SMB signing for the corresponding traffic direction.

How do I check SMB signing in Windows 11?

For the SMB client, run Get-SmbClientConfiguration | FL RequireSecuritySignature. For the SMB server, run Get-SmbServerConfiguration | FL RequireSecuritySignature.

Is SMB signing the same as SMB encryption?

No. SMB signing helps verify message integrity and protect against certain attacks, while SMB encryption protects SMB data from being read during transmission.

Does Windows 11 24H2 require SMB signing?

Windows 11 24H2 introduced SMB signing requirements by default. The exact behavior can depend on the Windows edition and current configuration, so checking the actual system settings is recommended.

Can SMB signing cause compatibility problems?

Yes. Older or third-party SMB servers that do not support signing can have compatibility problems when connecting from a Windows system that requires SMB signing.

Should I disable SMB signing if my NAS cannot connect?

Do not treat disabling signing as the first solution. Check the NAS firmware, SMB version, signing support, and available security settings first. Updating the device may provide a better long-term solution.

How can I check the SMB dialect and signing together?

Use Get-SmbConnection to inspect active SMB connections and their dialect, then use Get-SmbClientConfiguration to inspect the client signing requirement.

Related Windows 11 SMB Guides

Final Thoughts

Checking SMB signing is a useful part of diagnosing Windows 11 network file-sharing and security issues. PowerShell makes it possible to inspect both SMB client and server requirements without relying only on graphical configuration tools.

The most important commands to remember are Get-SmbClientConfiguration, Get-SmbServerConfiguration, Get-SmbConnection, and Get-SmbSession.

For a complete SMB troubleshooting workflow, do not look at signing in isolation. Check the SMB dialect, client and server configuration, Multichannel, share permissions, network profile, firewall, and active SMB sessions as well. This gives you a clearer picture of why a network share works, fails, or behaves differently between Windows 11 computers and other SMB devices.