Were sorry we can t continue because we weren t able to download a required file

  1. Were sorry we can t continue because we weren t able to download a required file

    If the required setup files won’t download, the wizard throws an error and just halts. So, before you blame it on Configuration Manager, let’s look at some solutions to address the download of Office 365 file failed.

    Table of Contents

    • Fix: Download of Office 365 file failed, Error =
      • Solution 1. Install ConfigMgr 2006 Hotfix KB4578605
      • Solution 2. Check your Firewall Configuration
      • Solution 3. Office 365 Application Deployment
      • Solution 4. Uninstall October 2020 Update (KB4577668)

    Fix: Download of Office 365 file failed, Error =

    Recently, I saw people posting about the Office 365 file download error in my ConfigMgr forums. The error is Download of Office 365 file failed, error =. This error is observed while downloading the Office 365 setup files and the interesting part is there is no error code, and it’s just blank.

    Were sorry we can t continue because we weren t able to download a required file
    Download of Office 365 file failed, Error =

    It is very challenging to diagnose the O365 file download issue without error code. Furthermore, I would never consider looking through any log files in this situation. If you are unable to download the Office 365 setup files and you have encountered the same issue, here are some of the solutions.

    Solution 1. Install ConfigMgr 2006 Hotfix KB4578605

    There is a new hotfix KB4578605 for ConfigMgr 2006. This hotfix resolves the issue where the Configuration Manager clients are unable to download Office 365 updates. ERROR: DownloadContentFiles() failed with hr=0x80073633. So ensure you install this hotfix and try downloading the updates again.

    Solution 2. Check your Firewall Configuration

    So with no error code, we don’t know why this issue is occurring. However we know that the Office 365 downloads aren’t working. So the first thing that you must do is check your firewall configuration. We all know that Office 365 requires connectivity to the Internet. The endpoints should be reachable for customers using Office 365 plans. Endpoints data is updated almost every month with new IP Addresses and URLs published 30 days in advance of being active. Endpoint data in this article lists requirements for connectivity from a user’s machine to Office 365. Talk to your network team and whitelist the endpoints provided in that article and give a try. I am confident that Office 365 downloads will work.

    Solution 3. Office 365 Application Deployment

    The second solution is bit weird but I see it has worked for few. Here is the Technet forum thread that I am talking about. The issue is resolved by changing the setting Do you want to deploy the application now? to Yes.

    Were sorry we can t continue because we weren t able to download a required file
    Download of Office 365 file failed

    Solution 4. Uninstall October 2020 Update (KB4577668)

    I am updating this solution after I saw an update from ConfigMgr product team.According to David James’s tweet, Windows October patches broke #configmgr #memcm’s ability to download o365 patches. we are working on a hotfix, and KB. The break is caused when the machine doing the download (admin UI, or ADR) is patched with oct’s 10b patches; causing a cert failure.

    So the only workaround for now until a fix is released, is run the Admin UI on a machine that isn’t patched to 10b and manually sync the o356 patches.

    Were sorry we can t continue because we weren t able to download a required file
    Download of Office 365 file failed Error | Uninstall KB4577668

    According to Robinson Chan, seems like the October 2020 Update (KB4577668) on your primary site server may be the cause of the issue. In the Patchdownloader.log, you may see error: Authentication of file failed, error 0x800b0004.

    The October 2020 Update (KB4577668) on the Primary Site Server must currently be removed before the server can be restarted. Thanks, Robinson, for this information. Apart from the solutions listed above, if something else has worked for you, kindly let me know, and I will add it to this post.