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

Page 10 of 31 FirstFirst ... 8910111220 ... LastLast

  1. VBF
    Posts : 602
    Win 10 Pro
       #90

    bagavan said:
    Now Understood..
    Thank you :)
      My Computers


  2. Posts : 27,166
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #91

    EdKiefer said:
    Ok, I see many of you running new PS version 0.13 with MDS entries added.

    When I try to follow this site to load new module https://support.microsoft.com/en-us/...ngs-powershell

    The command " Install-Module SpeculationControl" gives me just a pop-up window, "what file do you want to open"
    I tried DL script as noted on that site PowerShell Gallery
    | SpeculationControl 1.0.13
    but after I unpack it I again run "Import-Module.\SpeculationControl.psd1 " I get a red error saying path, name is not right but it is.right, so stuck on version 0.12.
    Open up ISE as admin and click File, select open, and find the PS script, then run the script with the green arrow icon.
      My Computers


  3. VBF
    Posts : 602
    Win 10 Pro
       #92

    EdTittel said:
    OK, so now I'm puzzled. I also experienced what others reported here -- thanks to @khanmein and @IronZorg89 for their follow-ups which quoted my earlier post to this thread -- and had to install KB4494441 TWICE to get to .503. Here's what I see in my update history on the production PC as an example:
    Attachment 233807
    What's the deal here? I'm a little surprised and puzzled by this phenomenon. There's no longer any doubt in my mind that two installs of the same CU are required to get completely up-to-level (.503). But I'd like to know why? Anybody got an explanation, or some idea of what's happening here? TIA,
    --Ed--
    I get exactly that.
    Have a look back at post #71.
    I am wondering if perhaps the code was mis-labelled somewhere, so a machine downloads it successfully, the label gets corrected and it appears that the download is still needed and it gets downloaded again???

    UPDATE:
    On another PC the 2 updates occurred on the same day using the following sequence:

    PC Started out on Winver 1809 (OS Build 17763.475)

    AUTOMATIC check for updates CU KB4494441and routine updates downloaded and installed - restart requested
    Restarted - STILL Winver 1809 (OS Build 17763.475)
    MANUAL check for updates, CU KB4494441 downloaded and installed AGAIN - restart requested
    Restarted - Winver 1809 (OS Build 17763.503)
    MANUAL check for updates, "You're up to date"
    11:23 16/05/2019

    This gave:
    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-capture.jpg
    As you can see, it also happened with a previous update last month.

    CP shows this, so possibly if both attempts occur on the same day, CP only reports one except that the April one isn't in CP at all! Go figure

    Cumulative Update KB4494441 Windows 10 v1809 Build 17763.503 - May 14-capture-2.jpg
    Last edited by VBF; 16 May 2019 at 05:49.
      My Computers


  4. Posts : 2,450
    Windows 10 Pro x64
       #93

    EdTittel said:
    OK, so now I'm puzzled. I also experienced what others reported here -- thanks to @khanmein and @IronZorg89 for their follow-ups which quoted my earlier post to this thread -- and had to install KB4494441 TWICE to get to .503. Here's what I see in my update history on the production PC as an example:
    Attachment 233807
    What's the deal here? I'm a little surprised and puzzled by this phenomenon. There's no longer any doubt in my mind that two installs of the same CU are required to get completely up-to-level (.503). But I'd like to know why? Anybody got an explanation, or some idea of what's happening here? TIA,
    --Ed--
    My only guess Ed, is that the 1st time fails, because it doesn't find the new SSU.
    It applies it and then needs a second time around to install the update.
    Not the proper way to do it, but that's the only thing that might make some sense, for the double installation.
      My Computer


  5. Posts : 31,471
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #94

    EdTittel said:
    OK, so now I'm puzzled. I also experienced what others reported here ... had to install KB4494441 TWICE to get to .503...
    I can confirm that, all bar one of my 1809 systems required two passes to install .503 - but NOT two downloads, the second pass downloaded nothing new (I was watching network activity in Task Manager). It seemed to use the files already downloaded. The one exception that installed on the first attempt was an x86 machine, all the others were x64.

    Microsoft have also confirmed this unexpected 'two pass' install....

    Microsoft said:
    Windows 10, version 1809 Update Tuesday update may install twice
    We are presently investigating and will provide an update when available.
    https://docs.microsoft.com/en-us/win...019#375msgdesc
      My Computers


  6. Posts : 2,450
    Windows 10 Pro x64
       #95

    Bree said:
    I can confirm that, all bar one of my 1809 systems required two passes to install .503 - but NOT two downloads, the second pass downloaded nothing new (I was watching network activity in Task Manager). It seemed to use the files already downloaded. The one exception that installed on the first attempt was an x86 machine.

    Microsoft have also confirmed this unexpected 'two pass' install....

    https://docs.microsoft.com/en-us/win...019#375msgdesc

    Not for this Build though, but for 17763.502!
      My Computer


  7. Posts : 31,471
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #96

    ddelo said:
    Not for this Build though, but for 17763.502!
    I assumed that was a typo by MS (woulldn't be the first time)
      My Computers


  8. Posts : 2,450
    Windows 10 Pro x64
       #97

    Bree said:
    I assumed that was a typo by MS (woulldn't be the first time)
    Typos....are not allowed, when acknowledging errors!
      My Computer


  9. Posts : 208
    Win 10
       #98

    Cliff S said:
    Open up ISE as admin and click File, select open, and find the PS script, then run the script with the green arrow icon.
    Thanks for the help.
    I did what you said, pointed to the SpeculationControl.psd1 file (ver 0.13) I hit run and then ran
    Import-Module SpeculationControl
    then
    Get-SpeculationControlSettings
    but I am still missing MDS lines and if I check path "C:\Program Files\WindowsPowerShell\Modules\SpeculationControl" it is still ver 0.12.
      My Computer


  10. Posts : 2,450
    Windows 10 Pro x64
       #99

    EdKiefer said:
    Thanks for the help.
    I did what you said, pointed to the SpeculationControl.psd1 file (ver 0.13) I hit run and then ran
    Import-Module SpeculationControl
    then
    Get-SpeculationControlSettings
    but I am still missing MDS lines and if I check path "C:\Program Files\WindowsPowerShell\Modules\SpeculationControl" it is still ver 0.12.
    Try by running the command
    Uninstall-Module -name SpeculationControl
    And then follow the instructions given by Microsoft to reinstall it.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 04:34.
Find Us




Windows 10 Forums