You do know not everyone at Microsoft is back to work until Mon. 6 Jan. 2020 ???? So don't expect a New Build till next week at the earliest. .
From 19035 something is wrong with the releases at storage driver/chipset level, in VMWare scsi doesn't work anymore and had to be replaced with normal sata or nvme to be able to upgrade or clean install it.
19041.1 i been running almost 2 weeks i say it is snappier then 1909 i am just concern about security issues since it is not release to public as of yet
Yes, that's indeed the case with 20H1 that I've noticed too, even after making the ISO in GPT-UEFI+Fat32 schematic with latest Rufus, it still shows 'Loading files...' screen before booting up into the ISO, just like GPT. Don't know what MS changed in this branch. Also, I'd like to ask everyone who've been using this build that is the Windows Settings header is enabled in this 19041 build by default or not? In my case, it isn't and I need to run the mach2 with command in order to get it enabled. This feature is supposed to be there in 20H1 as per MS statement, right?
For me the Header in the settings showed up after I set my Microsoft account in the insider settings, after a couple of days/reboots, and it disapear after a couple of days/reboots if I remove my Microsoft account from the insider program page in the settings.
i would wait for them to start sending updates to patch what ever security issue it my have...i would not run this as a primary OS.
Why would you not run it as primary? I have run all flights as primary, after all that's what being a insider is all about. Where is your sense of adventure it's like man up. Every once and a while you have to take a MS blow to the chin in order learn. What ever way you want to look it. It's what we do as Insiders.
But that takes all the fun out of it. I keep a full back up of all releases so if anything goes wrong I just re-set the accepted release aka GA release.
Like I stated I keep full back up of everything. So I don't worry at all about that. Needless to say I have had a few times where the MS software has had me bent over the keyboard. I learned to remain anally retentive working with Winblows.
everything I have is a test machine. Sometimes I try to break it just so I can fix it and learn from it.