As you know, Windows allows you to share files between systems that are on the same network even though they are not connected physically. All you have to do is to make sure that the folder administrator allows access to the intended use and that your computer should be connected to the internet. Once you meet these conditions, you can share files between systems. However, recently a number of users reported that despite fulfilling these conditions, they end up getting errors instead when they try to access the shared drive. The error states:
“Error code: 0x80070035. The network path was not found.”
One of the common causes of this error is the antivirus program or the Firewall installed on your computer. It could also be that the drive is not shared in the first place or there are some issues with your network drivers. Whichever the case is, here are some potential fixes you need to check out to fix the Error code: 0x80070035.
Option 1 – Try to temporarily disable anti-virus and Windows Defender Firewall
As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like Error code: 0x80070035 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program and Windows Defender Firewall for the meantime and check if it fixes the error or not.
Option 2 – Check if the drive is shared
Before you further troubleshoot the problem, make sure that the drive you are trying to access is shared first. To do so, follow these steps:
- Right-click on the folder and select Properties.
- Go to the Sharing tab and check the status of the Network File and Folder Sharing.
- And if the status is “Not Shared”, you need to select Share.
- Next, select the intended Network User for sharing the file and choose the permission level for the user.
- After that, click on the Apply and OK buttons to save the changes made. You or the intended user should now be able to access the shared folder or file.
Option 3 – Try to ping the IP address of the targeted computer
Even though the shared folder or file is shared correctly, it is possible that the network channel is not connected properly which is why you have to test it by pinging the IP address of the targeted computer from the primary computer.
- Tap the Win + R keys to launch the Run dialog box.
- Type “cmd” in the field and tap Enter to open Command Prompt.
- Next, type the “ipconfig/all” command and tap Enter to execute it. This will populate various details.
- From the given details, take note of the IPv4 address.
- Afterward, open Command Prompt on the primary computer and then type the “ping <IPv4 address of the target computer>” command and hit Enter.
- Now check if you get 4 confirmation replies or not. If not, you can try to access the Network Adapter Troubleshooter.
To run the Network Troubleshooter, refer to these steps:
- Open the Search bar on your computer and type in “troubleshoot” to open the Troubleshoot settings.
- Next, scroll down and select the “Network Adapter” option from the right pane.
- Then click on the Run Troubleshooter” button.
- After that, your computer will check for any possible errors and will pinpoint the root cause of the problem if possible.
- Restart your computer.
Option 4 – Verify if Network Discovery is enabled
All you have to do is go to Start > Settings > Network & Internet and from there, click on the “Change connection properties” option and shift the radio button for Network profile to Private. After that, check if folder sharing is now working.
Option 5 – Try to modify the Network Security settings
There are times when the Network Security settings interfere with the folder or file sharing process. And if that’s the case, you can modify it to resolve the problem. How? Refer to these steps:
- Tap the Win + R keys to open the Run dialog box.
- Then type “secpol.msc” in the field and tap Enter to open the Local Security Policy manager window.
- After that, go to Local Policies > Security Options located on the left pane.
- Next, double click on Network security: LAN Manager authentication level in the right pane to open its Properties.
- And then select the “Send LM & NTLM-use NTLMv2 session security if negotiated” option from the drop-down menu.
- Now click on Apply and OK buttons to save the changes made.
- Reboot your computer.
Option 6 – Try to enable NetBIOS over TCP/IP
- Tap the Win + R keys to open the Run dialog box.
- Then type “ncpa.cpl” in the field and tap Enter to open the Network Connections window.
- After that, right-click on your network and select Properties.
- Next, double click on Internet Protocol Version 4 and click on the Advanced button.
- From there, go to the WINS tab and shift the radio button to Enable NetBIOS over TCP/IP.
- Now click OK to save the changes made and then restart your computer.
Option 7 – Update the Network Adapter drivers
You might also want to update the Network Adapter drivers by following these steps:
- Tap the Win + R keys to launch the Run window and then type in the “MSC” command and hit Enter to open the Device Manager window.
- Under the Device Manager, you will see a list of drivers. From there, look for the Network Adapters and expand it.
- Then right-click on each one of the Network drivers and update them all.
- Restart your PC and see if it helped in fixing the BSOD error.
Note: If updating the network drivers didn’t help in fixing Error code: 0x80070035, you can also try to uninstall the very same drivers and restart your Windows 10 PC. After that, the system itself will reinstall the drivers you just uninstalled. Alternatively, you can also download and install the drivers from the manufacturer’s website directly.
To reinstall the network adapter driver, refer to these steps:
- Open the Devices Manager from the Win X Menu.
- Then locate the device drivers and right-click on them to open the Properties.
- After that, switch to the Driver tab and click on the Uninstall Device button.
- Follow the screen option to completely uninstall it.
- Finally, restart your computer. It will just reinstall the device drivers automatically.
Most of the time running applications with typical settings is fine but from time to time we might have some applications that will require running with administrator privilege in order to work properly. In this case, it is very easy to do it, you just right-click and choose run as administrator.
Now before you go on the bandwagon on bashing Intel itself take note that it is not Intel’s fault at all. The issue that arises is mostly due to DRM software and how it works. As you might know or not, Alder Lake has two sets of cores, standard performance cores, and power cores, and with Intel’s Thread Director on-chip right cores will be used for the right tasks, and here lies the issue.
DRM software might detect Thread Director as something suspicious and malicious, and then cut access to the game because of this. Intel, of course, has reached DRM manufacturers and places documentation about how software should be developed with this hybrid technology in mind.
Of course, newer games will be updated if needed and everything will work fine, also games on GOG will work fine because of GOG’s policy of no DRM store but some older ones might be left in limbo. They could work fine but DRM might be triggered and prevent them from loading, usually, game developer itself removes DRM protection after some time but that is not really always the case and there is a chance that some games might simply just not work on Alder Lake CPU only because of DRM protection.
