Prajwal Desai

SCCM | ConfigMgr | Intune | Windows 11 | Azure

  • Home
  • Cloud
    • Autopilot
    • Azure
    • Endpoint Analytics
    • Intune
    • PowerShell
    • Teams
    • Windows 365
  • Microsoft
    • Active Directory
    • Group Policy
    • SCCM
    • SCOM
    • Windows 10
    • Windows 11
    • Windows Server
    • WSUS
  • Software
  • Forums
  • Newsletter
  • Contact
Notification Show More
Latest News
Fix Windows Autopilot Reset Error 0x80070032
Fix Windows Autopilot Reset Error 0x80070032
Autopilot Intune
Windows activation error 0xc004c020
Fix: Windows Activation Error 0xC004C020 with 2 Easy Methods
Windows 11 Windows 10
Find the Package ID of SCCM Application
3 Best Ways to Find the Package ID of SCCM Application
SCCM
SCCM Updates Install Error 0x800b0109 0x8024b303
Fix: SCCM Updates Install Error 0x800b0109 | 0x8024b303
SCCM
Disable Windows Hello for Business using Intune ftimg
Disable Windows Hello for Business using Intune – Comprehensive Guide
Intune Autopilot
Aa

Prajwal Desai

SCCM | ConfigMgr | Intune | Windows 11 | Azure

Aa
Search
  • Home
  • Cloud
    • Autopilot
    • Azure
    • Endpoint Analytics
    • Intune
    • PowerShell
    • Teams
    • Windows 365
  • Microsoft
    • Active Directory
    • Group Policy
    • SCCM
    • SCOM
    • Windows 10
    • Windows 11
    • Windows Server
    • WSUS
  • Software
  • Forums
  • Newsletter
  • Contact
Follow US

Home » Windows 10 » Fix Can’t Connect to File Share Obsolete SMB1 protocol

Windows 10Security

Fix Can’t Connect to File Share Obsolete SMB1 protocol

By Prajwal Desai 2 Views 21 comments February 18, 2022 3 Min Read

While accessing a remote file share, I got the error You can’t connect to the file share because it’s not secure. This share requires the obsolete SMB1 protocol. I got this error on my Dell Precision laptop after I installed Windows 10 1903 on it.

In addition to that above error, the fix mentioned in this post also applies if you see any of the below errors while accessing file shares.

  • The specified network name is no longer available.
  • Unspecified error 0x80004005
  • System Error 64
  • The specified server cannot perform the requested operation.
  • Error 58

Obsolete SMB1 protocol

So why did I get this error ?. The reason is that SMBv1 protocol is now obsolete. Microsoft strongly advises consumers to use SMB2 or higher protocol.

In Windows 10 Fall Creators Update and later versions, the Server Message Block version 1 (SMBv1) network protocol is no longer installed by default. It is superseded by SMBv2 and later protocols starting in 2007.

- Advertisement -
Ad image

Hence due to the above reason, I got the error while accessing a share from my Windows 10 machine. Furthermore if you install Windows 10 Enterprise 1903, it no longer contains the SMBv1 client. However SMBv1 can still be reinstalled in all editions of Windows 10.

Here is the complete error message – You can’t connect to the file share because it’s not secure. This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack. Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink/?linkid=852747

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol

Cannot Connect to File Share

To quickly fix the error You can’t connect to the file share because it’s not secure :-

  • On your computer, open Control Panel. Click Programs.
  • Click on Turn Windows features on or off link.
  • Expand the SMB 1.0/CIFS File Sharing Support option. Check the box SMB 1.0/CIFS Client.
  • Click the OK button.
  • Restart the computer now.

An alternate method to enable SMB1 Protocol is via PowerShell. Here is how you do it.

On your Computer, open the PowerShell and run the below command. This command gives you details about SMB1Protocol.

Get-WindowsOptionalFeature –Online –FeatureName SMB1Protocol

You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol

Run the below command to Enable SM1Protocol on your computer.

Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

After you execute this command, you must restart your computer. After you restart, login to the computer and you shouldn’t see the file share access error again.
You can't connect to the file share because it's not secure. This share requires the obsolete SMB1 protocol

Sign Up For Weekly Newsletter

