[DISCUSSION] Windows 11 Final Build 226x1/2/3/4/5 (PC) 22/3H2 [RETAiL/BETA/RP Channel - ni_release]

Discussion in 'Windows 11' started by Enthousiast, May 11, 2022.

  1. BetaWorld

    BetaWorld MDL Member

    Jan 9, 2015
    111
    272
    10
    I investigated further into the problem and found that the failure was caused by clean up, not cab/psf.

    Error log:
    Code:
    Could not find Microsoft-Windows-Security-Processor-Native-Whitebox, version 10.0.22621.1
    I tried installing 22621.160 cab/psf first and then 22621.169 updates without any problem. However if I clean up the image after the installation of 22621.160 first 22621.169 would fail to install.
     
  2. hcvn

    hcvn MDL Junior Member

    Aug 11, 2017
    57
    30
    0
    yes, dism log say its lack of many Manifests after cleanup/resetbase
    log:
    Code:
    amd64_microsoft-windows-s..sor-native-whitebox_31bf3856ad364e35_10.0.22621.1_none_028b3b1725364e29.manifest
    amd64_microsoft-windows-codeintegrity_31bf3856ad364e35_10.0.22621.1_none_020dbcf1f87e1485.manifest
    amd64_microsoft-windows-d2d_31bf3856ad364e35_10.0.22621.1_none_0932b2784faf2971.manifest
    amd64_microsoft-windows-directx-direct3d9on12_31bf3856ad364e35_10.0.22621.1_none_3f512ac88b9ab92c.manifest
    amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_10.0.22621.1_none_514e1a8ac16a47a1.manifest
    amd64_microsoft-windows-directx-direct3d11on12_31bf3856ad364e35_10.0.22621.1_none_5d6d66233b36aa43.manifest
    amd64_microsoft-windows-directx-direct3d12_31bf3856ad364e35_10.0.22621.1_none_514e03c2c16a6142.manifest
    amd64_microsoft-windows-directx-warp10_31bf3856ad364e35_10.0.22621.1_none_4bf96f984a6a8ec0.manifest
    amd64_microsoft-windows-windowscodec_31bf3856ad364e35_10.0.22621.1_none_f817832e94dc4e3a.manifest
    amd64_microsoft-windows-ucrt_31bf3856ad364e35_10.0.22621.1_none_0d5700fb0d3e19c7.manifest
    ....................................................................................................
    
    I think problem is not resetbase or cleanup, its from this LCU package.
     
  3. BetaWorld

    BetaWorld MDL Member

    Jan 9, 2015
    111
    272
    10
    Actually this reminds me of 19041.899 which had the same problem. Besides that both 19041.899 and 22621.160 are from **_release_svc_prod2, which is an insider only branch. This could mean that changes from prod2 updates will very likely be rolled back or replaced in following updates thus reverse differentials are required.

    I don't think cab/psf will cause any problem however that's my personal guess.
     
  4. AveYo

    AveYo MDL Expert

    Feb 10, 2009
    1,836
    5,730
    60
    Stuff like this is what I'm talking about with (artificial) .1 image vs. incremental one - for some god damn reason setup is set to hard-terminate further install if it does not find some intermediary hard-coded manifest that is 100% dead weight otherwise.
    And it's not a problem with uupdump and the converter script, but 100% an issue on microsoft side, resetbase is an afterthought for them (and can break with official images just as well).
    It happens rarely, but when it does, it's very frustrating, so I'm dodging uupdump refreshed builds by always clean installing the latest ESD when needed, then using WU for it's lifetime.
    Those using uupdump builds should try dodging WU instead, by always refreshing the builds (for a perpetual repair-install that is guaranteed to pass).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,681
    103,561
    450
    Thanks for confirming this, we had this problem with many older IP updates (specially those with the same kbnr but different delta builds).

    But then it was just a simple matter of time till msft released the (next) update to the public and that one would install fine.
    Now with this kinda public but still claimed to be IP 22621 builds it will take some time before they release the official non IP updates.

    The actual question is, how to overcome/solve this without having to perform an inplace/repair upgrade with an uptodate ISO (or something like the rtm reset stuff like @abbodi1406 had to create in the past?).
     
  6. BetaWorld

    BetaWorld MDL Member

    Jan 9, 2015
    111
    272
    10
    #1186 BetaWorld, Jul 2, 2022
    Last edited: Jul 2, 2022
    That depends on the actual content of a following update. Usually the next prod2 update will install just fine, however it's still not clear whether prod1/prod3 updates can be installed afterwards. Inplace upgrade is still a better way, especially Nickel builds upgrade relatively fast.

    I suggest avoiding prod2 updates (they are all IP builds, not even RP) or never cleanup updates after installation. Also give enough space to Windows otherwise the system could cleanup itself for more space.
     
  7. taylorcole

    taylorcole MDL Novice

    Jul 1, 2021
    28
    12
    0
    Has anyone faced an issue where Software Restriction Policy just doesnt work in 22621.105??...I added few path rules in teh SRP list but it JUST DOESNT WORK. Bad :(
     
  8. coleoptere2007

    coleoptere2007 MDL Guru

    Apr 8, 2008
    3,302
    1,936
    120
  9. taylorcole

    taylorcole MDL Novice

    Jul 1, 2021
    28
    12
    0
    Adding an extra point to my own question given above. Any workarounds for the above issue???

    I dont use Antivirus so rely on SRP only for execution prevention. Even Applocker is NOT working in 22621.105. A third party software - SoftwarePolicySetup220 also failed to work.

    SRP and The third party software mentioned above worked fine on 22000.xxx builds and all previous version of Windows from XP to 10 and even Servers 2003 to 2022. Never faced such an issue with SRP before.
     
  10. bdl

    bdl MDL Addicted

    Aug 8, 2012
    565
    43
    30
    guys i not found what limit internet speed,i am 22612.169,i know it is suspect service but dont know what service or services STOP,from 1gbps i have only 400,i update ethernet driver tg 3468 v4 ,ethernet card it is set to 1 gb,in sppedtest from m$ store i have 920 mbps,in windows only 400-450 mbps for download,please help me...
    thank you !
    in this build tab explorer not work,only with vivetool :(
     
  11. cta62

    cta62 MDL Member

    Jul 9, 2015
    152
    67
    10
    Uhhhhhh wut
     
  12. Jessie Pinkman

    Jessie Pinkman MDL Addicted

    Aug 25, 2016
    551
    275
    30
    Something is slowing his speed so probably his provider or using a VPN plus he's not saying where he's downloading from either and he cant even get the number right with it been 22621 :biggrin5::biggrin5:
     
  13. bdl

    bdl MDL Addicted

    Aug 8, 2012
    565
    43
    30
    22621.169,not using vpn,not down from ISP !
    thank you
     
  14. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,828
    2,431
    60
    You do remember that Gigabit speed is theoretical under perfect conditions, right? Where did you measure "400-500 Mbit" speed?
     
  15. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream

    Dec 21, 2012
    6,773
    7,721
    210
    I have also Gigabit speed (1150Mbps down) and the full speeds are only reached under very special conditions. Most servers are not up to par, and there is a lot of throttling going on. Also remember that you are not alone in the Internet, lots of routes are congested and packet dropping is common.
    Not to mention El-Cheapo consumer routers and other devices, packet-analyzing "security" software etc. Plus, you might need to set your TCP/IP parameters right in the OS, after measuring your bandwidth-delay product.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. ohenry

    ohenry MDL Senior Member

    Aug 10, 2009
    435
    270
    10
    I'm running 22161.169, on AT&T 1 gig fiber line. Speed tests, run just now, from Ookla and M-Labs. Somehow I don't think 22161.169 is affecting my internet connection speeds. (smile)


    ookla.jpg ookla.jpg m-labs.jpg
     
  17. d5aqoëp

    d5aqoëp MDL Addicted

    Jan 19, 2017
    828
    614
    30
    My speedtest results are in my sig.
     
  18. Stimpy88

    Stimpy88 MDL Senior Member

    Mar 24, 2011
    378
    213
    10
    Speedtest results are sometimes a speed test of the server it is connected to. Try a different server, get a different result.
     
  19. shhnedo

    shhnedo MDL Expert

    Mar 20, 2011
    1,828
    2,431
    60
    @abbodi1406
    Code:
    ============================================================
    Running W10UI v10.18
    ============================================================
    
    ============================================================
    Removing temporary extracted files...
    ============================================================
    
    
    ============================================================
    Extracting files from update cabinets (.cab)...
    *** This will require some disk space, please be patient ***
    ============================================================
    
    1/4: defender-dism-x64.cab
    2/4: Windows10.0-KB5007297-x64-NDP48.cab [NetFx]
    3/4: Windows11.0-KB5014958-x64.cab [LCU]
    4/4: Windows11.0-KB5015713-x64.cab [SSU]
    
    ============================================================
    Mounting sources\install.wim - index 1/6
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Checking Updates...
    ============================================================
    
    ============================================================
    Installing servicing stack update...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_169~31bf3856ad364e35~amd64~~22621.169.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_169 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    ============================================================
    Installing updates...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4460.20
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Cleaning up OS image...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [=====                      10.0%                          ]
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Adding Defender update...
    ============================================================
    
    
    ============================================================
    Adding .NET Framework 3.5 feature...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    Enabling feature(s)
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Reinstalling cumulative update(s)...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    Processing 1 of 2 - Adding package Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.4460.20
    [==========================100.0%==========================]
    Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Updating winre.wim ...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_169~31bf3856ad364e35~amd64~~22621.169.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_169 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [================           28.8%                          ]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image File : D:\win11\intupd\winre.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Exporting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Adding updated winre.wim ...
    ============================================================
    
            1 file(s) copied.
    
    ============================================================
    Unmounting sources\install.wim - index 1/6
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image File : C:\wMSMG\DVD\sources\install.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ...
    
    ============================================================
    Rebuilding sources\install.wim ...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Mounting sources\boot.wim - index 1/2
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Checking Updates...
    ============================================================
    
    ============================================================
    Installing servicing stack update...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_169~31bf3856ad364e35~amd64~~22621.169.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_169 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    ============================================================
    Installing updates...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Resetting WinPE image base...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [================           28.8%                          ]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Unmounting sources\boot.wim - index 1/2
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image File : C:\wMSMG\DVD\sources\boot.wim
    Image Index : 1
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Mounting sources\boot.wim - index 2/2
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Checking Updates...
    ============================================================
    
    ============================================================
    Installing servicing stack update...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_ServicingStack_169~31bf3856ad364e35~amd64~~22621.169.1.1
    [==========================100.0%==========================]
    The changes due to package Package_for_ServicingStack_169 requires the current servicing session to be reloaded.
    All the packages will be processed again.
    The operation completed successfully.
    
    ============================================================
    Installing updates...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.1
    
    Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~22621.169.1.5
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Resetting WinPE image base...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [================           28.8%                          ]
    The operation completed successfully.
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image Version: 10.0.22621.169
    
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Unmounting sources\boot.wim - index 2/2
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Image File : C:\wMSMG\DVD\sources\boot.wim
    Image Index : 2
    Saving image
    [==========================100.0%==========================]
    Unmounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Rebuilding sources\boot.wim ...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Converting install.wim to install.esd ...
    ============================================================
    
    Deployment Image Servicing and Management tool
    Version: 10.0.19041.844
    
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    Exporting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    ============================================================
    Removing temporary extracted files...
    ============================================================
    
    
    ============================================================
       Finished
    ============================================================
    Base image is 22621.1 from uupdump, AppsLevel=2. For every index, applying the servicing stack results in that message.
    Idk if it's something worth looking at. It says "operation successful" so maybe it's fine.