Download Failed: 404 Not Found
Purpose
When running a deployment, the deployment fails with the following error.
Download failed: 'filename.msi': there was an error processing your request; statusCode: 404 Not FoundThe deployment output may also include an XML message like the one below.
<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message></Error>Cause
This error means PDQ Connect could not find the installer file in storage when the deployment tried to download it to the target device. The most common cause is that the file uploaded to the package is corrupt or was not stored correctly — for example, a custom-branded or vendor-modified installer that did not upload successfully.
This is a file-level issue, not a platform outage. Duplicating the package will produce the same error, because the underlying file copy stored on PDQ's platform is the problem.
Resolution
Follow these steps to identify and fix the issue.
- Check the PDQ status page. Visit status.pdq.com to confirm there are no active platform outages that could be affecting deployments.
- Try downloading the file from within PDQ Connect. Open the package in PDQ Connect and try to download the attached installer directly from the interface. If that download also fails with a 404 error, the file itself is the problem — not the deployment.
- Download a fresh copy of the installer from the vendor. Go to the software vendor's website and download a new copy of the installer. Do not reuse the file you previously uploaded, as it may have been corrupt prior to upload.
- If you are using a custom or vendor-branded installer, try the standard version instead. Custom-branded installers are sometimes configured in ways that cause upload or storage issues. The standard public installer from the vendor's download page is more reliable.
- Create a new package with the fresh installer and test the deployment. Upload the newly downloaded file to a new package and run a test deployment. If it succeeds, the original uploaded file was corrupt or improperly configured.
If the issue persists after trying the steps above, contact PDQ Support.
Related articles
