0x80072F8F is a secure-connection failure: Windows tried to talk to Microsoft's servers over HTTPS and the handshake failed. On Windows 7 and 8.1 it famously appears as "0x80072F8F - 0x20000" the moment the Media Creation Tool starts - those systems speak old TLS by default, and Microsoft's servers require TLS 1.2. Elsewhere (activation, Store, Update) the same code usually means the system clock is wrong. Both causes are fixable in minutes.
Ask Chipps
Describe what is happening in your own words, for example: "I keep getting error 0x80072F8F and don't know what to do". Chipps checks your PC, shows what it found and proposes a fix. Nothing changes until you click Allow.
Download Chipps Downloads the Chipps setup file for Windows.Quick answer
First check the clock: date, time and time zone must be correct - a wrong clock breaks certificate checks and produces exactly this error. On Windows 7/8.1 with the Media Creation Tool, enable TLS 1.2 (method 2) - or skip the tool entirely and download the Windows ISO from Microsoft's site in a browser (method 3).
These systems default to TLS 1.0 for system components. Microsoft's servers require TLS 1.2 - the handshake fails before anything downloads.
HTTPS certificates are valid for date ranges. A clock that is off - dead CMOS battery, wrong time zone - makes every certificate look invalid, and secure connections fail with 0x80072F8F.
TLS 1.2 support on Windows 7 arrived through updates. A long-unpatched system may lack the component itself, not just the setting.
Proxies, VPNs and some antivirus "HTTPS scanning" features break the secure handshake the same way - temporarily disabling them isolates the cause.
inetcpl.cpl), Advanced tab: tick Use TLS 1.1 and Use TLS 1.2, untick SSL 3.0; apply.HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp create DWORD DefaultSecureProtocols = 0xA00 (on 64-bit also under the matching Wow6432Node path), then restart.Careful: Edit the registry exactly as written and only these values - or prefer method 3, which avoids the registry entirely.
The first part is a secure-channel (HTTPS) failure; the suffix is the Media Creation Tool's context code. Together: the tool could not establish a TLS connection to Microsoft's servers - which on Windows 7/8.1 is almost always the TLS 1.2 issue.
The upgrade path via the Windows ISO still works technically: download the ISO (method 3), run setup from it and keep files where offered. Whether the hardware meets requirements - particularly for Windows 11 - is a separate check the installer performs.
Browsers tolerate small clock drift; the system's own HTTPS stack is stricter. A clock off by enough makes valid certificates appear not-yet-valid or expired, so system components fail with 0x80072F8F while websites still open.
Describe the problem in your own words. Chipps reads the Windows logs, points to the likely cause and proposes the narrowest fix. Nothing is changed without your Allow, and at the end it shows what it did and what it did not do.
Download Chipps Downloads the Chipps setup file for Windows.