New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14 Win Update

    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14

    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14

    Category: Win Update
    Last Updated: 29 May 2019 at 17:12

    UPDATE 5/29: New KB4498523 Servicing Stack Update for Windows 10 v1903 - May 29


    Servicing stack update for Windows 10, Version 1903: May 14, 2019

    Applies to: Windows 10 version 1903

    Summary

    Microsoft released a new Servicing stack update to Window Insider program Slow, Fast, and Release Preview rings. This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Key changes include:

    • Addresses an issue that may prevent updates from installing when using an unattended.xml file with Deployment Image Servicing and Management (DISM).
    • Addresses an issue that may prevent updates from installing when the File Server Resource Manager role is enabled.
    • Addresses an issue with factory reset, also called Push-button reset or PBR. During a factory reset, after the “Preparing” step some devices may receive an error, "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click 'OK' to restart the computer, and then restart the installation."

    Microsoft strongly recommends you install the latest servicing stack update (SSU) for your operating system before installing the latest cumulative update (LCU). Installing servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft security fixes.

    How to get this update

    Method 1: Windows Update

    This update will be downloaded and installed automatically.

    Note: This update is also available through Windows Server Update Services (WSUS).

    Method 2: Microsoft Update Catalog

    Windows Insiders may also download the standalone package for this update, go to the Microsoft Update Catalog website.

    More information

    Prerequisites

    There are no prerequisites for installing this update.

    Restart information

    You don't have to restart your computer after you apply this update.

    Update replacement information

    This update replaces the previously released update KB4498524.


    Source: https://support.microsoft.com/en-us/...date-kb4500109


    Direct download links for KB4498524 MSU file from Microsoft:

    Download KB4500109 MSU for Windows 10 v1903 32-bit (x86) - 6.5 MB

    Download KB4500109 MSU for Windows 10 v1903 64-bit (x64) - 14.5 MB

    Download KB4500109 MSU for Windows 10 v1903 ARM64 - 17.7 MB
    Brink's Avatar Posted By: Brink
    16 May 2019


  1. NeoBeum
    Posts : 17
    W10P
       New #1

    Linking
    NeoBeum said:
    ADK 18362.1 DISM will fail to install KB4497936 on an Offline 18362.30 Winre.wim
    SSU KB4500109 was meant to address this issue.

    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14

    https://support.microsoft.com/en-us/...date-kb4500109

    It does not.
    Code:
    PS E:\WinROG> DISM /Mount-Image /ImageFile:winre.wim /Index:1  /MountDir:mount\RE                                                                                                                                                               
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Mounting image
[==========================100.0%==========================]
The operation completed successfully.
PS E:\WinROG> DISM /Image:mount\RE /Add-Package  /PackagePath:"\\Nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4500109-x64_b727d70aacc30ac3522c02b285164d908e818ad6.msu"                                                                      
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.30

Processing 1 of 1 - Adding package  \\Nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4500109-x64_b727d70aacc30ac3522c02b285164d908e818ad6.msu
[==========================100.0%==========================]
The operation completed successfully.
PS E:\WinROG> DISM /Image:E:\WinROG\mount\RE /Add-Package  /PackagePath:"E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu"                                                                                      
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.30

Processing 1 of 1 - Adding package E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu
[==========================100.0%==========================]
E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu:  An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
 Error: 0x80070002

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

PS E:\WinROG> DISM /Image:E:\WinROG\mount\RE /Add-Package  /PackagePath:"E:\WinROG\windows10.0-kb4497936-x64_4ac9328bb1376d2cadb09f56ba95ac9b08b88fba.msu"                                                                                      
Deployment Image Servicing and Management tool
Version: 10.0.18362.1


Error: 50

DISM does not support servicing a Windows Vista RTM or earlier operating system.
If the operating system is supported check that SSShim.DLL is present.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
      My Computer
    Quote Quote

  3. nunzio
    Posts : 10
    Windows 10 Pro x64
       New #2

    Please, KB4500109 in my pc does'nt install.
    I got the previous KB4498524 installed.
    Please help me. Thank you.
      My Computer
    Quote Quote

  4. EdTittel
    Posts : 4,224
    Windows 10
       New #3

    @nunzio: Please post a new thread to the general support or the updates and activation forums to get help with your problem. The news forums aren't where you normally ask for (or receive) help. You should probably call it something like "Can't install KB4500109," and repeat your issue in the body of that message. Just FYI, and hope this helps!
    --Ed--
      My Computers
    Quote Quote

  6. nunzio
    Posts : 10
    Windows 10 Pro x64
       New #4

    Thank you so much.
      My Computer
    Quote Quote

  7. NeoBeum
    Posts : 17
    W10P
       New #5

    NeoBeum said:
    Linking
    Someone with Magic needs to update my post with the addition of below: (add, not replace - both packages will fail)

    ADK 18362.1 DISM will fail to install KB4505057 on an Offline 18362.30 Winre.wim

    Code:
    PS E:\WinROG> DISM /Image:O:\mount\RE /Add-Package /PackagePath:"\\nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4505057-x64_fd4b2ba8b25ed78316ce27fc54d55afa6d622b19.msu"                                                                  
Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.30

