Case of ConfigMgr Setup Updates Failing–Error 0x80072efe

ConfigMgr setup successfully downloaded several thousand files during pre-requisite downloads, then failed with error:

An error has occurred while attempting to download or verify required

prerequisite components and Setup cannot continue. Review the

configmgrsetup.log file for further details.


Opening C:\configmgrsetup.log showed the following error:

INFO: Downloading as  $$<Configuration Manager Setup><03-20-2017 14:13:55.946-660><thread=3224 (0xC98)>
INFO: WinHttpQueryHeaders() in Download() returned OK (200)  $$<Configuration Manager Setup><03-20-2017 14:14:01.830-660><thread=3224 (0xC98)>
ERROR: _ReadDataAndWriteToFile() failed with 0x80072efe  $$<Configuration Manager Setup><03-20-2017 14:14:27.760-660><thread=3224 (0xC98)>
ERROR: Download() failed with 0x80072EFE  $$<Configuration Manager Setup><03-20-2017 14:14:27.776-660><thread=3224 (0xC98)>

The download always failed on same file. Re-running the download while running Fiddler

We see downloads with result code 302, redirecting to URL which fails with result code 504.

Fiddler shows the following info for the failing request:

HTTP/1.1 504 Fiddler – Receive Failure
Date: Mon, 20 Mar 2017 07:52:30 GMT
Content-Type: text/html; charset=UTF-8
Connection: close
Cache-Control: no-cache, must-revalidate
Timestamp: 18:52:30.059

[Fiddler] ReadResponse() failed: The server did not return a complete response for this request. Server returned 19,871,449 bytes.                                                                                                                                                                                                                                                                                                                                                                                             

I repeated the download, this time without Fiddler, and running Wireshark capture. Using Fiddler’s File –> Import Sessions –> Packet Capture option, the trace this time showed shows 200 response.


Selecting this response in Fiddler, right clicking, and selecting Save –> Save Response –> Response Body resulted in a .CAB file that was corrupt and didn’t open.

Reviewing the Wireshark trace with a filter on the proxy server IP address ip.addr eq <proxy IP> we can see what goes wrong

The last packet received from proxy server is a TCP reset:


You can also see the failure at Windows API level easily using Rohitab API Monitor

For this I monitored Internet and Windows Application UI Development –> Dialog Boxes APIs for process SetupDL.exe. This process is created only when downloads start. By monitoring the Dialog Box APIs you can just search for the error message application displayed and work backwards to see events leading to error.

In this case WinHttpReadData fails with error 12030 “The Connection with the server was terminated abnormally”


Attempting to manually download file in Internet Explorer, Mozilla Firefox or Google Chrome from the same machine via the same proxy ended up with the same result – corrupt CAB file.

Checking the environment’s proxy.pac file I noticed there was about 6 different potential proxy servers listed.

I manually set a different proxy server….the download worked manually. Re-trying ConfigMgr update download succeeded. Further investigation would need to be done from proxy server side to identify root cause of problem.

If a fix to proxy server is not immediately available you can use the “Get the latest Configuration Manager updates” option on a machine directly connected to the internet with no proxy, to download the updates.

About chentiangemalc

specializes in end-user computing technologies. disclaimer 1) use at your own risk. test any solution in your environment. if you do not understand the impact/consequences of what you're doing please stop, and ask advice from somebody who does. 2) views are my own at the time of posting and do not necessarily represent my current view or the view of my employer and family members/relatives. 3) over the years Microsoft/Citrix/VMWare have given me a few free shirts, pens, paper notebooks/etc. despite these gifts i will try to remain unbiased.
This entry was posted in API Monitor, ConfigMgr, Fiddler, WireShark and tagged . Bookmark the permalink.

1 Response to Case of ConfigMgr Setup Updates Failing–Error 0x80072efe

  1. Nik says:

    Hi, Had same problem and unable to fix but did find a workaround with 1802. Luckily, some of the 1802 EasySetupPayload existed so I was able to find SetupDL.exe (1802). Steps used:
    1. Ran “D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\eab25b02-02dd-4a14-b6d0-ba5bde540d66\SMSSETUP\BIN\X64\SetupDL.exe”. Target Folder “D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\Prereq_Manual “.
    2. Found failure:
    redirects to:
    3. Manually downloaded in IE logged in as svcCMsystemUpdates by resuming and retrying on failure. Placed in: “D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\Prereq_Manual “.
    4. Re-Ran SetupDL.exe – Completed successfully.
    5. Copied content of “D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\Prereq_Manual\*” to “D:\Program Files\Microsoft Configuration Manager\EasySetupPayload\eab25b02-02dd-4a14-b6d0-ba5bde540d66\Redist”
    6. Restarted smsexec.exe, monitored dmpdownloadeder.log and ConfigMgrSetup.log. Completed successfully, available for install in-console.
    7. Ran Prerequisite checks successfully
    8. Installed 1802 successfully

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s