The short version
- 01Record the failed Update package, time and complete 0x80072EFE code.
- 02Ask an administrator to inspect BITS jobs with BITSADMIN /LIST /ALLUSERS /VERBOSE.
- 03Find the matching 80072EFE entry, HTTP result and file URL.
- 04Have the administrator compare that exact download URL through the organization's normal proxy.
- 05Give the failed URL and comparison result to the proxy or network team if it still fails.
- 06Retry the identified update after the transfer issue is corrected.
Raw message
0x80072EFE
Likely causes
- A server connection closes abnormally during update checking or downloading.
- BITS transfer trouble or an unwritable destination affects the download.
Use the specific aborted-connection entry
Microsoft's common Update table maps this code to WININET_E_CONNECTION_ABORTED and an abnormally closed server connection. It also names BITS transfer or destination-file trouble. Our recommendation is to retain the package and time rather than treating every occurrence as the same timeout.
Identify the matching BITS transfer
Microsoft's diagnostic uses BITSADMIN /LIST /ALLUSERS /VERBOSE. Have an administrator match the 80072EFE job, HTTP result and file URL. Our recommendation is to retain only the relevant result for troubleshooting instead of publishing complete device job output.
Compare the exact URL through the normal proxy
The table tests the specific file URL in a browser using the organization's proxy. If that fails too, give the URL to the proxy or network team. Our recommendation is to keep the normal managed connection; the comparison does not require disabling its protections.
Sources and review notes
Checked on . Official documentation read October 6, 2026. Matching the incident and retaining limited diagnostic output are editorial guidance. This reference is for Windows Update transfers. Glitchary is independent of Microsoft.