AskWoody

Patch Lady – downloading the 1809 iso

So given that the tea leaves look like that 1903 is coming soon, I’m making sure that I’m downloading 1809 from the media download site and parking it on a location so that when I’m ready to install 1809, I have it ready to go.

Today the previews of next month updates came out for everything but 1809.

https://www.microsoft.com/en-us/software-download/windows10

So if you decide WHEN you want the feature releases, make sure you’ve deferred to the semi annual channel and have 1809 downloaded and parked for the future.

KB 4487017 Feb Cumulative update for Win10 v1803 causing BSODs

@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

This page was changed today

https://support.microsoft.com/en-us/help/4028685/windows-10-get-the-update

Any idea what’s up?

Thx VulturEMaN

Patch Lady – Domain admins and issues with KB4489878

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.

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

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

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 zdnet.com that update 1.289.1588.0 was issued on March 19th. @alqamar posted his tests were fixed by update 1.289.1587.0.

Woody’s Windows Watch: Seven Semper Fi – How to ride Win7 into the sunset

Humbug. The Windows “experts” who say that you should throw away your Win7 machine because it’s too old are just out of touch. Ain’t broke, don’t fix. Yes, there are security reasons for moving to Win10, but if you’re careful, you may be able to beat the Grim Redmond Reaper.

I’m going with you on the ride to Win7 not-so-planned obsolescence. Here’s the machine I’ve set up — my Seven Semper Fi — to weather the ride. Let’s see what slings and arrows Microsoft may cast.

Details in this week’s AskWoody Plus Newsletter 16.10.0, out this morning to AskWoody Plus Members.

LangaList: Win10’s new winver alternative, jv16 PowerTools, hard drive somnambulance

Fred Langa’s back with a detailed exploration of three readers’ questions:

• Comparing the traditional winver command (which shows you details about your Windows version) with the new Win10 about command (which offers much more)
• Does the venerable jv16 PowerTools still offer features that you can use?
• Why an external hard drive keeps nodding off

All of it in Fred’s inimitable, accessible style.

Details in this week’s AskWoody Plus Newsletter 16.10.0, out this morning to AskWoody Plus Members.