Same for me, forgot to mention previously. Welp, I reinstalled Windows and wanted to set up my dev stuff with dev drive but I guess I'll just stick the 'normal' ones, unless MS releases new Beta build this week and fixes this.
I don't know what this means. Are you trying to say the current state of the beta channel is not buggy as hell? No one is tweaking anything to break the beta builds if that is what you are trying to say. Microsoft has that covered.
So the latest update "August 22, 2023—KB5029351 (OS Build 22621.2215) Preview" made my PC BSOD at bootup with a "UNSUPPORTED_PROCESSOR" error code. It auto rolled back the update after a few reboots. It's quite insane that they mess with supported cpus still and allow the update to install on what they think is unsupported causing such problems. Specs: Intel Core i9-13900K on a MSI PRO Z690-A DDR4 with newest BIOS (7D25v1D)
I noticed that on 22631, unlike 22621 (and even 25xxx) is impossible to get the signature enforcement disabled permanently (f8 at boot still works). Not sure if that's a bug, the intended behavior, or the result of a glitch in the UUP conversion process @abbodi1406 Are you aware of any official change / mention about that from MS?
Ivy bridge still works even using the infamous 259xx builds, only older CPUs are affected (say my Turion X2, or core 2)
the idea of the beta channel was to give us a stable platform for testing new features( since the launch of 3 or 4 channels), yet they break the os where new features have nothing to do with whats broken i still they doing this sh*t on purpose just for kicks explorer gets a pass as we testing new features...doesn't excuse the rest of the bugs that are accumulating in each CU
Have been running every 22631 beta, gottta say that 22631.2199 is by far the buggiest release so far.. What a pile of horse S..T!
Maybe we just got interns working in beta department, dev department seem to be far better with what they do If it wasn't for the timebomb and installing full builds ...i would of stayed in dev
No one is changing anything for the beta to be buggy ya moron. Look around. Right click is still transparent. The downloads folder sorting is still broken. Explorer is still slow and laggy. The check for updates button is now missing. Properties option for drives now crashes explorer. Gaming performance is lower as well compared to the stable builds. The beta is a mess right now. You two seem like complete morons for even asking or thinking people using tweaks are the reason for the bugs.
Many years ago, when I was on the Windows95 launch team, the term "Beta Means Broken" was coined. I'm not certain if that term applies to Windows 11 beta now. I just commented because I was joking around.