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: March 19, 2019

  • KB 4487017 Feb Cumulative update for Win10 v1803 causing BSODs

    Posted on March 19th, 2019 at 14:57 PKCano Comment on the AskWoody Lounge

    @weedacres reports that the Feb 2019 Cumulative Update KB KB4487017 for Win10 v1803  is causing BSODs.

    One of my customers called yesterday reporting BSOD’s on their two HP AIO’s. This KB is the 2019-02 Cumulative update for 1803. This apparently started on or about 3/8 when the update was installed.

    I found that they’re getting 001a BSOD’s and after some research saw that many others are having the same problem. I saw several failures while working on both PC’s and finally uninstalled the update last evening. I hid it with wushowhide and so far all seems well.

    My question is how long with wushowhide keep it hidden? Am I going to have to hand tend this thing until the March updates install?

    Is anyone else seeing this problem?

    This is a correction to an earlier report. It was not KB 4023057 causing the problems.

  • More signs that MS is closer to releasing 1809

    Posted on March 19th, 2019 at 12:55 woody Comment on the AskWoody Lounge

    This page was changed today

    Any idea what’s up?

    Thx VulturEMaN

  • Patch Lady – Domain admins and issues with KB4489878

    Posted on March 19th, 2019 at 11:32 Susan Bradley Comment on the AskWoody Lounge

    Sandeep pointed out that after he installed KB4489878 on a Server 2008 R2 he can no longer use the netdom query commands.  I can attest that commands on a Server 2012 R2 machine work fine, but on a Server 2008 R2 it comes back with an error.

    That’s what it looks like on a Server 2008 R2 after the March updates when I went to check.

    This is what it looks like on a Server 2012 R2 after the March updates on a patched server.

    Anyone else seeing this?

    netdom /query is a command used by Admins to determine what server is the domain controller, what holds what is called the FSMO roles.

    In on premises deployments it’s a command not used that often, but it’s like the c prompt or command line.  It normally just works and you take it for granted.

    It’s not a deal breaker bug, but needs to be addressed nonetheless.  I’ll keep you posted on the status.

    Now documented in the KB as a known issue.  Microsoft is working on the fix.

  • Microsoft acknowledges yet another bug in this month’s Win10 1809 cumulative update, this one with Windows Deployment Services server and PXE

    Posted on March 19th, 2019 at 09:12 woody Comment on the AskWoody Lounge

    An anonymous poster raised the red flag a few hours ago.

    KB article 4898499 now says:

    After installing this update, there may be issues using the Preboot Execution Environment (PXE) to start a device from a Windows Deployment Services (WDS) server configured to use Variable Window Extension. This may cause the connection to the WDS server to terminate prematurely while downloading the image. This issue does not affect clients or devices that are not using Variable Window Extension.

    There are three manual solutions offered.

    Microsoft is working on a resolution and will provide an update in an upcoming release.

    You really gotta wonder who’s testing this stuff – and, in this case, why it took almost a week to acknowledge the problem, which appears to happen on every Windows Deployment Service server with VWE.

  • Windows Defender Security definition problems

    Posted on March 19th, 2019 at 00:52 Kirsty Comment on the AskWoody Lounge

    We’re hearing reports of problems with Definitions Update 1.289.1521.0, preventing scanning in Windows 7 and 8.0 virtual machines. Other OS versions are still being tested by @alqamar.

    Has your machine been affected by this definition update?

    UPDATE: Win 8.1 also affected, but newer OS are ok.
    @alqamar has posted his results
    (This is a real-world problem, not just limited to virtual machines, where early reports were first tested)

    RESOLVED: Microsoft has now issued an update that fixes the issue. In her article on the problem (which was noted as first being seen here), Mary Jo Foley wrote on that update 1.289.1588.0 was issued on March 19th. @alqamar posted his tests were fixed by update 1.289.1587.0.