# Network Path Not Found/ An Extended Error Occurred

**Last Updated On:** 11 Mar 2026  
**8 minutes read**

Also applicable for **Endpoint Central**

## Problem

Endpoint Central Agent/Distribution server installation, Patch Scan, Asset Scan and Remote Control fail with error message - "Network Path was not found."

## Cause

This error will be shown if:

1. The client computer is down or not accessible.
2. "File and Printer Sharing for Microsoft Networks" is not enabled in the network adapter of the client computers.
3. Microsoft Firewall blocks the process.
4. Third-party Firewall blocks the process.
5. Administrative Share (Admin$) on the client computer might have been disabled.

**Note:**

1. The causes/resolution that are explained in this article are based on experiences in production and client environments. However, there may still be a few unknown causes. In case this article does not resolve your issue and if you have an Active Directory-based network, you can [automate Agent Installation](https://www.manageengine.com/products/desktop-central/help/cve/agent_installation_windows_gpo.html) using a Start-Up script.
2. The resolution provided in this article will help you overcome the problems encountered during manual patch and inventory scanning. However, there might be some cases where it fails again due to various reasons. It is hence recommended to perform scheduled [patch](https://www.manageengine.com/products/desktop-central/help/cve/scheduled_patch_scanning.html) and [inventory scanning](https://www.manageengine.com/products/desktop-central/help/cve/inventory-management-how-to.html#inventory-management-how-to1).

## Resolution

You can resolve this issue as follows:

1. **Ensure the client computer is accessible**

   Check that the client computer is switched on and properly connected to the network to install the Agent/Distribution server and carry out operations like Patch Scan, Remote Control, and Asset Scan. Also, ensure that you have specified the computer name correctly.

   The following step will help you confirm the client machine's accessibility:

   - Go to **Start > Run**
   - Type the computer name prefixed by `\\`
   - Press **Enter**

2. **Enable "File and Printer Sharing for Microsoft Networks"**

   Enable this in all client computers to carry out remote operations like Agent or Distribution server Installation, Patch Scan, Inventory Scan, and Remote Control.

   ### For operating systems released before Windows 7

   1. Select **Start → Settings → Network Connections**.
   2. Right-click on **Network Connection** and select **Properties**.
   3. In the connection properties dialog, select the **General** tab.
   4. Select **File and Printer Sharing for Microsoft Networks** and click **OK**.
   5. If you do not find this option, click **Install**.
   6. In the network component type, select **Service** and click **Add**.
   7. Select **File and Printer Sharing for Microsoft Networks** and click **OK**.
   8. Click **Close** to exit the properties dialog.

   ### For Windows 7

   1. Select **Start → Control Panel**.
   2. Choose **Network and Internet**.
   3. Select **Network and Sharing Center** and choose **Change Advanced Sharing Settings**.
   4. Under **File and Printer Sharing**, enable **Turn on File and Printer Sharing**.
   5. Click **Save changes**.

3. **Enable the Administrative Share (Admin$) on the client machine**

   Endpoint Central copies the Agent/Distribution server binaries to the Admin$ of the client machine prior to triggering installation. Therefore, it is essential to have Admin$ enabled on client machines for smooth Agent/Distribution server installation. You will need to edit the registry to enable the default administrative share.

   ### For Servers

   1. Click **Start** and select **Run**.
   2. Type `regedit` in the Run prompt and click **OK**.
   3. Navigate to the following registry location and edit the REG_DWORD value to `1`:

      ```
      Hive: HKEY_LOCAL_MACHINE
      Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
      Name: AutoShareServer
      Data Type: REG_DWORD
      Value: 1
      ```

      **Note:**
      - If the value does not exist in the specified registry location, there is no need to create a new value.
      - A reboot is necessary for this to take effect.

   ### For Windows Server 2008 R2

   In a Windows Server 2008 R2-based domain environment, you can enable Admin$ on your client machine using a Start-Up script. Refer to this [document](http://technet.microsoft.com/en-us/library/cc732793.aspx) for details.

   ### For Workstations

   1. Click **Start** and select **Run**.
   2. Type `regedit` in the Run prompt and click **OK**.
   3. Navigate to the following registry location and edit the REG_DWORD value to `1`:

      ```
      Hive: HKEY_LOCAL_MACHINE
      Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
      Name: AutoShareWks
      Data Type: REG_DWORD
      Value: 1
      ```

      **Note:**
      - If the value does not exist in the specified registry location, there is no need to create a new value.
      - A reboot is necessary for this to take effect.

**Applies to:** Agent/Distribution server Installation Failure, Endpoint Central Agent/Distribution server Installation, Patch Scan Failure, Asset Scan Failure  

**Keywords:** Agent/Distribution server Installation, Endpoint Central Agent/Distribution server Installation Failure, Patch Scan Fails, Asset Scan Fails, Installation Failure, An Extended Error Occurred