Windows 11 CO-Release Build 22000.51 is out to Dev Channel

I'm reporting and hoping for confirmation of 2 new bugs on a clean installation of 22000.51 done from ISO a few hours ago.

1. Unable to dismiss setting up OneDrive

2. Windows 10 style menu

You are right. Shouldn't have a delay .

Something I ran into though:

One of the Nvidia updates pushed from Microsoft really confused my system. I had to download a 'fresh' driver from Nvidia and do a 'clean install' with it to fix the issue. It caused the monitors to be mis-identified and the monitor ID for the two monitors was opposite when comparing Windows ID and Nvidia ID. During the last several months when I have gotten a driver update from either party the update always turns off my second monitor. I have isolated the problem to Nvidia and not Microsoft. For some reason the Nvidia driver does not 'see' my settings for the two monitors (both Dell Touch monitors, 24 inch) and turns one off whenever there is a new driver.

Have been coping with it and reported to Feedback Hub my findings.

Anyway, might be worth it to reinstall the driver to be sure.

Looks like you have a pretty nice system.

My Nvidia driver is already the latest available for the RTX 2060.

Hi John,

IF one was a registered Dev Insider on or before June 24th they waived (for lack of a better word) the hardware requirements so we could take the next Build after 21390, which would be our 1st Win11 Build. BUT that is an Insider Build. So, I think, be I right or wrong 🤷‍♂️, once it goes GA, a machine will have to meet the requirements. Unless one stays on Insider Builds, then could continue. Of course beta Builds are only for testing, not regular, daily use.

Cheers,
Drew

You are right. Shouldn't have a delay .

Something I ran into though:

One of the Nvidia updates pushed from Microsoft really confused my system. I had to download a 'fresh' driver from Nvidia and do a 'clean install' with it to fix the issue. It caused the monitors to be mis-identified and the monitor ID for the two monitors was opposite when comparing Windows ID and Nvidia ID. During the last several months when I have gotten a driver update from either party the update always turns off my second monitor. I have isolated the problem to Nvidia and not Microsoft. For some reason the Nvidia driver does not 'see' my settings for the two monitors (both Dell Touch monitors, 24 inch) and turns one off whenever there is a new driver.

Have been coping with it and reported to Feedback Hub my findings.

Anyway, might be worth it to reinstall the driver to be sure.

Looks like you have a pretty nice system.

Hi Johnny,

I remember that, but in my case W.U. always offered the kb5004564 and was already downloaded when I created my first ISO.

but it created just 22000.1,

Probably it did not add the option in the converter to include all updates.

I now have both ISOs with or without kb5004564.

There is an option in the ConvertConfig.ini.

Guessing the CU windows10.0-kb5004564-x64.cab may have been in another folder in SoftwareDistribution when you created the ISO. Did you locate that file.

If you were using wimlib, with all the recent updates, possible it did not add the option. Forget which version, but one it did add updates, but the convert to esd option failed (skipped). Had to compress install.wim manually for flash card. Have not come across adding updates failing, unless I possibly got distracted and did not hit the proper keys.

Regards.