News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon

Daily Archives: August 16, 2019

  • MS fixes the bug that causes a looooong delay in starting Internet Explorer

    Posted on August 16th, 2019 at 22:11 woody Comment on the AskWoody Lounge

    From four hours ago:

    On August 16, 2019 at 7:16 AM a server required for downloading the Internet Explorer 11 (IE11) startup page, went down. As a result of the server outage, IE 11 became unresponsive for some customers who had not yet installed the August 2019 security updates. Customers who had the August 2019 security update installed were not affected. In order to ensure your devices remain in a serviced and secure state, we recommend you install the latest monthly update.
    This issue was resolved on the server side at 1:00 pm PST.
  • Microsoft releases patches to fix the VB/VBA/VBScript bugs

    Posted on August 16th, 2019 at 21:59 woody Comment on the AskWoody Lounge

    Sometime in the past few hours, Microsoft released 18 new patches through the Update Catalog.

    They purport to fix the VB, VBA and VBScript bug in Tuesday’s patches.

    At this moment – 10 pm US Central time on Friday night – patches are only available for Win10 1709 (!), Win7, Win8.1, Server 2008, 2008 R2, 2012 and 2012 R2. The 1709 patch is documented. I don’t see any KB articles for the others – but that’ll likely change as the night wears on.

    We’re still at MS-DEFCON 2. Don’t install them. Let’s see what wails of pain emerge in the next 12 hours or so.

    Like I said on Monday:

    Traditionally, August finds Microsoft in a mid-summer lull, with lots of folks on vacation and more than the usual chances of surprising screw-ups from second-string staff. It’s an excellent month to sit on the sidelines and see what problems appear with the latest round of Windows and Office patches.

  • Patch Lady – VBA errors

    Posted on August 16th, 2019 at 19:11 Susan Bradley Comment on the AskWoody Lounge

    https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903#632msgdesc

    pps using Visual Basic 6 (VB6), VBA, and VBScript may stop responding with error

    After installing KB4512508, applications that were made using Visual Basic 6 (VB6), macros using Visual Basic for Applications (VBA), and scripts or apps using Visual Basic Scripting Edition (VBScript) may stop responding and you may receive an “invalid procedure call error.”
    Affected platforms:
    • Client: Windows 10, version 1903; Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607; Windows 10 Enterprise LTSC 2015; Windows 8.1; Windows 7 SP1
    • Server: Windows Server, version 1903; Windows Server, version 1809; Windows Server 2019; Windows Server, version 1803; Windows Server, version 1709 ; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012; Windows Server 2008 R2 SP1; Windows Server 2008 SP2
    Next steps: Microsoft is working on a resolution and estimates a solution will be available late August. The ‘optional’ update will be available on Microsoft Update Catalog, Windows Update, Microsoft Update and Windows Server Update Services (WSUS). As with any ‘optional’ update, you will need to Check for updates to receive the update once it is released.
    Note Windows Update for Business customers should apply the update via Microsoft Update Catalog or Windows Server Update Services (WSUS).

     

  • Patch Lady – 1903 Error 0x80073701

    Posted on August 16th, 2019 at 19:10 Susan Bradley Comment on the AskWoody Lounge

    Updates may fail to install and you may receive Error 0x80073701

    Installation of updates may fail and you may receive the error message, “Updates Failed, There were problems installing some updates, but we’ll try again later” or “Error 0x80073701” on the Windows Update dialog or within Update history.
    Affected platforms:
    • Client: Windows 10, version 1903
    • Server: Windows Server, version 1903
    Next steps: We are working on a resolution and will provide an update in an upcoming release.
  • Stop the presses: Notepad will be available in the Store

    Posted on August 16th, 2019 at 17:22 woody Comment on the AskWoody Lounge

    Now that’s an improvement at least one person will appreciate. Here’s the official word on the latest Windows  20H1 beta build (due in the first half of 2020, possibly called 2003, but I hope not):

    Making Notepad store-updatable

    Notepad has been a well-loved text editor in Windows for over 30 years. Over the last few releases, we’ve been making a number of small improvements to Notepad based on your feedback (including expanded line ending supportwrap around search, and indicating when there’s unsaved content.) Starting with this build, we’re making a change so that future Notepad updates will be automatically available via the store. This will allow us the flexibility to respond to issues and feedback outside the bounds of Windows releases. As always, if you have any feedback for Notepad, we welcome it in the Feedback Hub under Apps > Notepad.

    Let’s hear it for rapid deployment.

    Gad, you couldn’t make this stuff up.

  • Kaspersky antivirus places a unique identifier on every website you visit

    Posted on August 16th, 2019 at 15:51 woody Comment on the AskWoody Lounge

    I still swear by Microsoft Defender.

    Dan Goodin at Ars Technica has the story:

    For almost four years, AV products from Kaspersky Lab injected a unique identifier into the HTML of every website a user visited, making it possible for sites to identify people even when using incognito mode or when they switched between Chrome, Firefox, or Edge.

    The JavaScript… was designed to, among other things, present a green icon that corresponded to safe links returned in search results.

    Looks like Kaspersky ended its wayward ways in a June update. Four years later.

  • Do you want to protect yourself against BlueKeep, or break Visual Basic?

    Posted on August 16th, 2019 at 09:51 woody Comment on the AskWoody Lounge

    Gawd this is tiresome.

    If you read somewhere that you have to install the August patches, even though you read somewhere that you can’t install the August patches (e.g., if you use Juris), chill. The authors of those advisories are parroting things that they’ve read that they don’t understand.

    Installing patches right now is not a good idea. In very rare circumstances, you need to install a patch soon after it arrives. This isn’t one of those circumstances.

    Right now, we know for sure that these August patches break VB, VBA and VBScript in some situations. Günter Born has a good explainer, which points the finger at array handling. An anonymous follow-on post says it’s related to working with empty arrays.

    You’ll get hit if you’re using Raiser’s Edge, Financial Edge, Education Edge, Epic, Ivanti Workspace Control, or Juris. All have been mentioned by name in our forums.

    DejaBlue, on the other hand — BlueKeep II, III, IV and V — remain theoretical. They, like BlueKeep, will pose a threat at some point. But that point isn’t now.

    It looks like Metasploit is poised to add a BlueKeep module to its package at some point in the next week or two. You’re protected if you followed my instructions and have installed any Windows patch from May onward.

    Meanwhile, there are no credible reports that I can see of a BlueKeep infection. And DejaBlue? I haven’t heard of anything beyond bluescreens.

    Meanwhile, every local news show is telling people to patch now. Bah.