KB5001478 Windows 10 Insider Preview Dev Build 21332.1010 - March 15  

With the millions and millions of different hardware configurations and types of printers running out there, it would be very difficult for MS to target all the issues (bugs) beforehand even with the work of AI. Bugs are probably the only way for them to find out. We are all curious and cannot sometimes resist the temptation of installing a new update—including myself.

That is why it is wise to take a system image backup before applying any major update. I am pretty sure almost all TF's members follow this rule. First thing to do when facing these kinds of bugs is to roll back; that way it is very easy to pinpoint that the bug (issue) was caused by the new installed update if everything gets back to running normally after that. At this point, one can always wait until there is a fix for the issue at hand.

waltc said:

Doesn't seem to have anything to do with a specific driver, as I've related in some detail, several times now...

The problem appears to be that new Windows builds of late seem to be improperly installing those drivers when a new build is installed--likewise, even the troubleshooter fails to properly install it. All of the drivers (there are no exceptions) stay up permanently when installed through the Device Manager, manually. I have no idea why this isn't being understood as I've taken pains (and screenshots) to illustrate it plainly. This is a Win10 bug relative to Windows automatic driver installs for the RealTek 2.5GbE LAN drivers.

Just to explain, again--if it was a driver problem then the manner of installation would have no effect and the driver would continue to drop offline, even when manually installed. Since this doesn't happen, we know it's not a driver problem but a problem with the Win10 automatic driver install relative to the Realtek LAN driver installation. More to the point, this issue is relatively recent, and going back 2-3 months in builds, it did not occur with the Realtek drivers whenever a new build was installed. The same drivers I used then now fail to install properly when a new build is installed or the troubleshooter is invoked--but they work fine when manually installed.

I see, thank you for the explanation!

waltc said:

Doesn't seem to have anything to do with a specific driver, as I've related in some detail, several times now...

The problem appears to be that new Windows builds of late seem to be improperly installing those drivers when a new build is installed--likewise, even the troubleshooter fails to properly install it. All of the drivers (there are no exceptions) stay up permanently when installed through the Device Manager, manually. I have no idea why this isn't being understood as I've taken pains (and screenshots) to illustrate it plainly. This is a Win10 bug relative to Windows automatic driver installs for the RealTek 2.5GbE LAN drivers.

Just to explain, again--if it was a driver problem then the manner of installation would have no effect and the driver would continue to drop offline, even when manually installed. Since this doesn't happen, we know it's not a driver problem but a problem with the Win10 automatic driver install relative to the Realtek LAN driver installation. More to the point, this issue is relatively recent, and going back 2-3 months in builds, it did not occur with the Realtek drivers whenever a new build was installed. The same drivers I used then now fail to install properly when a new build is installed or the troubleshooter is invoked--but they work fine when manually installed.

@waltc,
That is just your assumption, you don't really know that unless you compare the Realtek driver file that is loaded when it fails with the one that is loaded when it works. The driver file that fails could be corrupted or simply a bad driver.
You could use a utility to compare the driver file that fails with the one that works and find out for sure which one is the case.

This build has big issues with my system , m.2 issues , locking up and restarting , but on SSD , no issues at all . will stay on SSD till next build, see if indeed it is a build issues.

Bench Virgin said:

This build has big issues with my system , m.2 issues , locking up and restarting , but on SSD , no issues at all . will stay on SSD till next build, see if indeed it is a build issues.

Yep. 21332 doesn't play nice with M.2 NVMe disks. I suspect its due to a buggy NVMe driver.

Calendar not showing when click the taskbar clock on this build. Any suggestions?

jyusa said:

Calendar not showing when click the taskbar clock on this build. Any suggestions?

@jyusa,

No idea, it shows up normally on my 21332 machines when I click on the taskbar clock..