Processing 1 of 1 - Adding package \\nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4505057-x64_fd4b2ba8b25ed78316ce27fc54d55afa6d622b19.msu
[==========================100.0%==========================]
\\nb-domain-hq\hq-hdd\1903\2019-05\windows10.0-kb4505057-x64_fd4b2ba8b25ed78316ce27fc54d55afa6d622b19.msu: An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
 Error: 0x80070002

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
    - - - Updated - - -

    I think I found the problem.... LOLOLOLOL

    Here's a start:

    This is what the Windows directory looks like in Winre.wim, side by side, is what it SHOULD look like....
    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14-msft-engineer-released-kb-developmentmode.jpg


    Fairly sure that the MSFT Engineers aren't in the correct release mode for WinPE...
    This is the bug that wiped out drivers a few years ago.

    Code:
    <?xml version='1.0' encoding='utf-8'?>
<PendingTransaction PrimitivesCommitted="yes" Version="3.1" WcpVersion="10.0.18362.110 (WinBuild.160101.0800)" Identifier="6bacbd72fe0fd501fe070000880cf02f">
    <Transactions>
        <Transaction TransactionId="TI4.3208_1228953:4/Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.116.1.0">
            <Uninstall Application="Microsoft-Windows-WinPE-OC-SRT-Deployment, Culture=neutral, Version=10.0.18362.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="WinPE-SRT-Package~31bf3856ad364e35~amd64~~10.0.18362.30.WinPE-SRT" RefExtra=""/>
            <MarkDeploymentUnstaged Application="Microsoft-Windows-WinPE-OC-SRT-Deployment, Culture=neutral, Version=10.0.18362.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="WinPE-SRT-Package~31bf3856ad364e35~amd64~~10.0.18362.30.WinPE-SRT" RefExtra=""/>
            <Unpin Application="Microsoft-Windows-WinPE-OC-SRT-Deployment, Culture=neutral, Version=10.0.18362.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="WinPE-SRT-Package~31bf3856ad364e35~amd64~~10.0.18362.30.WinPE-SRT" RefExtra=""/>
            <Uninstall Application="WinPE-MDAC-Package-windows-deployment, Culture=neutral, Version=10.0.18362.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS" RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="WinPE-MDAC-Package-windows~31bf3856ad364e35~amd64~~10.0.18362.1.WinPE-MDAC-Package-windows" RefExtra=""/>
    A Giant list of uninstall... and no where is Install.

    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14-lolderp.jpg

    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14-urfurf.jpg

    New KB4500109 Servicing Stack Update for Windows 10 v1903 - May 14-hahahaha.jpg

    I'm gonna be locking 18362.30 as a Golden Image, and not installing any updates until Microsoft sort their drugs engineers out.




    Here's a dump of WinPE Logs, the fun begins after the <resolve> tags and at <uninstall>
    start at the bottom... then work upwards. easier to find.

    <package id="Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.116 - Pastebin.com

    A little preview... of
    Code:
    <?xml version="1.0" encoding="utf-8" ?>
<Sessions>
<Session version="8.0" id="29324_31243375" client="Cbss" options="0" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="false" operationCovered="1025" correlationVector="cw0OdRxZlUerJ+5C.0" Queued="2019/03/18/20:49:20" Started="2019/03/18/20:49:20" Complete="2019/03/18/20:53:25" status="0x0">
    <Tasks>
        <Phase seq="1">
            <package id="Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.18362.1" name="WinPE" targetState="Installed" options="0"/>
        </Phase>
    </Tasks>
    <Actions>
    - - - Updated - - -

    The problem is multiplying.... I'm fairly certain servicing stack updates shouldn't even be reading decade old updates....


    This is in KB4500109.msu >> WSUSSCAN.cab >> package.cab >> package.xml
    Code:
    <?xml version="1.0" encoding="utf-8"?>
