CO-Release Build 21364 to Dev Channel + KB5003397 + KB5003402 to .1011

 FG, I don't know what the difference would be.  All my test PCs are several year old Dell desktops with Intel CPUs.  I don't use virtualization or Linux, but all PCs are multi-boot 64 bit Dev channel, FWIW.  I have 3 printers, two Samsung lasers and one HP multi-function laser.  I don't know if any of that is relevant, but I saw you or somebody mention Brother printers - that's a brand I don't have.

I connected to the pc I have:

Samsung ML2010R

HP Photosmart B109

and both from version 21354 onwards do not work with the exact same problem described in the previous comments, last night I went back to build 21343 and as if by magic the printers started working again, the problem itself is that in the Insider Blog it is described as problem solved is actually not solved, since I'm not the only one to encounter this problem you probably see that Microsoft still has to fix the bug

Hi Eddie, 

Another fix mentioned in the blog which doesn't seem to work.

Disk1 here is an HDD not an SDD. Looks like they still show all disks as SDDs.

• We fixed an issue where the “Manage Disks and Volumes” page in Settings was incorrectly displaying HDDs as SSDs.

https://aka.ms/AAb4rf8  Manage Disks and Volumes shows internal SSD even when it is an HDD.

Same here: my HDD Disk 1 is shown as SSD

 FG, I don't know what the difference would be.  All my test PCs are several year old Dell desktops with Intel CPUs.  I don't use virtualization or Linux, but all PCs are multi-boot 64 bit Dev channel, FWIW.  I have 3 printers, two Samsung lasers and one HP multi-function laser.  I don't know if any of that is relevant, but I saw you or somebody mention Brother printers - that's a brand I don't have.

Nothing to do with the USB printer problem which in my case is an HP LaserJet 1020 that fails. 

This is yet another machine which doesn't even have a printer.

The W.U. to 21364.1 works fine and completes with no errors.

The error below occurs afterwards when W.U. checks for updates again and tries to install kb5001030.

Perhaps is another one of those regional mistakes, where are you located ?

I saw other users saying W.U. does not even try to download and install kb5001030 ?

FG, I don't know what the difference would be.  All my test PCs are several year old Dell desktops with Intel CPUs.  I don't use virtualization or Linux, but all PCs are multi-boot 64 bit Dev channel, FWIW.  I have 3 printers, two Samsung lasers and one HP multi-function laser.  I don't know if any of that is relevant, but I saw you or somebody mention Brother printers - that's a brand I don't have.

FG, I haven't seen any problems with kb5001030 or any other update, just that last 8th update with a code had a couple of 8s and half dozen 0s.

Weird, many users have reported it and I got it on every machine, I wonder what the difference is ?