Comment by EvanAnderson

> My favorite trick is to install with English (World) language to avoid auto-install of all sorts of crap.

Edit: This sounded neat so I tried it. I just loaded up a physical box from a 24H2 ISO on a thumb drive (booted from Ventoy with no special options loaded to bypass the Microsoft Account requirement).

I got an oddball "Something went wrong" / "You can try again, or skip for now" / "OOBEREGION" window with a silly and wholly inappropriate for a corporate-targeted OSA depiction of a dropped ice cream cone (pink flavor, by the look of it). I've definitely never seen this one before.

I clicked "Skip" and then it proceeded thru the OOBE as I'd expect, including demanding an Internet connection.

I added "BypassNRO" to the registry, rebooted, and completed the OOBE with a local account (seeing the same silly ice cream cone again).

Once I got into Windows I found the Start menu looked a little emptier than normal. Memory usage seems a little lower than I'd expect. The running process list is still ridiculously long.

I connected the Ethernet to a network with Internet access and didn't see a huge change.

The Store app doesn't work. It returns "Sorry about that!" / "Something went wrong...".

The Co-Pilot pinned shortcut returns a blue modal error dialog in the Windows 8 style saying "Search Support" / "Something happened on our end ... 0x87E10BC6".

Installing this way definitely did something. I'm just not sure exactly what. It'll be interesting to see what happens when the machine updates. I already see it loading drivers and doing device detects.