Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 0x80070032

0x80070032 and SMB1 shares: why old NAS boxes stop working in Windows

11 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

0x80070032 is Win32 50, ERROR_NOT_SUPPORTED, “The request is not supported”. On a file share it usually means the two ends have no protocol version in common, because the device speaks only SMB1 and modern Windows does not offer it. This is an old device meeting a deliberate change, not a fault to repair on the client.

Run these on the client, in an elevated PowerShell

Get-SmbConnection
Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol
Get-SmbClientConfiguration | Select-Object RequireSecuritySignature, EnableSecuritySignature
  1. Read the Dialect column from Get-SmbConnection. It tells you what the client is negotiating with everything it can still reach, which is your baseline.
  2. Look in the device’s own administration pages for a file sharing or SMB setting, and see whether a maximum or minimum protocol version can be raised.
  3. Apply any firmware update the manufacturer still offers, then look again. On a great many devices the setting only appears after an update.
  4. If the device also relies on unauthenticated access, expect a second refusal about guest access even after the dialect question is settled. Create a real account on the device instead of re-enabling guest.
  5. Where nothing raises the dialect, plan to move the data rather than leaving the connection working by weakening the client.

Microsoft’s own position is to upgrade or replace third-party devices that only support the old protocol or guest authentication, rather than to relax the client. Reinstating SMB1 affects every connection that machine makes, not just the one to the old box.

If the device now negotiates a modern dialect, stop here. If it cannot, the next section is about which of the modern defaults you have actually hit.

Why it happens

When a client connects to a file server the two sides negotiate which version of the protocol to use, and the client offers only versions it is prepared to speak. Modern Windows does not offer the first one. Microsoft’s published position is unambiguous: SMBv1 is not installed by default in any edition of Windows 11 or Windows Server 2019 and later, and it is not installed by default in Windows 10 either, except on the Home and Pro editions. So the negotiation ends with nothing in common, and the client reports that the request is not supported.

The neighbouring codes are the same conversation failing slightly differently. 0x8007003B is Win32 59, ERROR_UNEXP_NET_ERR, “An unexpected network error occurred” – broader than a session ending, and it will not tell you which layer gave up. 0x8007054F is Win32 1359, ERROR_INTERNAL_ERROR, “An internal error occurred”, which is what you get when the connection attempt cannot be completed cleanly and nothing more specific is available. Neither indicates a permissions problem, which is why granting rights on the device changes nothing at all.

Two other modern defaults produce a wall that looks identical from the client. Windows 11 version 24H2 and Windows Server 2025 require SMB signing by default, so a device that cannot sign is refused whatever dialect it speaks. And insecure guest logons are disabled on most current editions, which produces a refusal about security rather than about protocol. The three failures get blurred together in most advice; they have different fixes and it is worth knowing which one you have.

The device can be raised and nobody has done it

You have this one if The manufacturer’s interface has an SMB or file service setting, or newer firmware is available.

  1. Update the firmware first, then look again. The setting frequently appears only after an update.
  2. Set the maximum and minimum protocol version to the newest the device offers.
  3. Reconnect and confirm with Get-SmbConnection that the dialect is now a modern one.

This is the outcome to aim for. It costs nothing beyond the time to apply an update, and it removes the problem permanently rather than working around it.

The SMB 1.0 client is simply not present on this machine

You have this one if Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol reports the feature as not present, and the device has always needed it.

  1. Treat this as a prompt rather than a fault. Microsoft does not install this component by default on Windows 11 at all.
  2. Look for a modern route to the data before reinstating anything.
  3. If it genuinely must be reinstated for a short period, do it on the one machine that needs it rather than by policy, record why, and set a date to remove it again.

Signing requirements cannot be met

You have this one if The device supports a modern dialect but connections are still refused, and the behaviour changed with a Windows feature update.

  1. Check whether the device has a signing option in its own settings and enable it.
  2. Read the client’s current expectations with Get-SmbClientConfiguration rather than assuming them.
  3. Remember that Windows 11 version 24H2 and Windows Server 2025 require SMB signing by default, so a machine that was fine last year may not be now.
  4. Where the device cannot sign at all, that is the same conversation as the dialect: raise it, replace it, or accept the exposure knowingly.

The share only offers unauthenticated access

You have this one if The refusal mentions security rather than protocol, and the device has no user accounts configured.

  1. Create a named account with a password on the device and grant it access to the share.
  2. Connect with those credentials and save them, so the connection no longer depends on anonymous access.
  3. Leave the client’s refusal of guest connections in place. It is protecting you from connecting to something impersonating your file server.

Nothing on the device can be changed

You have this one if The manufacturer has not shipped firmware for years and there is no protocol setting anywhere in its interface.

  1. Copy the data off to a supported file server or a current NAS, ideally from a machine that still has a working connection.
  2. Retire the device from the network, or leave it isolated with no route to anything that matters.
  3. Where the data must stay available to users, present it from a file server that speaks a current dialect and can be secured properly.

Full reference

What Microsoft publishes about the defaults

Statement Where it applies
SMBv1 is not installed by default Any edition of Windows 11, and Windows Server 2019 and later
SMBv1 is not installed by default Windows 10, except the Home and Pro editions
SMB signing is required by default Windows 11 version 24H2 and Windows Server 2025
Insecure guest logons are disabled by default Windows 10 Enterprise, Pro for Workstations and Education from 1709; Windows Server 2019 and later; Windows 11 Pro from Insider build 25267
Guest authentication is allowed by default Windows 10 Home and Pro

