From: marianjones@helpfulpeople.com   
      
   Paul wrote:   
   >> That is, maybe we can get all the latest updates (without being in the   
   >> extended-support program) up to early October 2026 by simply using the   
   >> latest ISO of that time in the future, to "repair" our Windows 10 setup.   
   >>   
   >> Dunno.   
   >   
   > You should install old media, with the network cable disconnected.   
   >   
   > This prevents the installer from attempting to download 22H2 to replace   
   > your entire session :-/ The installer had in-flight upgrade capability   
   > for some number of years.   
   >   
   > As a test, some Insider versions had DVD files with short duration signing,   
   > and the DVD would no longer boot for fresh installs, past a certain date.   
   > I've not heard of any other media situations where that was employed.   
      
   Hi Paul,   
      
   Happy New Year!   
      
   Thanks for the warning of the "in-flight" switcheroo!   
      
   I should have noted that we refused the network connection near the   
   beginning of the installation process, as that's just habit learned the   
   hard way. So I was unaware of this "in-flight" switcheroo you speak of.   
      
   I believe you though.   
   Oh, I believe you.   
      
   So I'm glad, out of sheer habit, we refused not only all the telemetry   
   options, but also we didn't sign onto the network until we set up Windows   
   10 the way we wanted it to be set up (specifically with a local account).   
      
   I also wasn't aware of time-limited DVD ISO installs either, so that's   
   another potential gotcha, but these were official release ISOs luckily.   
      
   I've been googling the problem set, and I think no matter what DVD ISO we   
   use to install/repair Windows 10, that Microsoft updates it to 22H2 anyway.   
      
      Windows 10 1909 is not eligible for the "enablement package" shortcut.   
      Only versions 2004 -> 22H2 can use the tiny KB5015684 switch.   
      So if we install 1909, Windows Update will:   
       a. Download the full 22H2 feature update (3-4 GB)   
       b. Perform a full in-place upgrade   
       c. Reboot several times   
       d. And finally, land us on 22H2   
       
      
   BTW, THANK GOD we didn't try to install while we were connected to the net!   
   As you noted, "in-flight" upgrades may very well have been substituted.   
   Which would have taken forever when we least had the patience to wait.   
   As we didn't know if the repair was gonna work at that early stage.   
      
   Thanks for the warning of the "in-flight" switcheroo!   
      
   Luckily, we dodged that one by habitually never turning on the net until   
   necessary, and certainly it wasn't necessary while we were installing.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)