<OfflineSyncPackageMinimumClientVersion="5.4.3790.2191"ProtocolVersion="2.0"PackageId="fc56cee1-dc08-4533-a65b-b70181258ebd"SourceId="8af5b5e4-1eb7-4fad-aac4-cb031bc3147e"CreationDate="2019-04-23T04:42:16Z"PackageVersion="1.0"
xmlns="http://schemas.microsoft.com/msus/2004/02/OfflineSync">
<Updates>
<UpdateCreationDate="2019-04-22T21:42:17Z"DefaultLanguage="en"UpdateId="5b6707c2-984f-4078-ad73-1a92d939a74d"RevisionNumber="501"RevisionId="2859"IsLeaf="true"IsBundle="true">
<Categories>
<CategoryType="Company"Id="56309036-4c77-4dd9-951a-99ee9c246a94"/>
<CategoryType="Product"Id="6964aab4-c5b5-43bd-a17d-ffb4346a8e1d"/>
<CategoryType="ProductFamily"Id="6964aab4-c5b5-43bd-a17d-ffb4346a8e1d"/>
<CategoryType="UpdateClassification"Id="0fa1201d-4330-4fa8-8ae9-b877473b6441"/>
</Categories>
<Prerequisites>
<UpdateIdId="0fa1201d-4330-4fa8-8ae9-b877473b6441"/>
<UpdateIdId="6964aab4-c5b5-43bd-a17d-ffb4346a8e1d"/>
</Prerequisites>
</Update>

...




<UpdateCreationDate="2004-02-28T18:17:34Z"DefaultLanguage="en"UpdateId="cd5ffd1e-e932-4e3a-bf74-18bf0b1bbd83"RevisionNumber="1"RevisionId="9"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>

<UpdateCreationDate="2004-02-28T18:17:34Z"DefaultLanguage="en"UpdateId="28bc880e-0592-4cbf-8f95-c79b17911d5f"RevisionNumber="1"RevisionId="8"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>

<UpdateCreationDate="2004-02-28T18:17:36Z"DefaultLanguage="en"UpdateId="b4832bd8-e735-4761-8daf-37f882276dab"RevisionNumber="1"RevisionId="7"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>
<UpdateCreationDate="2004-02-28T18:17:35Z"DefaultLanguage="en"UpdateId="68c5b0a3-d1a6-4553-ae49-01d3a7827828"RevisionNumber="1"RevisionId="6"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>
<UpdateCreationDate="2004-02-28T18:17:33Z"DefaultLanguage="en"UpdateId="0fa1201d-4330-4fa8-8ae9-b877473b6441"RevisionNumber="1"RevisionId="5"DeploymentAction="Evaluate"IsSoftware="false"/>
<UpdateCreationDate="2004-02-28T18:17:22Z"DefaultLanguage="en"UpdateId="56309036-4c77-4dd9-951a-99ee9c246a94"RevisionNumber="1"RevisionId="4"DeploymentAction="Evaluate"IsSoftware="false"/>
<UpdateCreationDate="2004-02-28T18:17:35Z"DefaultLanguage="en"UpdateId="b54e7d24-7add-428f-8b75-90a396fa584f"RevisionNumber="1"RevisionId="3"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>
<UpdateCreationDate="2004-02-28T18:17:35Z"DefaultLanguage="en"UpdateId="ebfc1fc5-71a4-4f7b-9aca-3b9a503104a0"RevisionNumber="1"RevisionId="2"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>
<UpdateCreationDate="2004-02-28T18:17:34Z"DefaultLanguage="en"UpdateId="e6cf1350-c01b-414d-a61f-263d14d133b4"RevisionNumber="1"RevisionId="1"DeploymentAction="Evaluate"IsLeaf="true"IsSoftware="false"/>
</Updates>
<FileLocations>
<FileLocationId="Q7CStSEKAt40vLamR3m3sxQYi08="Url="http://www.windowsupdate.com/Windows10.0-KB4500109-x64.cab"/>
</FileLocations>
</OfflineSyncPackage>
      My Computer
    Quote Quote

  8. NeoBeum
    Posts : 17
    W10P
       New #6

    KB4498523 Servicing Stack Update resolves the issue above.

    New KB4498523 Servicing Stack Update for Windows 10 v1903 - May 29
      My Computer
    Quote Quote

 

  Related Discussions
Source: https://support.microsoft.com/en-us/help/4525419/compatibility-update-for-installing-windows-10-version-1903 Direct download links for KB4525419 MSU file from Microsoft: fas fa-download Download KB4525419 MSU for Windows 10 v1903...
Source: https://support.microsoft.com/en-us/help/4521863/compatibility-update-for-installing-windows-10-version-1903 Direct download links for KB4521863 MSU file from Microsoft: fas fa-download Download KB4521863 MSU for Windows 10 v1903...
See also: Cumulative Update KB4497935 Windows 10 v1903 build 18362.145 - May 24 Direct download links for KB4498523 MSU file from Microsoft Update Catalog: :arrow: Download KB4498523 MSU for Windows 10 v1903 32-bit (x86) - 6.5 MB :arrow:...
Please, KB4500109 in my pc does'nt install. I got the previous KB4498524 installed. Please help me. Thank you.
UPDATE 6/27: New KB4506933 Servicing Stack Update for Windows 10 v1903 - June 27 Source: https://support.microsoft.com/en-us/help/4498523/windows-10-update-kb4498523 See also: Cumulative Update KB4497935 Windows 10 v1903 build...
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 09:00.
Find Us




Windows 10 Forums