Newsletter Archives

• Caution updating Win7 if you have an ASUS motherboard and get a “Secure Boot Violation” warning

  Posted on September 7, 2019 at 16:09 CDT by woody • Comment in the Forums

  Poster @Charlie has questions about ASUS motherboards and the August Win7 Monthly Rollup:

  I was all set to go ahead with the August Updates when I read about this apparent problem that KB3133977 has with ASUS motherboards, and that stopped me dead in my tracks!  I have an ASUS P8H61-MLE CSM, H61 B3 chipset motherboard of around 2012 vintage and it has an EFI BIOS, but not UEFI.  I do not already have KB3133977 and according to what I see will need to install it (maybe).

  Just to refresh your memory, KB 3133977 caused all sorts of havoc when it was released in May of 2016. I wrote an article about it in Computerworld at the time. I’m not at all sure if the ghost from more than two years ago is still haunting Win7 Monthly Rollups.

  @PKCano has an answer:

  For those with ASUS motherboards considering KB3133977:

  It would seem that ASUS implemented “Safe Boot” on some Win7 machines, when Win7 doesn’t support Safe Boot, by altering the BIOS.

  There are instructions on the ASUS website (thank you, @samak ) here to deal with the situation:
  https://www.asus.com/support/FAQ/1016356/

  If you have an ASUS motherboard, and Safe Boot is implemented, it looks there are three options:
  Either
  Make the modification in the BIOS so you can install KB3133977
  OR
  Not install KB3133977 and just install the August patch.
  OR
  Do not install either patch and wait for further instructions.

  Anybody out there have more recent info?

  UPDATE: @Sinclair has a related question:

  What I am trying to get sorted is can you install the August and future patches on a non UEFI motherboard without installing the Bitlocker patch. Does the August patch not alter your boot files if the Bitlocker patch is not installed on a non UEFI system? Does it even matter if it is a non UEFI system or not when it comes to the boot files? Because it would really suck if so short before Windows 7 goes out of patching. I end up with a system that can not use any old repair tool to fix it if it ever has harddisk problems.

  That is why it is so complex. I have not seen anyone say yeah your fine the new boot files can be seen by old tools. Or yeah no worries nothing is altered on a non UEFI motherboard.

  Windows Patches/Security August 2019 Black Tuesday, KB 3133977

• MS-DEFCON 3: Time to get the August 2019 patches installed

  Posted on September 6, 2019 at 07:34 CDT by woody • Comment in the Forums

  Lingering bugs await the unwary. Make sure you understand them before you take the August patching leap.

  Details in Computerworld Woody on Windows.

  For those of you new to the MS-DEFCON system… every month I send out warnings to block updates, and then an all-clear (possibly with assorted caveats) when things appear safe. We just hit the “sorta safe” mark, and we’ll descend back to the “block updates” part on Monday. Details on how to handle both transitions appear in Computerworld.

  Windows Patches/Security August 2019 Black Tuesday, MS-DEFCON 3

• The second August patch for Win10 1903 shoots one core up to 100% utilization

  Posted on August 31, 2019 at 00:12 CDT by woody • Comment in the Forums

  Is your machine red-lining after installing today’s KB 4512941, the second August cumulative update for Win10 version 1903?

  Günter Born has a workaround.

  The problem is caused by a corrupt cache in

  c:\Windows\SystemApps\Microsoft.Windows.Cortana_cw5n1h2txyewy\cache\
  

  The solution is to replace that folder with an old, correctly functioning version. Born has links.

  There’s a reason why I haven’t flipped over to MS-DEFCON 3 or 4 just yet. This patch, in particular, hasn’t been sufficiently tested.

  Windows Patches/Security August 2019 Black Tuesday

• Patch Alert: Where we stand with the August 2019 patches

  Posted on August 30, 2019 at 11:45 CDT by woody • Comment in the Forums

  Overview in Computerworld Woody on Windows.

  Wouldn’t ya know it… Microsoft just released the second August patch for Win10 version 1903. Look at all of those fixes.

  Windows Patches/Security August 2019 Black Tuesday

• More than two weeks later, still no VB/VBA/VBScript fix for Win10 version 1903

  Posted on August 28, 2019 at 12:51 CDT by woody • Comment in the Forums

  Fixing bugs introduced by Windows security patches be like:

  https://twitter.com/i/status/1165757143448018944

  Oh, if Microsoft only worked that well. RIP SRV.

  Windows Patches/Security August 2019 Black Tuesday

• Microsoft removes the update block for August Win7 patches on Symantec/Norton systems

  Posted on August 28, 2019 at 07:18 CDT by woody • Comment in the Forums

  Symantec advises that it and Microsoft have come to an agreement about Symantec and Norton antivirus problems with the August Win7 and Server 2008 R2 patches. As a result, MS relaxed its weeks-long block on installing the August Monthly Rollup and Security-only patches on systems running Symantec and Norton antivirus products.

  Details in Computerworld Woody on Windows.

  Thx, @RDRGuy

  Windows Patches/Security August 2019 Black Tuesday, KB 4512486, KB 4512506, KB 4512514, Norton, Symantec

• Symantec fixes the SHA-2 patch problem for Win7

  Posted on August 20, 2019 at 17:14 CDT by woody • Comment in the Forums

  Remember how Microsoft put in a block, preventing the Win7 August Patch Tuesday patches from installing on systems with Symantec Endpoint Protection? This is what the KB articles for this month’s Win7 patches say:

  Microsoft and Symantec have identified an issue that occurs when a device is running any Symantec or Norton antivirus program and installs updates for Windows that are signed with SHA-2 certificates only. The Windows updates are blocked or deleted by the antivirus program during installation, which may then cause Windows to stop working or fail to start.

  I just got a message from CA that says:

  Symantec released an updated version of Norton Internet Security that
  fixes the SHA-2 patch problem for Windows 7 this morning (Tues). The new
  version will show up through Live Update (140+ mb).

  Once the patched version is applied (v22.18.0.222), security roll-ups
  for August (Group A – Aug 13 KB4512506) will appear in Windows Update
  without user intervention. A reboot may be required for this to happen.

  MS has not updated KB4512506 or KB4512486 to reflect this:
  https://support.microsoft.com/en-us/help/4512506

  For Symantec Endpoint Protection users, the English 14.2 version has
  been updated. Localized language versions will be available on the 21st.

  Symantec Endpoint Protection
  https://support.symantec.com/us/en/article.tech255857.html

  Windows Patches/Security August 2019 Black Tuesday

• Fix for the VB bug introduced this month released for Win10 1803

  Posted on August 19, 2019 at 21:16 CDT by woody • Comment in the Forums

  Thanks to @WC and @EP for the heads up.

  A few hours ago we got KB 4512509 – the second cumulative update for Win10 version 1803 this month.

  It claims to fix the VB/VBA/VBScript bug introduced by the first cumulative update this month.

  We’re still waiting for Win10 1903.

  Windows Patches/Security August 2019 Black Tuesday
• « Older Entries