How to Fix Error Code 0x80070035 on Your Windows Network

windows updateHaving all of your PCs or devices connected to the same network can make your daily tasks a whole lot easier. The benefits are tremendous - you can access files on one of the devices while using another or print important documents no matter which computer is physically connected to the printer. What should you do if suddenly you encounter an error code 0x80070035 and "The network path was not found" text while attempting to access one of the devices on the network?

Windows Patch Causes Error Code 0x80070035

While there are quite a few methods that could potentially fix this error, all affected users should first check to see if their Windows 7 and Windows Server 2008 R2 computers have either the KB4480970 (Monthly Rollup) or KB4480960 (Security-only update) updates installed on them. Both updates applied several security fixes including a fix for a remote execution vulnerability in PowerShell. Unfortunately, the patches also caused some unforeseen issues such as:

  1. The network interface controller may stop working due to an issue related to a missing file - "oem<number>.inf".
  2. Local users may be prevented from remotely accessing shares on Windows 7 or Windows Server 2008 R2 machines.
  3. An error stating an incorrect format when opening databases in Access 97 .mdb format could occur.

Windows Error Code 0x80070035 screenshot
windows error code fix

Recommended

Top 3 Reasons Why Your PC May be Vulnerable to Hacking

Outdated OS, visiting malware-laced sites or opening spam emails can open doors to hackers to your PC. Take steps to protect yourself from getting hacked.

Get SpyHunter Today!

Microsoft Releases a Fix

Initially, users were forced to either uninstall the updates and lose the important security fixes that came with them or tamper with the Windows registry for a crude workaround to the problem. That is no longer necessary However, Microsoft swiftly released a new update that addresses the network shares being inaccessible. While update KB4487345 fixes this issue, it has not been marked as a high priority update forcing users to manually search for and install it on all Windows 7 and Windows Server 2008 R2 SP1 computers in their network. A separate update -KB4487354, has been released specifically for machines using Windows Server 2008 SP2.

Microsoft has also provided a workaround for the network interface controller issue:

  1. To locate the network device, launch "devmgmt.msc."
  2. Look for the network device. It may be under Other Devices.
  3. From the Action menu, select "Scan for Hardware Changes" to automatically rediscover the network controller and install the necessary drivers.

Alternatively, users can try the following:

  1. Locate the device, right click it and select "Update".
  2. Choose "Search automatically for updated driver software" or "Browse my computer for driver software."

One Comment

  • rosered:

    The users are facing these issues with Window based systems that will be really very fruitful for them to get effective features for them.

Leave a Reply

Please DO NOT use this comment system for support or billing questions. For SpyHunter technical support requests, please contact our technical support team directly by opening a customer support ticket via your SpyHunter. For billing issues, please refer to our "Billing Questions or Problems?" page. For general inquiries (complaints, legal, press, marketing, copyright), visit our "Inquiries and Feedback" page.