,
If after installing Windows 11 24H2 you cannot access the shared files and printers on other network PCs with error “0x80070035: Network path not found”, then in this guide you’ll learn how to fix the problem.
Symptom: After upgrading Windows 11 to version 24H2, shares cannot be accessed with error code 0x80070035 “The network path not found”, while all other computers running Windows 11 v23H2 or Windows 10 can access the Shares without issue.
Cause: Windows 11 24H2 has increased the level of security and by default no longer allows the access to shared files without providing credentials. This means that insecure connections are not allowed by default, and you can no longer access the shares on another computer unless you have a user account and password on that computer.
How to FIX: “0x80070035: Network path not found”, when trying to access shares on other computers from Windows 11 24H2.
As you can understand from the cause of the problem, the recommended method to solve the above issue is to create different accounts and passwords on the computer with the shares for each user on the network who will access the shares.
If you do not want to create credentials on the PC with the shared items, follow the instructions below to allow the non-secure connections.*
* Suggestion: Before proceeding with the methods below, check if you can access the computer with the shared folder(s) through direct access. To do this, type in the explorer’s address bar “\“, and then the Name or the Static IP address of the computer with the shared folders.
For example: If the computer with the shared items, is named “PC1” and has the IP address “192.168.1.25“:
1. Type in File Explorer’s address bar (or in the ‘Run” command box), one of the following and hit Enter.
- \PC1
- \192.168.1.25
2. If prompted, type a username and password on that PC to access its shares. Then if you can “see” the shared folder(s), right-click on it and select Map Network Drive to easy access the shared folder at anytime from File Explorer.
Method 1. Allow Insecure Logins via Group Policy (Windows 10/11 PRO)*.
The first method to solve the above problem is to allow users to be able to access the shared folders without requiring credentials. To do this, go ahead and make the following changes to Group Policy, both on the computer with the shares and on Windows 11 v24H2 computer.
* Note: This method requires Windows 11/10 Pro Editions. For Windows 11/10 Home Editions, see methods 2 & 3 below.
Step 1. Allow insecure guest logons via Group Policy.
1a. Press Windows 
+ R keys to load the Run dialog box.
1b. Type gpedit.msc and press Enter, to open the Group Policy Editor.
2. In Local Group Policy Editor navigate to the following location:
- Computer ConfigurationAdministrative TemplatesNetworkLanman Workstation
3a. On the right, open the Enable insecure guest logons policy.
3b. Set the policy to Enabled and click Apply > OK.
4. Close the Group Policy Editor and restart the computer.
5. After making the above changes on both the Windows 11 24H2 computer and the computer with the shared files, check if you can now access the shared files from the Windows 11 24H2 computer. If not, proceed to step-2.
Step 2. Disable “Digitally sign communications” via Group Policy.
Proceed and make the following changes to Group Policy, both on the Windows 11 24H2 computer and the computer(s) with the shares.
1. Open the Group Policy Editor and navigate to this location:
-
Computer ConfigurationWindows SettingsSecurity SettingsLocal PoliciesSecurity Options
2. At the right pane, make sure that the following two (2) policies are Disabled. If so skip to next step.*
-
Microsoft Network Client: Digitally sign communications (always)
-
Microsoft Network Client: Digitally sign communications (if server agrees)
* Note: If one or both of the above policies is Enabled the open it set it to Disabled and click Apply > OK. Then restart the computer(s) and check if the problem is fixed.
Method 2. Allow Insecure Guest Logins in Registry.
If you don’t own a PRO edition of Windows 11/10, then you can allow the insecure guest logons by modifying registry. To do this:
1. Open Command Prompt as Administrator and issue the following three (3) commands:
-
reg add HKLMSYSTEMCurrentControlSetServicesLanmanWorkstationParameters /f /v RequireSecuritySignature /t REG_DWORD /d 0
-
reg add HKLMSOFTWAREPoliciesMicrosoftWindowsLanmanWorkstation /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
-
reg add HKLMSOFTWAREWOW6432NodePoliciesMicrosoftWindowsLanmanWorkstation /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
2. Restart the computer, and check if you can access the shares now.*
* Note: If you still cannot the shares, and you want to remove the added registry values, issue the following commands in Command Prompt (Admin):
-
reg delete HKLMSYSTEMCurrentControlSetServicesLanmanWorkstationParameters /f /v RequireSecuritySignature
-
reg delete HKLMSOFTWAREPoliciesMicrosoftWindowsLanmanWorkstation /f /v AllowInsecureGuestAuth
-
reg delete HKLMSOFTWAREWOW6432NodePoliciesMicrosoftWindowsLanmanWorkstation /f /v AllowInsecureGuestAuth
Method 3. Allow Insecure Connections from PowerShell.
The final method to fix the error “Network path not found – 0x80070035” in Windows 11 24H2, is to allow the insecure guest logons, using PowerShell.*
* Note: Run the below PowerShell commands on both the computer with the shares and on Windows 11 v24H2 computer.
1. Open PowerShell as Administrator and give the following three (3) commands:
-
Set-SmbClientConfiguration -EnableInsecureGuestLogons $true -Force
-
Set-SmbClientConfiguration -RequireSecuritySignature $false -Force
-
Set-SmbServerConfiguration -RequireSecuritySignature $false -Force
That’s it! Which method worked for you?
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.
