Not likely, then we would already have seen it, the 2 would mean a fully new compiled build, not by an update (like with 18362 > 18363), but all can happen these days.
No sh*t, Sherlock! That was most certainly meant to be ironic. Not everyone appreciates all of the clusterf*ck Start Menu MS has created, luckily, OpenShell and similar tools allow us to avoid it.
Keep getting this in the setuperr.log when doing a inplace upgrade with this build [RelPost.exe] RegOpenKeyEx(RecEnv) failed: 0x2 Anybody knows how to fix this ?
Hey, This is mine after a successfull/smooth upgrade from 1909. When I right click on temperature and select copy then paste in Notepad: GPU 0 NVIDIA GeForce GTX 970 Driver version:26.21.14.4237 Driver date:2/13/2020 DirectX version:12 (FL 12.1) Physical location:PCI bus 1, device 0, function 0 Utilization0% Dedicated GPU memory0.3/4.0 GB Shared GPU memory0.0/8.0 GB GPU Memory0.3/12.0 GB So temperature is not included! Bug? Yes?
I try now and then to upgrade if a new build is released, however I seem to have nowhere to hurry, as I have an sli setup, which is mutually exclusive with hardware gpu scheduling. And I'm not upgrading for some new icons either, i am more interested in performance.
Well the build isn't technically released yet although they're doing it a bit differently this time so apparently it's 19041 and that's it but over March and April I assume with a planned release for early or mid May perhaps these remaining issues are being resolved via cumulative updates instead and lengthier testing while remaining on the same build and then development is progressing with 19500.xx for what will eventually be the next Windows 10 version but from what I understand the fast ring is more experimental and a preview of what's to come now not just a skip ahead to 20H2 as Microsoft wraps up development of this 20H1 build for the slow ring and I assume release preview shortly after it's considered release worthy a bit ahead of general rollout. Next up should be the March cumulative but it's possible this build is outside of the regular cycle though I think the previous .81 update coincided with the monthly patch Tuesday routine but it might not mean anything and if it needs to be fixed Microsoft will just roll out a update or several until the build is up to whatever quality standard is considered good to go. (Although waiting one or two months for some extra updates wouldn't really hurt.) EDIT: Not that I know much of what's going on here though it's just bits of what I've heard mostly. For new features and functionality I assume the drivers also have to be up to speed but NVIDIA already has some 450.xx branch WDDM 2.7 driver that should fit that criteria so if that's installed yeah probably a OS issue that needs to be resolved. The prior boot issue should hopefully be fixed now and then whatever else remains after that so still a ways to go but probably fairly good for general usage as long as the user is aware that there are still some problems and things to fix before it's truly finished or what to call it. EDIT: Suppose with the ESD's or converted ISO's passed around as 19041 / 20H1 / 2004 and so on as if it were finalized the build is also spread over from just the opt-in beta/testing channels and users might decide to try it that way too without being part of the insider program and all that.
No amount of customization will turn the Windows 10 Start menu into the one I want - the Windows 7 one. If you are satisfied with it, use it. You will only receive public updates for that build. 19041 updates are public, so, yes. Here is a cool topic that might help you with Insider updates: https://forums.mydigitallife.net/th...ider-program-without-microsoft-account.80145/