Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14 Win Update

Anak · 15 May 2019

ddelo said:

Hi Steve...and please don't thank me for giving you the credit you deserve!!

BTW, the link in my post works from my end. It takes me to your post #71.
I think that's something that needs John's @z3r010 attention.

Hi Dimitri, just trying to be gracious.

Okay, still not sure what happened there, yep, John may take a look probably a minor glitch.

p.s. Tried your link again just now, and now it takes me to the top of page 4?? Last time it was page 3, I dunno maybe its my browser but any other links I try work okay.

Steve

kludge · 15 May 2019

Clintlgm said:

Try installing this update first worked for me (SSU) (KB4499728) You'll find it on page 1 of this thread

Thank you! Installing this updated solved my "This update is not applicable to your computer" problem!

khanmein · 16 May 2019

I ran mdstool-win64

Cliff S · 16 May 2019

@Brink :https://support.microsoft.com/en-us/...date-kb4494441

They update the known issues with this:

Symptom
Some customers report that KB4494441 installed twice on their device.
In certain situations, installing an update requires multiple download and restart steps. If two intermediate steps of the installation complete successfully, the View your Update history page will report that installation completed successfully twice.

Workaround
No action is required on your part. The update installation may take longer and may require more than one restart, but will install successfully after all intermediate installation steps have completed.
We are working on improving this update experience to ensure the Update history correctly reflects the installation of the latest cumulative update (LCU)

Hopachi · 16 May 2019

I didn't paid attention to all those version numbers but:

Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-capture.png

version at .475 didn't changed to .503 but win update says it's successfully installed.
I guess it's coffee time anyway.

Then I'm going to try what kludge's post mentioned, that small update first.
Some pack might be missing.

ddelo · 16 May 2019

There is a new version 1.0.14 of the PowerShell script SpeculationControl

Installation steps:

1. Open PowerShell as Administrator and run the command:

Code:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

2.1 To install the new version, keeping the already installed versions of the script:

Code:

Find-Module -Name 'SpeculationControl' | Save-Module -Path "$env:ProgramFiles\WindowsPowerShell\Modules"

2.2 To install the new version, uninstalling all previously installed versions of the script (clean install of new version):

Code:

Uninstall-Module -Name 'SpeculationControl' -AllVersions -Force -Verbose
Find-Module -Name 'SpeculationControl' | Save-Module -Path "$env:ProgramFiles\WindowsPowerShell\Modules"

3. To run the new version of the script, close and reopen your PowerShell session as Administrator and type the commands:

Code:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
Get-SpeculationControlSettings

dustymars · 16 May 2019

I still have an issue with my Context Menu "New" hanging up; when will MS fix that one?

Bree · 16 May 2019

Cliff S said:

They update the known issues with this:

MS may already have made some changes behind the scenes. I have just updated my last remaining 1809 machine. This one fully installed .503 at the first attempt. I did however notice that the install progress went all the way up to 100%, then jumped back to 14% before slowly rising to 100% again. Only the one restart was required to get to .503, and it was recorded in History as only having been installed once.

Hopachi said:

I didn't paid attention to all those version numbers but ... version at .475 didn't changed to .503 but win update says it's successfully installed...

On my machines it seemed to require two passes to install successfully. All I did on my machines was to check for updates a second time. Then the install completed fully, raising the build to .503.

Cliff S · 16 May 2019

Yeah @Bree they probably got on it quick as soon as the found out a lot of users had the problem.

For me it has always been a habit after Windows updates anything(including from app store) to recheck, as with older Windows versions, like 7 and 8, there was often a specific order the updates needed to install, so a few would be auto selected, install, then you needed to go back and select the rest.

EdKiefer · 16 May 2019

ddelo said:

There is a new version 1.0.14 of the PowerShell script SpeculationControl

Installation steps:

1. Open PowerShell as Administrator and run the command:

Code:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process

2.1 To install the new version, keeping the already installed versions of the script:

Code:

Find-Module -Name 'SpeculationControl' | Save-Module -Path "$env:ProgramFiles\WindowsPowerShell\Modules"

2.2 To install the new version, uninstalling all previously installed versions of the script (clean install of new version):

Code:

Uninstall-Module -Name 'SpeculationControl' -AllVersions -Force -Verbose
Find-Module -Name 'SpeculationControl' | Save-Module -Path "$env:ProgramFiles\WindowsPowerShell\Modules"

3. To run the new version of the script, close and reopen your PowerShell session as Administrator and type the commands:

Code:

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
Get-SpeculationControlSettings

Thank you, this got me updated to new version but I had to use "Import-Module SpeculationControl " after "
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process" in step 3. I used step 2.1.
Anyway it worked, shown MDS stuff now.