Exercise 3: A Local-Account, No-Internet Setup — Possible Solution ==================================================================== WHAT THE USER GAINS WITH A LOCAL ACCOUNT ------------------------------ Per this chapter's own trade-off table, a local account offers "no cloud dependency, works fully offline, no account-level data leaves the machine" - matching exactly what this user wants: no Microsoft account features, and no internet connection handed over during setup. WHAT THE USER GIVES UP ------------------------------ The same table lists the real costs: "no cross-device sync, password recovery is entirely local (no 'forgot password' email flow)." If this user ever forgets their local password, there's no email-based reset flow to fall back on - recovery depends entirely on local mechanisms (a password reset disk made in advance, or a full reinstall), which is a genuinely higher-stakes trade-off than it might first appear. WHY MICROSOFT HAS MADE THIS OPTION HARDER TO REACH ------------------------------ Per this chapter, "since Windows 11 22H2, a network connection is required by default before setup will continue on the Home edition, specifically so the account-creation step that follows can push toward a Microsoft account." The internet requirement isn't a neutral technical necessity - it's specifically positioned to steer setup toward the Microsoft account gains (settings sync, OneDrive, Windows Hello portability) this chapter's own table lists, since a local account historically didn't require a network connection to create at all. WHY THIS IS WORTH FLAGGING TO THE USER DIRECTLY ------------------------------ This chapter's own warn-box notes that "Microsoft has made this option progressively harder to find in the OOBE flow over successive updates" - meaning the exact path to a local account changes between releases and isn't something to promise a fixed set of steps for. The honest answer for this user is naming the real trade-off (offline independence and no cloud sharing, at the cost of sync and easy password recovery) rather than promising a specific click-path that may not match whatever build is actually running. WHY THIS WORKS AS AN ANSWER ------------------------------ It states both sides of the trade-off directly from this chapter's own table, explains specifically why Microsoft's own network requirement works against this user's stated goal rather than being incidental, and gives an honest caveat about the setup path itself changing over time rather than promising a fixed procedure.