Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • So, where’s the 32-bit Windows 7 Meltdown patch?

    Posted on March 7th, 2018 at 14:37 woody Comment on the AskWoody Lounge

    Just got this from LB:

    Hey Woody,

    What do you think about doing a story on the missing Windows 7 32-bit meltdown fix? Or maybe mentioning it in next week’s update writeup (unless it finally hits.)

    It seems very odd that it’s taken microsoft so long to issue a fix when the problem, and the solution (kpti), are clear cut (as opposed to the much tougher spectre problems.) 32-bit Win7 should still be getting security fixes until Jan 2020, last I knew.

    Anyway, just a thought. Thanks for all the work you do to keep us informed!

    take care,

    Anybody out there have some insight? Microsoft was slow to get the 32-bit Meltdown patches to Win10. Surely they wouldn’t just give up on Win7, would they?

    Er, would they?

  • Patch Lady – proving that documentation is key

    Posted on March 7th, 2018 at 01:40 Susan Bradley Comment on the AskWoody Lounge

    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.