[DISCUSSION] Windows 10 Final Build 19041>>>19045 (PC) [20H1>>>22H2 vb_release]

I understood what happened ...

Very good.

With your script I can use an X64 version without problems.

Thnks!

 

I did not get the win11 notification on my dad's Toshiba Satellite 2013 laptop running Win10 Home 21H1 build 19043.1202.
maybe because the Toshiba laptop was deemed not worthy by MS to receive win11

 

You need to login to view this posts content.

 

Is there any known or tested way/workaround to use the Win11 MS Store in (under) Win10?

 

I do't think so

Code:

    <TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.22000.20" MaxVersionTested="10.0.22000.20"/>
    <TargetDeviceFamily Name="Windows.Core" MinVersion="10.0.22000.20" MaxVersionTested="10.0.22000.20"/>

 

You need to login to view this posts content.

 

Oh, I missed them... Thank you.

 

Weird enough, there is a third version of KB5005101 released on WSUS.
Size: 615700333 bytes (587 MiB)
SHA1: 980BA7FBBA36F0C161C201D382F89C12176261C8

 

Same build.
When installing on top of the previous 1202.1.15 with dism it only does:
"Adding package Multiple_Packages~~~~0.0.0.0"

 

Combined cab inside combined msu

e.g. from 1809 Windows10.0-KB5005102-x86_uup.xml

Code:

<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
    <package action="install">
        <assemblyIdentity  name="Package_for_ServicingStack" version="17763.2140.1.1" language="neutral" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"/>
        <source location="%configsetroot%\SSU-17763.2140-x86.cab"/>
    </package>
        <package action="install">
            <assemblyIdentity  name="Multiple_Packages" version="0.0.0.0" language="neutral" processorArchitecture="" publicKeyToken=""/>
            <source location="%configsetroot%\Windows10.0-KB5005102-x86.CAB" />
        </package>
    </servicing>
</unattend>

p.s.
dism always try to apply the update, even if already installed

 

The detection mechanism considers the update installed if v2 is installed and does not push for v3.
I assume this latest one is the "official" one as much as a preview can be considered official.