Windows 11 Upgrade — Plan & Recommendation
Section titled “Windows 11 Upgrade — Plan & Recommendation”Current state (confirmed 2026-07-21)
Section titled “Current state (confirmed 2026-07-21)”| Item | Value |
|---|---|
| OS | Windows 10 Home, version 2009 (build 19045 / 22H2) |
| CPU | AMD Ryzen 7 1700 (8-core, launched March 2017) |
| TPM 2.0 / Secure Boot | Not confirmed — the WSL-invoked check needed elevation this session didn’t have; run Microsoft’s PC Health Check app for a definitive pass/fail (fastest, official) |
The blocker: CPU compatibility
Section titled “The blocker: CPU compatibility”Microsoft’s official Windows 11 supported-CPU list starts at 2nd-generation Ryzen (Zen+, the 2000-series) for most AMD chips — the Ryzen 7 1700 is 1st-gen Zen and is not on that list. This is a well-established, publicly documented Microsoft compatibility boundary, not something specific to this machine.
Practical effect:
- No official free upgrade path via Windows Update — the PC Health Check app will report “This PC doesn’t currently meet Windows 11 requirements,” with CPU as the specific reason
- Unofficial installs are possible (registry bypass flags, or a modified install ISO via tools like Rufus) but come with real trade-offs: Microsoft doesn’t guarantee driver updates or even continued feature updates for unsupported hardware, and a bypass install can break on a future cumulative update
Why this matters now (not just “someday”)
Section titled “Why this matters now (not just “someday”)”Windows 10 passed its mainstream end-of-support date (October 14, 2025) — it’s already in the past as of today (2026-07-21). Consumer Extended Security Updates (ESU) exist as a bridge (free enrollment via Windows Backup sync, or paid), but that’s a 1-year stopgap, not a long-term answer. This is the actual urgency driver — not disk space, which the purge already addressed.
Recommendation
Section titled “Recommendation”Don’t treat this as “swap in a new SSD, keep the same box.” The Ryzen 7 1700 is 8+ years old and is the actual constraint, not storage. Two honest paths:
- Full platform refresh (recommended): new CPU/motherboard/RAM (AM5 platform gets you a currently-supported CPU + official Win11 + room to reuse the existing case/PSU/GPU/drives) — the SSD upgrade folds into this as “buy the 1TB drive as part of the new build,” not a standalone purchase. Bigger one-time cost, but you stop having “is this machine still supported” come up again for years.
- Bypass-install Windows 11 on current hardware as a stopgap: cheapest, fastest, but inherits real risk (see above) and doesn’t solve “8-year-old CPU” — likely revisits this exact decision again in 1-2 years.
This is a purchase/hardware decision — not something to execute from this session. Flagging the recommendation and the reasoning; the actual call (refresh vs. bypass vs. stay on ESU for now) is yours.
Next step if you want to proceed
Section titled “Next step if you want to proceed”- Run Microsoft’s PC Health Check app for the definitive TPM/Secure Boot verdict (CPU is already a known blocker regardless)
- not supported — confirms the CPU finding; even a bypass-install would need to route around Secure Boot/TPM checks too, not just the CPU list
- Decide: full refresh vs. bypass-install vs. stay on Win10 + ESU for now
Real downsides of staying on Windows 10 (answering the question above)
Section titled “Real downsides of staying on Windows 10 (answering the question above)”Your system working fine today is real signal, not a false sense of security — “unsupported OS” risk is about what happens going forward, not a change in today’s behavior. Concretely:
- Security patches stop (already stopped for free/mainstream as of Oct 2025) — newly discovered Windows vulnerabilities after that point don’t get fixed unless you’re enrolled in Consumer ESU (free via Microsoft account + Windows Backup sync, or ~$30 one-time — bridges to Oct 2026, one year only, no further extension for consumer). This is the actual clock, not a vague “it’ll get slow” concern.
- Practical exploit risk is a function of exposure, not raw vulnerability count — a machine with a firewall, updated browser, and no exposed services is a smaller target than an internet-facing server. Your risk profile is “home desktop used for business” (MBR touches client financial data), which argues for treating this a bit more conservatively than a pure personal-use machine would.
- Third-party support (Chrome, browsers, security tools) typically outlives Windows itself by a while — that’s not the risk. The risk is unpatched OS-level vulnerabilities (kernel, network stack, etc.) that no third-party tool can fully compensate for.
- No feature/driver regression risk from staying put — this isn’t “it’ll degrade,” it’s “the patch window closes.”
Given your stated plan (defer any platform change until the future AI-workstation build — bigger CPU, 32GB+ unified RAM/GPU, larger SSD — which isn’t urgent while cloud AI pricing stays favorable): the practical bridge is enroll in Consumer ESU now (free tier via Microsoft account sync is the obvious choice — no cost, no downside) to keep security patches flowing through Oct 2026, and revisit the full platform decision on your own timeline rather than Microsoft’s. This avoids the false choice of “refresh now vs. run unpatched” — ESU buys the exact runway your stated plan already assumes.
- Recommendation: enroll in Windows 10 Consumer ESU (free tier) as the bridge; defer full refresh until the AI-workstation upgrade is actually wanted — no forced timeline
- done; see C:\tmp\ScreenShots\explorer_wQzI3oAICW.png
- If/when the AI-workstation build becomes real: separate task to scope it (CPU/mobo/RAM/GPU/SSD) — that build will also resolve the Win11 CPU-support issue as a side effect, not a separate purchase
- Will do. I suspected and hoped that this was the reality.