I’ve been on 22H2 for a while and it’s been one of the buggier builds thus far, lots of green stop errors due to drivers and poor memory handling.

Hopefully this full release will have fixed the issues.

I'd still be using SEVEN if it wasn't for the "upgrade" to DX12 on my gaming machine. I have no plans to upgrade until I'm literally forced to by the games I play.

luckybob wrote on 2022-09-23, 03:29:

I'd still be using SEVEN if it wasn't for the "upgrade" to DX12 on my gaming machine. I have no plans to upgrade until I'm literally forced to by the games I play.

I’m at the point I want to roll back to Windows 10, the amount of driver issues Windows 11 is causing with up to date drivers is obnoxious.

I don't get it, after all these years you'd figure MS would have all this down cold by now. I'm a happy camper with 10 till 2025 or however long it can be stretched out.

Even Windows 10 had it's share of bad, buggy or downright broken updates. Seems Windows 11 is even worse in this regard.

I simply do not remember bad windows updates even being a thing before Windows 10. There were pretty consistent improvements in stability from Win95 to Windows XP, it more or less plateaued through Windows 7, and seems to be falling off a cliff now.

Was using Windows 10 until last week, then some blue screens started to show up (the error code being different each time).
Used their own memory diagnostic program and it accused my hardware for being bad. Then I used memtest86 and after running it overnight the result was that my memory was fine.
Not sure what caused that, probably update or messed driver, but everything was solved after a fresh install (even MS diagnostics program says everything is ok now), I used Windows 11 for the fresh install and it's running OK. Guess the problem is not Windows 11 per se, but having to install update after update which eventually break things up.
OSes are treated as a service nowadays and Win 10 will not receive the same care as Win 11, meaning the chance of updates breaking Win10 becoming more and more likely as MS surely will not test it with the same care they do for Win 11 (which is already not that much to begin with).

Windows 11 honestly has nothing to offer for me. On my daily driver I have a dual-boot of Windows 10 and Debian and see no reason to bother with Windows 11 at all. I'm just holding out till l2025 and hoping that some games I need windows for or certain mod tools become compatible with Linux/Proton.

I did try out Windows 11 when it was still brand new but it was such a downgrade and I basically "hacked it" to basically have the Windows 10 taskbar and explorer (but still having openshell for the start menu)

11 has been flawless on my personal machine and workstation. My laptop has been another story, but I think Lenovo screwed it up with a bad BIOS update.

I will say that the only way I can tolerate 11 over 10 is using the Explorer Patcher taskbar and start menu.

Namrok wrote on 2022-09-23, 13:19:

...I simply do not remember bad windows updates even being a thing before Windows 10....

Problems with official Windows updates are not new phenomena, e.g.
https://www.cnet.com/news/privacy/post-sp3-pa … windows-update/.

ptr1ck wrote on 2022-09-23, 15:37:

11 has been flawless on my personal machine and workstation. My laptop has been another story, but I think Lenovo screwed it up with a bad BIOS update.

I will say that the only way I can tolerate 11 over 10 is using the Explorer Patcher taskbar and start menu.

11 was great until 22H2 . .whatever they did that update has been the bane of my PC, more often than not its windows being overzealous with how tightly its controlling memory handling which is causing a lot of driver issues.

Perhaps they changed how windows 11 handles memory security in 22H2 but forgot to pass the message on to driver devs, even the latest nVidia drivers fall afoul of this, got a new set of intel updates for networking last night so hopefully the green stop screens resolve themselves.

If they continue Ill simply nuke and pave and see if a fresh install helps.

Can't roll it back?

I just installed it on my son's PC last night. Let's see how it goes on his 1060.

Looks like a fix is coming for the NVidia GPU performance issues.

https://www.guru3d.com/news-story/nvidi ... pdate.html

TrashPanda wrote on 2022-09-24, 09:43:

11 was great until 22H2 . .whatever they did that update has been the bane of my PC, more often than not its windows being overz […]
Show full quote

ptr1ck wrote on 2022-09-23, 15:37:

11 has been flawless on my personal machine and workstation. My laptop has been another story, but I think Lenovo screwed it up with a bad BIOS update.

I will say that the only way I can tolerate 11 over 10 is using the Explorer Patcher taskbar and start menu.

11 was great until 22H2 . .whatever they did that update has been the bane of my PC, more often than not its windows being overzealous with how tightly its controlling memory handling which is causing a lot of driver issues.

Perhaps they changed how windows 11 handles memory security in 22H2 but forgot to pass the message on to driver devs, even the latest nVidia drivers fall afoul of this, got a new set of intel updates for networking last night so hopefully the green stop screens resolve themselves.

If they continue Ill simply nuke and pave and see if a fresh install helps.

I had to reinstall Windows 11 21H2 (and I put 22H2) because it wouldn't run DOSBox from any media (USB, HDD, OS SSD) having a folder named "Program Files nnn", where nnn is any or no text. Plus it wouldn't run MSI Afterburner because it apparently couldn't find somd d3dx11_....dll file and also it freaked out on opening PDFs 😵

I'm staying off of 11 as long as possible. I learned my lesson with Windows 10 and it's "rolling development" feature problems.

I think I've been on 22h2 preview since early July, in a unsupported system (no TPM, 2nd gen i5), I think it updated to the final release version of it; I haven't had any issues

Looks like the Nvidia issues are related to GeForce Experience. I've never used that bloatware garbage.

I updated to the latest NVidia whql beta drivers and they fixed the green stop screens

Most of the instructions you will see are for bypassing the requirements when you have Windows already installed and you are running the setup from within Windows. In that case you can delete a file or run a script.
If you want to install from media then most instructions are for using rufus to create a bootable USB.

The following is for bypass the requirements while booted from ISO which for some reason has been difficult to find info on (these registry changes could also likely be added to boot.wim negating the need for this file):

Place the following in a file called "bypass.cmd"

1@ECHO OFF
2REM 1. Place batch file in root of ISO using AnyBurn
3REM 2. At install screen press shift+F10
4REM 3. Type in "D:\bypass.cmd"
5reg add HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig /v ByPassTPMCheck /t REG_DWORD /d 1 /f
6reg add HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig /v BypassSecureBootCheck /t REG_DWORD /d 1 /f
7reg add HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig /v BypassRAMCheck /t REG_DWORD /d 1 /f
8reg add HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig /v BypassStorageCheck /t REG_DWORD /d 1 /f
9reg add HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig /v BypassCPUCheck /t REG_DWORD /d 1 /f
10setup

gaffa2002 wrote on 2022-09-23, 13:59:

Used their own memory diagnostic program and it accused my hardware for being bad. Then I used memtest86 and after running it overnight the result was that my memory was fine.

Well that is strange. Isn't their memory diagnostic program run at boot time? It should not be affected by any drivers or the like.
I'm no fan of Windows, but I still find it hard to believe they would mess this up. Personally I'd really suspect the hardware, maybe it was temperature or something.