Tell me, I'm making a Lite custom client package Microsoft-Windows-Client-Desktop-Required-Package0310~31bf3856ad364e35~amd64~~10.0.26100.1.mum With the native original cat, it installs normally Microsoft-Windows-Client-Desktop-Required-Package0310~31bf3856ad364e35~amd64~~10.0.26100.1.cat I just delete the original cat, all the package files remain original. Then I make my own generated *.cat with this *.cdf, I publish only the header with the parameters Spoiler: *.cdf Code: [CatalogHeader] Name=update.cat PublicVersion=0x00000001 EncodingType=0x00010001 CATATTR1=0x00010001:OSAttr:2:5.1,2:5.2,2:6.0,2:6.1,2:6.2,2:6.3,2:10.0 [CatalogFiles] <HASH>File1=Files\amd64_microsoft-appmodel-..amodel-capabilities_31bf3856ad364e35_10.0.26100.1_none_b18904471adf7ede.manifest <HASH>File2=Files\amd64_microsoft-appmodel-..sitory-capabilities_31bf3856ad364e35_10.0.26100.1_none_395eec89a2182e8e.manifest <HASH>File3=Files\amd64_microsoft-appmodel-exec-events_31bf3856ad364e35_10.0.26100.1_none_1eda941c51b24d41.manifest <HASH>File4=Files\amd64_microsoft-client-li..ing-platform-client_31bf3856ad364e35_10.0.26100.1_none_065940c41c5cb083.manifest <HASH>File5=Files\amd64_microsoft-client-li..orm-instrumentation_31bf3856ad364e35_10.0.26100.1_none_fa39855234b808a2.manifest <HASH>File6=Files\amd64_microsoft-client-li..se-platform-service_31bf3856ad364e35_10.0.26100.1_none_d1db8edbaca18e3c.manifest <HASH>File7=Files\amd64_microsoft-client-li..sing-platform-winrt_31bf3856ad364e35_10.0.26100.1_none_7eae5031448165ea.manifest <HASH>File8=Files\amd64_microsoft-etw-ese_31bf3856ad364e35_10.0.26100.1_none_cc4e7afeeee8d3b1.manifest I sign it Code: signtool sign /a /fd SHA256 /v /f s.pfx /p 111111 update.cat , when installing error d0000429 - Can't understand the catalog algorithm in catalog Spoiler: error d0000429 - Can't understand the catalog algorithm in catalog Code: 2025-03-09 14:06:56, Info CBS Plan: Start to process package watchlist. 2025-03-09 14:06:56, Info CBS Computed hard reserve increase of 0 bytes for Client: DISM Package Manager Provider, Session: 6992_160568406 2025-03-09 14:06:56, Info CBS Perf: Resolve chain started. 2025-03-09 14:06:56, Info CBS FLOW: Entering stage: Resolving 2025-03-09 14:06:56, Info CBS Resolve: Using IServicingStager. 2025-03-09 14:06:56, Info SXS PERF: Beginning servicing tracing for session 6992_160568406 2025-03-09 14:06:56, Info SXS Introducing a SIL redirection for root \??\H:\Windows\CbsTemp\6992_160568406 2025-03-09 14:06:56, Info CBS Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package0310~31bf3856ad364e35~amd64~~10.0.26100.1, Update: 4DC6C15E9C14D729573E40EA0AA4F0D641DD46A05A20B84CAAEFE00C0C0C784A 2025-03-09 14:06:56, Info CBS Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package0310~31bf3856ad364e35~amd64~~10.0.26100.1, Update: 4DC6C15E9C14D729573E40EA0AA4F0D641DD46A05A20B84CAAEFE00C0C0C784A, PinDeployment: amd64_microsoft-windows-c..red-deployment03100_31bf3856ad364e35_10.0.26100.1_none_20723d39bd11e673 2025-03-09 14:06:56, Info SXS Introducing a SIL redirection for root \??\B:\Certificate\Files 2025-03-09 14:06:56, Info CBS Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package031020~31bf3856ad364e35~amd64~~10.0.26100.1, Update: 1031A898B977E97DB311107850698E4160F55C329E7FC73213EFF4CF95EED364 2025-03-09 14:06:56, Info CBS Exec: Resolving Package: Microsoft-Windows-Client-Desktop-Required-Package031020~31bf3856ad364e35~amd64~~10.0.26100.1, Update: 1031A898B977E97DB311107850698E4160F55C329E7FC73213EFF4CF95EED364, PinDeployment: amd64_microsoft-windows-c..d-deployment0310200_31bf3856ad364e35_10.0.26100.1_none_e9e77144e2da97ef 2025-03-09 14:06:56, Info SXS Waiting for components preload to finish 2025-03-09 14:06:56, Info SXS Components preload finished 2025-03-09 14:06:56, Info SXS Beginning staging 2025-03-09 14:06:56, Info SXS PERF: Amount of prep work before staging: 460ms 2025-03-09 14:06:56, Error SXS Can't understand the catalog algorithm in catalog \??\H:\Windows\CbsTemp\6992_160568406\Microsoft-Windows-Client-Desktop-Required-Package0310~31bf3856ad364e35~amd64~~10.0.26100.1.cat 2025-03-09 14:06:56, Error SXS WIL Origination: onecore\base\servicing\turbostack\lib\staging.cpp(3863)\TurboStack.dll!00007FFE94739AEF: (caller: 00007FFE946EC9C6) Exception(1) tid(e80) D0000429 As I understand, for this generated *.cat some other parameter needs to be added or changed. Which one fits the definition of "Can't understand the catalog algorithm in catalog"? Moreover, with this same *.cdf other selected packages are generated and installed normally from the original Microsoft-Windows-Client-Desktop-Required-Package.ESD. Thank you. P.S. As I understand it, there are many *.cdf options, and working ones for specific cases, I tried this option, which I also used earlier, but then switched to the one I wrote above, but apparently it does not always work This one worked great Spoiler: This one worked great Code: [CatalogHeader] Name=update.cat PublicVersion=0x00000001 EncodingType=0x00010001 CatalogVersion=2 HashAlgorithms=SHA256 ResultDir=.\ CATATTR1=0x10010001:OSAttr:V2:10.0,2:6.3,2:6.2,2:6.1,2:6.0,2:5.2,2:5.1 [CatalogFiles] <HASH>File1=Files\amd64_microsoft-appmodel-..amodel-capabilities_31bf3856ad364e35_10.0.26100.1_none_b18904471adf7ede.manifest <HASH>File2=Files\amd64_microsoft-appmodel-..sitory-capabilities_31bf3856ad364e35_10.0.26100.1_none_395eec89a2182e8e.manifest <HASH>File3=Files\amd64_microsoft-appmodel-exec-events_31bf3856ad364e35_10.0.26100.1_none_1eda941c51b24d41.manifest <HASH>File4=Files\amd64_microsoft-client-li..ing-platform-client_31bf3856ad364e35_10.0.26100.1_none_065940c41c5cb083.manifest <HASH>File5=Files\amd64_microsoft-client-li..orm-instrumentation_31bf3856ad364e35_10.0.26100.1_none_fa39855234b808a2.manifest <HASH>File6=Files\amd64_microsoft-client-li..se-platform-service_31bf3856ad364e35_10.0.26100.1_none_d1db8edbaca18e3c.manifest <HASH>File7=Files\amd64_microsoft-client-li..sing-platform-winrt_31bf3856ad364e35_10.0.26100.1_none_7eae5031448165ea.manifest <HASH>File8=Files\amd64_microsoft-etw-ese_31bf3856ad364e35_10.0.26100.1_none_cc4e7afeeee8d3b1.manifest
This is the right usage. Your .cdf file looks wrong. Did not it give error when making .cat https://forums.mydigitallife.net/th...struction-project.80939/page-758#post-1830389
Trying to add latest CU .3328 to 20349 AzureStackHCI. CU takes but does not show. Any ideas? Code: Microsoft Windows [Version 10.0.20348.3207] (c) Microsoft Corporation. All rights reserved. C:\Users\Administrator>Dism /Image:C:\mount /Add-Package /PackagePath:C:\SSU-20348.3320-x64.esd Deployment Image Servicing and Management tool Version: 10.0.20348.2849 Image Version: 10.0.20349.3207 Processing 1 of 1 - Adding package Package_for_ServicingStack_3320~31bf3856ad364e35~amd64~~20348.3320.1.0 [==========================100.0%==========================] The operation completed successfully. C:\Users\Administrator>Dism /Image:C:\mount /Add-Package /PackagePath:C:\Windows10.0-KB5053603-x64.esd Deployment Image Servicing and Management tool Version: 10.0.20348.2849 Image Version: 10.0.20349.3207 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.3328.1.7 [==========================100.0%==========================] The operation completed successfully. C:\Users\Administrator>Dism /Image:C:\mount /Get-CurrentEdition Deployment Image Servicing and Management tool Version: 10.0.20348.2849 Image Version: 10.0.20349.3207 Current edition is: Current Edition : ServerAzureStackHCICor The operation completed successfully.
I've added Microsoft-Windows-Client-Desktop-Required-Package~31bf3856ad364e35~amd64~en-US~10.0.20348.3328.mum (modded & unmodded) when making custom updates. Also tried this tweak by Ace2 but I changed to correspond with my 20349.3328 build. If UserExperience-Desktop-Package is not added to Microsoft-Windows-EditionSpecific-ServerAzureStackHCICor-Package, custom update will not take, even if update was successful. <update name="4b09b442caf9e09b264375c2a75aca38"> <package contained="false" integrate="hidden"> <assemblyIdentity name="UserExperience-Desktop-Package" version="10.0.26100.1150" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </package> </update>
Q: Where are 14393.0 Client amd64 Windows Defender packages? A: Microsoft-Windows-Client-Optional-Features-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> Windows-Defender-Client-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Microsoft-Windows-Client-Features-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> Windows-Defender-Client-WOW64-Package~31bf3856ad364e35~amd64~~10.0.14393.0 Q: Where is Windows-Defender-Group-Policy-Package? A: Microsoft-Windows-GroupPolicy-ClientTools-Group-Package~31bf3856ad364e35~amd64~~10.0.14393.0 ---> Windows-Defender-Group-Policy-Package~31bf3856ad364e35~amd64~~10.0.14393.0
Shoot was under impression your post was response to my CU update..guess not. If so I used the Microsoft-Windows-Server-DesktopUX-Package~31bf3856ad364e35~amd64~en-US~10.0.20348.3328.mum to make custom updates. Still no go.
[Desktop Experience] Microsoft-Windows-EditionPack-Server-Full-Package~31bf3856ad364e35~amd64~~10.0.20348.1 Microsoft-Windows-EditionPack-Server-Full-WOW64-ackage~31bf3856ad364e35~amd64~~10.0.20348.1 Microsoft-Windows-Server-DesktopUX-Package~31bf3856ad364e35~amd64~~10.0.20348.1 Microsoft-Windows-Server-DesktopUX-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20348.1 [Features on demand] Microsoft-Windows-UserExperience-Desktop-Package~31bf3856ad364e35~amd64~~10.0.20348.1
Anybody has the files for reconstructing EnterpriseG 19041? The whatever127 buzzheavier link shows a "site can't be reached" error (both direct and torrent) and the Bedi script (all versions) is also unavailable.