That table is the reason two people on the same network get different results from the same appliance. A Windows 10 Pro machine and a Windows 11 machine do not start from the same defaults, and neither does a Windows 10 Enterprise build. Check the edition before you conclude that something changed on the device.

Which wall you have hit

Symptom What it points at
0x80070032 against one old device, everything else fine That device offers only the legacy dialect
A refusal mentioning security rather than protocol Guest access, signing, or both
It worked until a Windows feature update The build raised what it requires, or the legacy client is not present on the new build
Other clients on older editions still connect Those editions start from different defaults
The device offers a protocol setting in its own interface Raise it there. No client change is needed

Reading and changing the client’s own state

Command What it does
Get-SmbConnection Lists live connections with the dialect negotiated for each
Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol Reports whether the SMB 1.0 component is present
Get-SmbClientConfiguration Shows the client’s signing and other requirements
Get-SmbServerConfiguration | Select EnableSMB1Protocol Reports whether this machine’s own server component would accept SMB1
Set-SmbServerConfiguration -EnableSMB1Protocol $false Turns the server side off on this machine

If you reinstate the old protocol anyway

  • Do it on one machine, not through a policy that reaches the estate.
  • Isolate the device on the network so that machine is the only thing that can reach it.
  • Write down what you did and why, in whatever holds your build documentation, because the next person will find it enabled and not know.
  • Set a removal date, and put it in the same place. A temporary exception with no date is a permanent one.
  • Plan the replacement in the meantime rather than after the deadline passes.

Reinstating the SMB 1.0 client to keep one device working exposes every connection that machine makes, not only the one to the old device. It has no usable integrity protection and it has been the delivery route for widely destructive malware. Microsoft’s own recommendation is to upgrade or replace devices that need it.

When a licence is the actual fix

Where the appliance can be raised to a current dialect in its own interface, do that, spend nothing, and stop reading here. The licence conversation only starts when the manufacturer stopped shipping firmware years ago and the honest position is that you are keeping an obsolete protocol alive for one box. Then the fix is to serve the data from a file server that speaks the current protocol with signing and encryption, and that can be backed up, audited and patched. Arco supplies Windows Server 2022 Standard licences along with the client access licences that model requires, and can check whether your existing licence position already covers the users who would connect to it. A current NAS from a manufacturer that still ships firmware is an equally legitimate answer to the same problem, and cheaper if you do not need directory integration.

Every code this article covers

Code What it points at Source
0x80070032 Win32 50, ERROR_NOT_SUPPORTED: the request is not supported. On a share, no protocol version is common to both ends Microsoft Learn
0x8007003B Win32 59, ERROR_UNEXP_NET_ERR: an unexpected network error occurred Microsoft Learn
0x8007054F Win32 1359, ERROR_INTERNAL_ERROR: an internal error occurred Microsoft Learn
You can't connect to the file share because it's not secure Microsoft publishes no page carrying this exact wording. It appears when the client refuses on security grounds; check the dialect the target offers and whether it only permits guest access. The message Microsoft does publish for the guest case is “You can’t access this shared folder because your organization’s security policies block unauthenticated guest access” not published by the vendor

Confirm the fix worked

  1. Open the share and run Get-SmbConnection to confirm the negotiated dialect is a modern one.
  2. Confirm the SMB 1.0 optional feature is still reported as not present on the client.
  3. Reconnect after a reboot and confirm the connection is made without prompting.
  4. Copy a large file both ways to confirm the connection is usable, not merely established.
  5. If you reinstated anything, confirm the removal date is recorded somewhere that will be read.

Questions people ask about this

Can I just turn the old protocol back on and move on?

You can, and Windows will let you. Understand what you are accepting: connections with no meaningful integrity protection, on a protocol that has been the route into networks for well-known destructive malware. If you do it, do it on one machine, isolate the device, and give yourself a deadline.

Does buying a Windows Server licence fix the error itself?

No, and it should not be sold as though it does. It replaces the thing that cannot be fixed. If your device can be updated, update it and spend nothing. The licence is the answer only when the appliance is genuinely at its end of life.

Why did this start after a Windows update?

Either the build you moved to does not install the legacy client, or it raised what it requires of a connection. Windows 11 24H2 and Windows Server 2025 require SMB signing by default, which catches devices that were fine on the previous build.

My colleague on Windows 10 Pro can still connect. Why can I not?

Because the defaults differ by edition. Microsoft publishes that SMBv1 is not installed by default on Windows 10 except Home and Pro, and that guest authentication is allowed by default on those two editions. Their machine is starting from a more permissive position than yours.

Will keeping an older Windows version buy me time?

For a while, and that is the trap. The device is unsupported either way, and building a dependency on an old client just moves the same decision to a worse moment.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error RDP error 0x80090326: the TLS handshake was rejected before logon Free Fix Print jobs stuck: error 0x00000040 and a print queue that will not clear License Error Scan to folder fails with 0xC00000CC: the copier cannot reach your share Free Fix Error 0x8009030C: logon denied when NTLM is blocked or restricted
โ† Back to Knowledge Base