Newsletter Archives

• Patch Lady – proving that documentation is key

  Posted on March 7, 2018 at 01:40 CST by Susan Bradley • Comment in the Forums

  Patch Lady here:  Tonight I noticed that the recent update for Windows 10 1709 KB4090913 now includes the following in the release notes indicating that it DOES address the problem with the race condition that occurred in the January and February updating cycles.

  • Addresses issue where 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.  (that sentence was there before)
  • Addresses issue where some devices may fail to boot with “INACCESSIBLE_BOOT_DEVICE”.  (AH HA, this is new!)

  That last one was not in the original KB release.  So now that it appears that this KB does help prevent this issue, let’s look at the issues left to worry about:

  Windows Update History reports that KB4054517 failed to install because of error 0x80070643.

  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. You can also type About your PC in the search box on the taskbar to verify that your device is using the expected OS build. Microsoft is working on a resolution and will provide an update in an upcoming release.

  This is a minor cosmetic-y issue in my opinion and can be (annoyingly) ignored.

  Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY.

  Contact your antivirus manufacturer to verify that their software is compatible and that they have set the following REGKEY on the computer: Key=”HKEY_LOCAL_MACHINE”Subkey=”SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat” Value Name=”cadca5fe-87d3-4b96-b7fb-a231484277cc” Type=”REG_DWORD” Data=”0x00000000”

  That is a standard “known” issue after the Spectre/Meltdown patch era and will be included as a known issue going forward for all cumulative updates.

  Because of an AD FS server issue that causes the WID AD FS database to become unusable after a restart, the AD FS service may fail to start.

  There is no way to undo the database corruption. To return your AD FS server to a functional state, you must restore it from a backup.

  That side effect only impacts customers running 1709 Server core and Windows server 2016.  While concerning (and pointing out that we still need backups), it won’t impact Windows 10 1709.

  Am I ready to give this update the all clear?

  Well?  Um… how about we still wait a few more days to just make sure there isn’t any more side effects.

  Windows Patches/Security KB 4090913, Patch Lady Posts

• Problems with yesterday’s Win10 1709 patch, KB 4090913, starting to appear

  Posted on March 6, 2018 at 07:26 CST by woody • Comment in the Forums

  I’m seeing some reports of problems with yesterday’s Patch Monday single-purpose cumulative update for Win10 1709.

  Computerworld Woody on Windows.

  UPDATE: We have a report of the “reboot to black” bug in the Win7 Feb. Monthly Rollup KB 4074598.

  Windows Patches/Security KB 4074598, KB 4090913, KB 4090914, Win10 1709

• Microsoft claims it’s solved the USB problem with Win10 1709 cumulative update KB 4090913

  Posted on March 5, 2018 at 20:15 CST by woody • Comment in the Forums

  Welcome to Patch Monday!

  A few hours after I posted my diatribe in Computerworld, taking Microsoft to task for not fixing Win10 Fall Creators Update, version 1709, wouldn’tcha know it, but Microsoft released yet another cumulative update for 1709 that claims to fix one (not all) of the admitted problems with Win10 FCU.

  KB 4090913 brings Win10 version 1709 up to build 16299.251.

  According to the KB article its sole raison d’être is fixing the USB bug introduced in the last cumulative 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.

  That’s all she wrote. The other bugs are still there:

  • Windows Update History reports that KB4054517 failed to install because of error 0x80070643.
  • After installing this update, some devices may fail to start, and return INACCESSIBLE_BOOT_DEVICE.
  • Because of an AD FS server issue that causes the WID AD FS database to become unusable after a restart, the AD FS service may fail to start. / There is no way to undo the database corruption. To return your AD FS server to a functional state, you must restore it from a backup.

  There’s also an out-of-out-of-band Servicing Stack update, KB 4090914.

  I suggest you hold off until we find out if this patch actually fixes the problem, or if some other ogre jumps out and bites.

  Windows Patches/Security KB 4090913, KB 4090914, March 2018 Black Tuesday, Win10 1709