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

Blog Archives

  • Microsoft: Win10 1903 having problems with Bluetooth speakers

    Posted on August 23rd, 2019 at 22:12 woody Comment on the AskWoody Lounge

    This one’s odd.

    According to the just-posted KB 4518538, “Bluetooth speakers don’t work after update 4505903 is installed on Windows 10, version 1903.”

    After you install update 4505903 on Windows 10, version 1903 on a computer that has an internal speaker installed, you experience one of the following issues:

    • A Bluetooth speaker can’t connect to the computer.
    • A Bluetooth speaker can connect to the computer. However, the speaker output sounds noisy (bad quality).
    • A Bluetooth speaker can connect to the computer. However, the sound is generated by the internal speaker instead of the Bluetooth device.

    Additionally, in Device Manager, you notice an entry under the Sound, video and game controllers node for Microsoft Bluetooth A2dp Source that shows a yellow bang (exclamation mark) icon.

    Here’s what’s odd. KB 4505903 is July’s “optional non-security” second monthly cumulative update. I have no idea why the second July update would have a problem that doesn’t occur in the first August cumulative update. (We haven’t yet seen the second August cumulative update for Win10 1903.)

    UPDATE: @abbodi86 has what sounds like the right diagnosis:

    The issue is probably caused by some combination, or bad sequence, of patches. It does not seem directly related to the update

  • Another re-release of the Win10 1809 installation fix KB 4506578 – appears to be metadata related

    Posted on August 23rd, 2019 at 11:17 woody Comment on the AskWoody Lounge

    Microsoft released a new version of KB 4506578 yesterday, “Compatibility update for installing and recovering Windows 10, version 1809: June 18, 2019

    Looking inside the download, all of the component files are dated May 31.

    Likely another metadata change.

    Thx, @PKCano, @Microfix, @photm, @gborn

  • Microsoft re-issues the Win7 VB/VBA/VBScript fixing patch KB 4517297

    Posted on August 22nd, 2019 at 09:56 woody Comment on the AskWoody Lounge

    Bear with me here….

    Microsoft screwed up all of the Windows patches this month, clobbering VisualBasic, VBA and VBScript. You know that.

    It has slowly been releasing Silver Bullet patches — largely single-purpose patches — to fix the error of its ways.

    But there have been problems with the Win7 patch, in particular, KB 4517297. People report that they can’t get it to install, or that it doesn’t fix the problem. Günter Born has details.

    Yesterday, MS released a new version of KB 4517297. The title of the KB article, Update for Windows 7 SP1 and Windows Server 2008 R2 SP1: August 16, 2019, hasn’t changed. Nor has the content of the KB article, as best I can tell — except for a note at the bottom that the article was updated on August 21.

    What’s different? Does it fix the reported problems with the original KB 4517297? Or is it just a metadata change, to fix installation problems?

    UPDATE: Looks like a metadata change.

    Confirming that all of the files inside the download are dated 8/15. That’s not definitive, but it’s highly indicative of metadata changes.

    Thx @PhantomOfMobile, @etguenni, @SBSDiva

  • Report: The new .NET updates break Veritas Backup Exec

    Posted on August 22nd, 2019 at 06:24 woody Comment on the AskWoody Lounge

    Two days ago, Microsoft released a bunch of patches for .NET Framework 3.5, 4.7.2 and 4.8.

    Now comes word from Günter Born that they’re breaking Veritas Backup Exec.

    The updates (per

    They all claim to fix the bug “Addresses a crash that occurs after enumerating event logs in Bass Class Library (BCL).”

    Born has a translation of a German blog post that says after installing the .NET 4.8 patches, Veritas BackupExec 20.4 won’t start. Apparently, rolling back the patch brings Backup Exec back to life.

    Have you had any problems with the .NET patches?

  • Patch Lady – How to avoid using RDP in Windows

    Posted on August 21st, 2019 at 09:46 woody Comment on the AskWoody Lounge

    An important new article from Susan Bradley in CIO Online:

    BlueKeep and DejaBlue are both potent threats. All of the variants depend on using Remote Desktop Services (commonly abbreviated RDP). Susan Bradley takes you through the steps to avoid or hide RDP, particularly in an enterprise.

    I still recommend that you not install the August Windows patches, which include DejaBlue fixes, specifically because they’re throwing errors like flowers at a wedding. (The May patches for BlueKeep are another story entirely. You should’ve installed those long ago.) But if you have RDP enabled on an internet-facing connection, it’s time to shut it off.

    Those of you connected to corporate servers should follow Susan’s advice and figure out an alternative to public-facing RDP. Those of you with standalone computers can take a couple of simple steps:

    In Vista or Win7, click My Computer and choose Computer. At the top, click System properties. On the left, click Remote Settings. You should be on the Remote tab, and the button under Remote Desktop marked “Don’t allow connections to this computer” should be selected. If it isn’t, click it and click OK.

    In Win10, right-click Start and choose System. On the left, choose Remote Desktop. Make sure the slider to Enable Remote Desktop is set Off.

    I’m not going to guarantee that those simple steps will ward off the Blue Evil Eyes, if and when they appear. But they’ll make breaking your system with the Blues just that much harder.

    If you need to get into your system remotely, there are dozens of alternatives. I use the free Chrome Remote Desktop, but my needs are tiny and I’m not overly concerned about Google snooping me even more. If you want the Tesla version, check out Solarwinds from Dameware. – which is $380 per site.

  • Symantec fixes the SHA-2 patch problem for Win7

    Posted on August 20th, 2019 at 17:14 woody Comment on the AskWoody Lounge

    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:

    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

  • Still no DejaBlue exploits generally available

    Posted on August 20th, 2019 at 07:59 woody Comment on the AskWoody Lounge

    And, in spite of what you’ve read, there are no DejaBlue attacks in the offing. Lots of people have posted “Proof of Concept” code on GitHub. A couple of bluescreen generators, but none of the publicly available exploits actually work.

    @MalwareTech has a new blog post analyzing the two DejaBlue CVEs:

    In August 2019 Microsoft announced it had patched a collection of RDP bugs, two of which were wormable. The wormable bugs, CVE-2019-1181 & CVE-2019-1182 affect every OS from Windows 7 to Windows 10. There is some confusion about which CVE is which, though it’s possible both refer to the same bug. The vulnerable code exist in both the RDP client and server, making it possible to exploit in either direction.

    His sample code crashes the system, but doesn’t infect.

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

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

    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.