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 14, 2019

  • The sky is not falling: DejaBlue (aka BlueKeep II, III, IV, V) are not being exploited in the wild

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

    I’m hearing a lot of saber rattling, urging folks to install the latest Patch Tuesday patches to guard against the newly-discovered BlueKeep variants. One blog says, “So patch your PCs and spread the word. Millions of users around the world refuse to update their versions of Windows but, in this case, the threat is immediate, viral and very real.”


    Permit me to remind you that BlueKeep itself hasn’t been reliably exploited. The threat is real, but it’s not viral or immediate.

    That said, Kevin Beaumont thinks these new exploits may be able to circumvent Microsoft’s recommended “mitigation”: NLA may not break the infection chain.

    I’ll be keeping a close eye on developments. In the meantime, I still don’t see any pressing reason to install this month’s patches — and I’m seeing more and more reports of bugs.

    We’re still at MS-DEFCON 2.

  • Report that Win10 1903 cumulative update KB 4512508 clobbers Outlook 365 startup

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

    A new report from the group:

    KB 4512508 causes Outlook 365 (Version 1902 Build 11328.20368 Click-to-Run – July version) to get stuck on loading profile. Uninstalling KB4512508 corrected the issue.

    I don’t see this listed as a known bug in either Win10 1903 or in Office.

  • Report that Server 2012 R2 Monthly Rollup KB 4512488 breaks RDP login

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

    Reader @sdsalsero reports:

    Last night we upgraded our public-facing Server 2012R2-based RDS Gateway (GW) and Connection Broker (CB) servers to the brand-new Aug 2019 Rollup. After the patching, no one could login. We use an RDP connection file which specifies the use of the GW and has the CB listed as the target system. You would be prompted to authenticate, i.e., I assume your login request was passing through the GW to the CB, but then there was a completely generic error, “Unable to connect.”

    On the CB’s Windows Event application log,

    There are repeating pairs of 1306/1296 errors:

    1306, “RD Connection Broker Client processes request from a user”
    “Remote Desktop Connection Broker Client failed to redirect the user. Error: NULL”

    1296, “RD Connection Broker Client processes request from a user”
    “Remote Desktop Connection Broker Client failed while getting redirection packet from Connection Broker. Error: Remote Desktop Connection Broker is not ready for RPC communication.”

    Anybody else hitting that problem?

  • CPU throttling to 0.4 GHz on Surface devices, including the Surface Pro 6 and Surface Book 2

    Posted on August 14th, 2019 at 09:29 woody Comment on the AskWoody Lounge

    Thanks to @TechThinkers for pointing me to this article by Mayank Parmar in Windows Latest:

    CPU suddenly slows itself down and drops to 0.4Ghz– below the base level for the chip.

    this issue is not associated with Microsoft’s firmware or software updates

    It could be a bug impacting the thermal management system which slowdowns the clock speeds under heavy thermal loads. The throttling issue was first reported in 2018 on Surface Book and complaints have increased significantly in 2019.

    Mayank points to threads on Reddit, the MS Answers Forum, and the Feedback Hub. The descriptions have an uncanny common thread: They all say that the CPU (measured in the Task Manager) pegs at 0.4 GHz — not 0.3, not 0.5 GHz.

    Have you hit this problem? Is it associated with your machine heating up?

    UPDATE: James Sanders at ZDNet has taken up the topic.