KB5004123 CU Windows 10 Insider Preview Dev Build 21390.2025 - June 14 Insider

Edwin said:

Simple File Explorer search won't work cuz I uninstalled Edge!!! What kind of horsesh*t is that!?!?!?

Search me!

Just get in the office and seeing this one... Downloading it now!

OK, finally got a break and figured this thing out. I hope my time-consuming experience will help someone else out. Here's what I wrote at the Hub:

"It all boils down to a single setting in the AMD Adrenalins...the setting is the 10-bits per pixel setting (see screenshot) that causes a black screen upon reboot--this option requires a reboot after it is turned on. Suspect it's a Windows bug because up to and including build 21370, the 10-bit pixel switch ran fine without problems. Also, both monitors I've used with the beta builds up through 21370 are 10-bit monitors and I haven't seen a problem yet. Problem has affected every build post 21370. This took awhile to narrow down to this precision and so I certainly hope it will help you post 21390! I've repeated the steps to get the black screens several times--just install a 5700XT running the latest Adrenalins, 21.5.2, turn that option on if you have a 10-bit monitor, and reboot per driver instruction, and when you come back up you will be in a unrecoverable black screen. Do a system restore before throwing the switch! I advise that strongly... What a relief !"


So glad to have solv-ed the problem, as Clouseau would say... So 21390 is up and humming along. Finally got something to run properly after 21370--was beginning to think I would be there until October...! The problem was that when I'd try upgrading to 21376/82/87 from 21370, I already had the 21.5.2 Adrenalins installed with the 10-bits-per-pixel option turned on--and so each attempt to upgrade was met with a black-screen failure to boot. It finally dawned on me in subsequent testing that it was only after turning the 10-bit option on and rebooting as instructed by the driver that the black screen bug appears--so that turned out to be the problem--a single GPU driver option the latest Win10 builds do not like (albeit all builds up to and including 21370 never had a problem with it.)

Here's the screenie I left at the Hub:



Forgot to crop out the white space...sorry, old boy...for those who might not be fully conversant with this, several months ago AMD added this 10-bits-per-pixel switch into the Adrenalin drivers...AMD already had a 6/8/10-bit monitor output switch located in another spot in the drivers and it is still there, in addition to this newer option. The 10-bits per pixel switch instructs the GPU to render each pixel at 10-bits of precision/depth internally, and if the monitor output is set to 10-bits, as well, then as long as the monitor is either a straight 10-bits or 8-bits + FRC dithering (for 10-bits), the AMD GPUs will now fully output 10 bit pixels.

Update completed well. The duration time was 40 minutes like it's predecessor, not the best I have had but okay.

All seems to be working for now.