I already know that! My question is specifically about visible feature/functional differences. Thank you. So it basically gets more stable updates! I have a standard installation with updates enabled, so I'll probably get these features a bit later once they've been tested on 26H2
That would be the part, it will be merged with mainstream build at the next major new release, most likely to be 27H2. It just gets hotfixes like all other builds.
Anyone else experiencing installation problems at first reboot during initial setup? My VMware Windows 10 test (legacy bios/no secure boot) VM does not boot at first reboot, on the ancient (legacy bios / no secureboot) laptop it installed fine. 28000.3231 with or without bootfiles updated, both behave the same.
Did you use the modern or the classic Setup? I have experienced issues in the past when using modern Setup and a legacy BIOS install. Sometimes it just does not make the disk bootable and it stops after the first reboot. Classic Setup always worked fine in these cases. Note: This isn't always occurring, no rhyme or reason. Edit: You mean 28000?
I use my fixes for setup on unsupported hardware, including the autorun.dll from 22621, so only legacy setup shows at boot. Ofcourse i tried different scenarios, including the real hardware test on a vista era legacy bios only first gen i3 system, it installed fine. On a windows 11 supported VM in VMWare it worked fine too.
Nope, i leave it 29000, people can come run and ask for it, over and over and over Nah, fixing it. ps, on a vbox windows 10 x64 vm it installed fine, weird, problems on vmware only this time
Is it just me, or does 28000's MS Store not work properly on x64 hardware? It seems to have issues downloading app updates and such. In fact I wonder why does 26H1 exist for x64 at all. Its very weird.