[German]Microsoft released an update for Windows 10 Fall Creators Update on March 5, 2018. This update is intended to fix USB problems on machines running this version of Windows 10. But the update has know issues.
Advertising
Some background
In February 2018 Microsoft released a series of updates for Windows, Office,. NET Framework etc. in February 2018. Some users have encountered problems with these updates (see my blog post Issues with Microsoft's February 2018 updates).
Cumulative update KB4074588 causes some USB devices such as notebook cameras etc. to be unrecognized under Windows 10 version 1709. The keyboard and mouse will no longer work either.
Microsoft stated that this behavior may occur if the Windows Update Servicing Stack incorrectly skips the installation of the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.
Furthermore, this cumulative update was responsible for further problems with context menus or the "Inaccessible boot device" error with BlueScreen. Read more about this below.
Update KB4090913 for Windows 10 Version 1709
Microsoft says, update KB4090913 (released March 5, 2018) for Windows 10 Version 1709 includes quality improvements. But significant is the following bug fixed by this update:
- Addresses an issue in which some USB devices and onboard devices, such as a built-in laptop camera, keyboard, or mouse, stop working. This may occur when the Windows Update servicing stack incorrectly skips installing the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.
So, Microsoft hopes, that after installation of this update, the Windows Update Servicing Stack works as designed. Update KB4090913 is cumulative, so only the new fixes that are contained in this package and hasn't been installed will be downloaded and installed on your device.
Advertising
Install requirement: Compatible AV program
The update is rolled out via Windows Update or made available for download in the Microsoft Update Catalog. But the update will only be installed if a compatible antivirus solution is available under Windows 10. The installer checks whether the antivirus solution installed in the HKEY_LOCAL_MACHINE branch in the registry checks the subkey:
SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat
for a DWORD value cadca5fe-87d3-4b96-b7fb-a231484277cc set to 0x00000000, as Microsoft writes within the kb article.
Other known issues
According to the Microsoft description, it seems that only the USB problem has been fixed, but the other bug that has been included in the cumulative updates for some time has not been fixed.
- Windows Update History continue to report that KB4054517 failed to install because of error 0x80070643. That's wrong, even though the update was successfully installed, Windows Update incorrectly reports that the update failed to install. Select Check for Updates to verify that there are no additional updates available.
- There is another error in the Active Directory (AD). Due to a problem with the AD FS-Server (AD FS stands for Active Directory Federation Services, see) the WID AD FS-Database (WID = Windows Internal Database) seems to become unusable after a restart. In this case it may happen that the AD FS service cannot be started. Seems to concern only Windows server farms, I guess. There is a cool workaround: The broken database cannot be repaired. You have to restore the AD FS-Server to working order by restoring a working backup.
- Also this update can send machines in an INACCESSIBLE_BOOT_DEVICE error with BlueScreen after installation. This problem occurs if the Windows Update Service Stack incorrectly skips the installation of the newer version of some critical drivers in the cumulative update and uninstalls the currently active drivers during maintenance.
Regarding the last issue I'm puzzled, because Microsoft wants to fix this, as mentioned in the KB article. I'm very unsure if there's just an old text left. It's this combination of old bugs that have been dragged along for months and often inaccurate descriptions in Microsoft KB articles that makes me doubt whether this is all on the right track.
