Bug fix: You cannot connect to the file share because it’s not secure

With the release of Windows 10 v1803 or Spring Creators Update, I decided to do a new installation on my PC. Once that was done, I tried to map the network sharing on the Popcorn Hour VTEN Media Streamer. Unfortunately, I was unable to do this because Microsoft seems to have disabled the SMB1 protocol in this version.

I got the following error message when trying to map the network drive:

You cannot connect to file sharing because it is not secure. This sharing requires SMB1 protocol, which is insecure and can expose your system to attacks.

Since Popcorn Hour runs on Linux and has installed the latest update available, I didn’t have many options for solving this problem. To solve this problem, I had to install and activate the SMB1 protocol using Powershell.

 

What is the cause of the ‘You cannot connect to the file share because it is not secure’ error

What is the cause of the 'You cannot connect to the file share because it is not secure' error

This error is mainly due to the fact that SMB1 is not activated on the system. SMB1 is no longer supported in Windows 10 version 1709 or later. Since SMB1 is a rather old protocol, security threats such as ransomware and other malware can use it to infiltrate your system. Therefore, as a precautionary measure, Microsoft has not included SMB1 protocol by default in Windows 10 versions. It has been replaced by SMBv2 and higher.

 

Here’s how to solve the “You cannot connect to the file share because it’s not secure” problem

Here's how to solve the "You cannot connect to the file share because it's not secure" problem

Enable SMBv1 protocol
  1. Press Win+R to open the Run window and type Control Panel. Press Enter to open the Control Panel.
  2. Click Programs.
  3. From the green Programs and Features menu, select Enable or Disable Windows Features.
  4. Scroll down the list (in alphabetical order) to SMB 1.0/CIFS File Sharing Support. Click the + sign next to it to expand the list.
  5. Select the check box for SMB 1.0/CIFS Client.
  6. Click OK to save the settings and restart the system.
Alternative Solution
  1. Open the services snap-in by running the services.msc command.
  2. Verify that the service provider’s feature discovery hosting services and feature discovery resource publishing services are running and working. If not, double-click them and click Start.
  3. Verify that network discovery is enabled on the system.
  4. If steps 1 to 3 do not help, contact the software manufacturer of the device that does not allow file sharing because of SMBv1, and ask if they can provide updates for their device with a new version of SMB protocol, such as SMBv2 or SMBv3.
  5. If you are connecting Windows 10 to a Windows Server and experiencing this problem, first disable SMBv1 on Windows Server. Then make sure that all clients connected to the Windows Server support SMBv2. Once the clients confirm SMBv2, you can upgrade your Windows Server and resolve the issue.

 

Frequently Asked Questions

  1. On your computer, open the Control Panel. Click Programs.
  2. Click the Enable or Disable Windows Features link.
  3. Expand the option to support SMB 1.0/CIFS file sharing. Select the SMB 1.0/CIFS client check box.
  4. Click the OK button.
  5. Now restart your computer.

  1. Click and open the search bar in Windows 10, in the search bar type "Windows Features".
  2. Scroll down to SMB/CIFS file sharing support version 1.0.
  3. Select the Net to SMB 1.0/CIFS File Sharing Support checkbox, and all other child boxes will be populated
  4. automatically. Click OK to apply the changes.
  5. Click the Restart Now button to restart your computer.

  1. Press Windows + R to open the Run dialog box and enter: optional features.
  2. Expand "SMB 1.0/CIFS file-sharing support" and check the box next to "SMB 1.0/CIFS client".
  3. Click OK.
  4. Now the installation will continue and you will be able to access shares again using SMB 1.

Server Message Block (SMB) is a network protocol that allows users to communicate with remote computers and servers - to use their resources or share, open, and modify files. It is also called a server/client protocol because the server has a resource that it can share with the client.