# Patch Store Location Not Available Last Updated On: 10 Sep 2026 ## Problem During patch deployment, the deployment fails with the remark **Patch Store Location Not Available**. The deployment may also display **Error 404** or **Unable to download the patches from the server**. The main patch or one of its dependency patches may not be available in the patch store. ## Cause This issue occurs when the required patch is not present in the server or Distribution Server patch store. This can happen when: - The patch or one of its dependency patches failed to download. - The patch store location was changed without copying the existing files to the new location. - The **Continue deployment** option was selected even though one or more patches failed to download to the server. ### Prerequisite The following troubleshooting procedures apply only when **Continue deployment even if some patches cannot be downloaded** was enabled under **Scheduler Settings → Deployment Rule** while creating the configuration. If this option was not enabled, skip these procedures and collect the logs specified below for the applicable deployment type. ![Prerequisite](https://www.manageengine.com/sites/meweb/images/desktop-central/help/patch-management/deployment-rule.png) ## Identify the Failed Patch ### Manual Deployment 1. Navigate to **Deployment → Manual Deployment**. 2. Locate the failed collection. 3. Click the **Draft Download Failed** status. The view displays the main patch and any dependency patches that failed to download or have not yet been downloaded. Review the **Remarks** column to identify the failure reason for each patch. ### Automate Patch Deployment 1. Navigate to **Deployment → Automate Patch Deployment**. 2. Locate the failed collection. 3. Click the task name. 4. Navigate to **Download Pending Patches**. The view displays the main patch and any dependency patches that failed to download or have not yet been downloaded. Review the **Remarks** column to identify the failure reason for each patch. ## Verify the Patch Download ### On-Premises Server Without a Distribution Server 1. Navigate to **Patches → Downloaded Patches**. 2. Locate the failed patch and click its **Patch ID**. 3. Click the **Patch Name** to obtain the vendor download URL. 4. Open the vendor URL in a web browser and verify that the patch downloads successfully. If the manual download fails, resolve the applicable network, proxy, firewall, or vendor-connectivity issue before proceeding with deployment. If the issue persists, use the [log collection instructions](https://www.manageengine.com/products/desktop-central/logs-how-to.html) to collect the server logs and agent logs. ### Cloud Server Without a Distribution Server 1. Navigate to **Patches → Downloaded Patches**. 2. Locate the failed patch and click its **Patch ID**. 3. Click the **Patch Name** to obtain the vendor download URL. 4. Open the vendor URL in a web browser on the agent machine and verify that the patch downloads successfully. If the manual download fails, resolve the applicable network, proxy, firewall, or vendor-connectivity issue before proceeding with deployment. If the issue persists, use the [log collection instructions](https://www.manageengine.com/products/desktop-central/logs-how-to.html) to collect the agent logs. ### Cloud Server With a Distribution Server 1. Navigate to **Patches → Downloaded Patches**. 2. Select the appropriate **Remote Office** from the drop-down menu. 3. Locate the failed patch and click its **Patch ID**. 4. Click the **Patch Name** to obtain the vendor download URL. 5. Open the vendor URL in a web browser on the Distribution Server machine and verify that the patch downloads successfully. If the issue persists, use the [log collection instructions](https://www.manageengine.com/products/desktop-central/logs-how-to.html) to collect the Distribution Server logs and agent logs. ### On-Premises Server With a Distribution Server Use the [log collection instructions](https://www.manageengine.com/products/desktop-central/logs-how-to.html) to collect the server logs, Distribution Server logs, and agent logs. Provide the applicable collected logs to [patchmanagerplus-support@manageengine.com](mailto:patchmanagerplus-support@manageengine.com) for further analysis. ## Related - [Collect logs for troubleshooting](https://www.manageengine.com/products/desktop-central/logs-how-to.html)