You people are the exact opposite of antivaxxers antiupdaters You thrive after the next dose of updates, even if you're not meant to install it on a "production" PC. Me likes test subjects - less issues to hit me. There's not even much to gain from it. I've read the pathetic release notes and it's like 75 percent about IME, emoji, japanese support. And GameBar. Right. Did not even fully fixed kerberos issues introduced in the last update.
same problem, can't update from ,661 t0 .662, the problem is that net framework 3.5 is broken by .661, can't be reinstall correctly, had to do in place upgrade
Same here, in place upgrade with a 19042.662 ISO and everything works fine now, even reinstalling the *.cab KB4586853 (19042.662) to testing.
remove/uninstall .661, reboot and then use DISM to install the .662 CAB version of KB4586853 I got much more success installing KB4586853 build .662 on both 2004 and 20H2 PCs on top of older CUs like KB4586781 (.630) or KB4594440 (.631)
better choice fresh install 19042.630 don't update like to .631 or 662 only on the 2nd Tuesday with windows update, 21/h1 will be here soon and it is doing real well...
does ei.cfg still work on latest windows 10? For able to choose windows edition pro or home when reinstalling
Hey. A question. Why did Microsoft update ISO 1809, 1903, 1909, 2004 to the latest builds in November, but the most recent and required 20H2 is not there?
Born yesterday? They want to make sure they can switch you to 20H2 or at least to using ChrEdge, by "accident" or otherwise (you conceding to the marketing).
Chredge isn't required for Windows 10, not as an aliased application and not as a background app. I refuse to use it. Unless one works for MSFT, interpreting their motives is risky.