Get the most recent information on Configuration Manager, Intune, Windows 11, Windows 365, Autopilot, Azure, Software Reviews, and much more by subscribing to the newsletter.
By signing up, you agree and acknowledge the data practices in our Privacy Policy. You may unsubscribe at any time.
Share this Article
Facebook Twitter Copy Link Print
Avatar photo
By Prajwal Desai
Follow:
Prajwal Desai is a Microsoft MVP in Enterprise Mobility. He writes articles on SCCM, Intune, Configuration Manager, Microsoft Intune, Azure, Windows Server, Windows 11, WordPress and other topics, with the goal of providing people with useful information.
Previous Article Lync is becoming Skype for Business ftimg Fix Lync is becoming Skype for Business – KB3115883 (MS15-044)
Next Article Repair SCOM Agents on Windows Computers How to Repair SCOM Agents on Windows Computers
21 Comments 21 Comments
  • Avatar photo Bruce Atwood says:
    January 30, 2023 at 9:44 pm

    I follow the instructions, which appear in many posts, to use power shell to install SMB1. Below is what I get. Where can I download the SMB1 code?

    PS C:\WINDOWS\system32> Set-SmbServerConfiguration -EnableSMB1Protocol $true
    Confirm
    Are you sure you want to perform this action?
    Performing operation ‘Modify’ on Target ‘SMB Server Configuration’.
    [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is “Y”): y
    Set-SmbServerConfiguration : The specified service does not exist.
    At line:1 char:1+ Set-SmbServerConfiguration -EnableSMB1Protocol $true
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : NotSpecified: (MSFT_SmbServerConfiguration:ROOT/Microsoft/…erConfiguration) [Set-SmbServerConfiguration], CimException
    + FullyQualifiedErrorId : Windows System Error 1243,Set-SmbServerConfiguration

    PS C:\WINDOWS\system32>

    Reply
  • Avatar photo syed says:
    September 19, 2022 at 3:37 pm

    Thank you ….

    Reply
  • Avatar photo Kenny S says:
    September 6, 2022 at 9:57 am

    Thank you , Thank you, Thank you! couldn’t have figured that out in a hundred years!

    Reply
  • Avatar photo Py says:
    August 25, 2022 at 11:49 am

    Many thanks, worked perfectly. So frustrating to have to do this after so long with no fix from Synology.

    Reply
  • Avatar photo Setchp says:
    March 1, 2021 at 11:53 pm

    Thanks, worked perfectly.

    Reply
  • Avatar photo JN says:
    February 7, 2021 at 12:12 am

    Kudos!

    Reply
  • Avatar photo John YU says:
    January 25, 2021 at 3:05 am

    Hello,

    I wanted to let you know how much I appreciated the solution you posted. It saved my day! I have been trying to gain file access net ReadyNAS Duo for a few days without success.

    Simply turning on the SMB1 resolved the issue.

    Thanks again.

    Reply
  • Avatar photo jai says:
    January 5, 2021 at 7:45 am

    thnx it worked like a charm.

    Reply
  • Avatar photo Juan says:
    December 16, 2020 at 11:42 pm

    SMB1 is not even a feature anymore in the latest versions i can’t enable this.

    Reply
  • Avatar photo Dave K. says:
    November 22, 2020 at 4:09 am

    Thanks very much for this solution! I realize SMB 1 is less secure than the newer version, but this lets my Win10 PC see the older XP systems on my home network. This will do until I can find a better way.

    Reply
  • Avatar photo Kym says:
    November 14, 2020 at 6:10 am

    Thank you for this solution!

    Reply
  • Avatar photo Junior says:
    August 17, 2020 at 2:09 pm

    Great tip, it worked for me, allowing me to access an old NAS drive.

    Reply
  • Avatar photo Mike says:
    August 10, 2020 at 8:44 pm

    Found that I had to reapply this fix after Window 10 Update 2004

    Reply
  • Avatar photo jeff says:
    March 10, 2020 at 8:17 pm

    Adding SMB 1.0 to Server 2019 cleared the error joining the server to the domain. After migration I will remove SMB 1.0.

    Reply
  • Avatar photo Jeff says:
    January 16, 2020 at 11:15 pm

    This worked on Win10 Pro after overnight Win update on the bosses machine. Thank you so much!

    Reply
  • Avatar photo Mahdi says:
    December 20, 2019 at 1:41 pm

    gotta restart next Monday, thanks for the info

    Reply
  • Avatar photo Prasad says:
    December 2, 2019 at 4:20 pm

    It’s worked
    Thank you very much

    Reply
  • Avatar photo Ray ma says:
    September 20, 2019 at 5:38 pm

    Install the SMBv1 already, still not working only in 1903

    Reply
    • Avatar photo Daniel says:
      October 12, 2019 at 10:34 am

      For me in 1903 still not working

      Reply
  • Avatar photo Jamie Dickson says:
    August 13, 2019 at 6:48 pm

    Can this issue be corrected on the server side so you don’t need to install SMBv1 on the client computer?

    Reply
    • Avatar photo Zham says:
      December 3, 2019 at 9:46 pm

      My thoughts exactly!

      How can we configure the share to be “secure” so that SMBv2 will be negotiated/used.

      The consensus of “implement old insecure protocols on all of your workstations” isn’t really a realistic or viable approach.

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Recast Sponsored AD
Ad image
Patch My PC Sponsored AD
Ad image

Latest Articles

Fix Windows Autopilot Reset Error 0x80070032
Fix Windows Autopilot Reset Error 0x80070032
Autopilot Intune
Windows activation error 0xc004c020
Fix: Windows Activation Error 0xC004C020 with 2 Easy Methods
Windows 11 Windows 10
Find the Package ID of SCCM Application
3 Best Ways to Find the Package ID of SCCM Application
SCCM
SCCM Updates Install Error 0x800b0109 0x8024b303
Fix: SCCM Updates Install Error 0x800b0109 | 0x8024b303
SCCM
Subscribe to Our Newsletter

Subscribe to our newsletter to get our newest articles instantly!

You Might Also Like

Windows activation error 0xc004c020
Windows 11Windows 10

Fix: Windows Activation Error 0xC004C020 with 2 Easy Methods

By Prajwal Desai
Azure VM Remote Computer Requires Network Level Authentication
Azure

Azure VM: Remote Computer Requires Network Level Authentication

By Prajwal Desai
Enable and Configure Bitlocker using Intune
Intune

Enable and Configure BitLocker using Intune: A Step-by-Step Guide

By Prajwal Desai

Removed from reading list

Undo
Welcome Back!

Sign in to your account

Lost your password?