You were probably entering a key that didn't align with the upgrade path that Windows allows. I think using an ei.cfg will bypass that and pick the right index for you. For example, if you were using Enterprise and entered a Pro key.
Anyone try VR with Oculus on 21966 yet? In my case, with Oculus Link, my GPU encoder starts dropping frames like crazy after exactly 25 seconds of starting a VR app. The process is: Start Link Launch VR game Play VR game fine for 24 seconds After 25 seconds, everything becomes a stuttery mess To confirm the stutter, using Oculus Debug Tool to show Performance Summary HUD, both application and compositor start dropping frames consistently and the counter climbs after 25 seconds. Never seen this happen in W10 or at any point prior to this. I assumed it was the graphics driver at first (using WDDM 3.0 drivers from AMD), but it still happens even after downgrading the driver all the way back to 21.11.1 (WDDM 2.7). I have a RX 580 and Oculus Quest 2. This happens on both wired Link and Air Link. Seemingly doesn't happen with Virtual Desktop though. Edit: Seemingly an issue only on 21996. Reinstalled W10 19043 and Oculus Link works fine, even with the WDDM 3.0 drivers from AMD (but only advertising 2.7 with 19043).
Installed and activated. Thanks again for the help guys, much appreciated. And with that, I bid yee all, a good night...
Spoiler How did you got these copies of legal Notice . Are you {Global Online Investigator} at {Collaborative Online Investigation Network Team} or [M$ Legal Response Team Employee] [COIN]
I always liked the Toolbar system. Windows 10 has some extra aspects compared to macOS. It doesn't exist on windows 11, for me it's a reason not to switch to Windows 11.
I believe Windows 11 is going to drop IA-32 support. This is the reason I think no 32-bit ISO for build 21996 was made available -- there is no 32-bit/IA-32 version of 21996 available. If I'm right, this means that on June 24, when MS publishes ISOs, there won't be 32-bit ones. This would make Win11 the first client Windows release to remove support for older IA-32 CPUs.
Maybe some people should stop rubbing and playing with their crystal balls ? @ Mods ........ what about a new section ....... called ' Computer orakel ' ? For the people that make predictions .
Build 21996 was not official MS release, it was a build supplied for OEM testing which got leaked and OEM ship system with 64-bit OS. As abbodi1406 posted earlier here reference to x86 can be seen.
This would be the best thing to happen. x86 is a dying architecture and was outdated even at the launch of Windows 10.