Windows System Errors

Connection Aborted

0x80072EFE
MediumSystem

Reviewed for reference consistency: August 11, 2026

an established link was terminated while data was still moving

What 0x80072EFE Means

The 0x80072EFE error on the Windows System Errors indicates connection aborted — an established link was terminated while data was still moving. This typically occurs due to a proxy, firewall, or nat device severed an in-progress transfer.

Transfers that die mid-flight — after the handshake, during the payload — end with 0x80072EFE, the HRESULT of WinINet error 12030, ERROR_INTERNET_CONNECTION_ABORTED: 'The connection with the server has been terminated'. Windows Update documentation gives the code a specific owner: BITS, which surfaces it when a transfer cannot complete, and the guidance walks through identifying the failing file from BITS job listings.

How to fix 0x80072EFE

General informational guidance, not professional advice. Commands can affect your system or data — back up first and proceed at your own risk. FixerCode is an independent reference, not affiliated with any vendor mentioned.

  1. List BITS jobs and their failures

    Verbose job listings name the file and HTTP response behind the abort, converting a transport code into a specific URL.

    bitsadmin /list /allusers /verbose
  2. Pull the update client's recent failures

    The operational event channel records download failures per update, which lines up with the BITS view.

    wevtutil qe Microsoft-Windows-WindowsUpdateClient/Operational /f:text /c:15 /rd:true /q:"*[System[(Level=2)]]"

Technical Background

Timing is the difference between this code and its connect-stage sibling. The handshake succeeded and bytes were moving, so the network path existed; the event is its termination. Middleboxes with session timeouts, aggressive state inspection, and unstable links are the usual terminators, and the failure pattern follows the middlebox: cuts at a consistent transfer duration point at policy, while random cuts point at the link.

The documented update story goes through BITS because BITS carries update payloads. The guidance for the code directs you to list BITS jobs verbosely, find the job that recorded 0x80072EFE, and read the HTTP code and file it references — the artifact-level answer to which transfer died and against which URL. Attempting the same file download through a browser then shows whether the path fails for all clients or only for BITS.

Common Causes

  • A proxy, firewall, or NAT device severed an in-progress transfer
  • A BITS download of update payloads failed because the connection was cut mid-file
  • Unstable network hardware or link renegotiation dropped the session

Typical Scenarios

  • BITS reports a failed update download with 0x80072EFE, and the BITS job listing names the URL and HTTP code behind it
  • A proxy or filtering device cuts long-running transfers after a fixed interval
  • Wireless or WAN links renegotiate mid-transfer, aborting the session

What to Know

Duration patterns carry the diagnosis: transfers cut after the same interval implicate a middlebox policy, while irregular cuts implicate the link itself.

Frequently Asked Questions

Common questions about Windows 0x80072EFE error

Error 12030, ERROR_INTERNET_CONNECTION_ABORTED, 'The connection with the server has been terminated'. The update documentation also lists the code under its WinINet symbol WININET_E_CONNECTION_ABORTED.

BITS transfers update payloads, and the documented mitigation lists BITS jobs verbosely to find the entry recording 0x80072EFE, which names the failing file and URL.

A timeout (12002) ends a wait that produced nothing. An abort (12030) ends a transfer that was actively progressing, which is why middlebox session policies show up here.

Related Error Codes

Related Errors From Other Categories

Similar error codes documented across different platforms and systems