It is not corrupted. It is made just to suit UUP image restore needs. It changes from old builds to new ones. So, obviously, the 22000 script is not applicable to 17134.
Then how can I make it installable? The 22000 script is appliable on 17763, 18362 and 19041, So WHY DOESN'T 17134 work?
Try to find one older Unstaged iso and imitate. 14357.1000, too old. 19100.1051, too new. 10240.16384 10586.0 14393.0 -------------------------------------- 15063.0 16299.15 -------------------------------------- 17134.1 17763.1 =================== 18362.1 19041.1 -------------------------------------- 22000.1
I replaced the manifests from uup professional_xx-xx.esd and it successfully entered installation phase but got this error: Code: 2022-05-01 13:41:01, Error CSI 0000ab0c (F) STATUS_CANNOT_DELETE #27943142# from Windows::Rtl::SystemImplementation::MarkFileDeletePending(...)[gle=0xd0000121] 2022-05-01 13:41:01, Error CSI 0000ab0d@2022/5/1:05:41:01.758 (F) onecore\base\wcp\sil\systemisolationlayer.cpp(349): Error STATUS_CANNOT_DELETE originated in function Windows::Rtl::SystemImplementation::MarkFileDeletePending expression: (null)
I didn't. I read the log. It said that it failed to remove api-xxx.dll in \Windows\System32\downlevel. Also fix.cmd works:
Which edition you install? Which packages, UUP? I still get "Invalid Data". Code: C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\Unstaged-Wim-Creation-WinRE\temp\mount\Packages\1.xml Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.17134.1 [==========================100.0%==========================] Error: 13 The data is invalid. The DISM log file can be found at z:\1.log C:\windows\system32> What is fix.cmd?
17134 fixes: Extract all neutral manifests,mums and cats from uup xxx_xx-xx.esd.Delete the 0KB ones and replace the ones in Z:\packages. Hint1 : Only neutral ones are needed. Hint2 : Microsoft-Windows-Holographic-Desktop-Analog-WOW64-Packages is missing. Either extract or remove in Professional.mum is acceptable. Hint3 : Use fix.cmd (The one I posted to fix 17763) to fix manifest problems.
@xinso, @gailium119 I've installed Windows Server 2019. And there're bunch of editions in Windows\servicing\Editions directory. But the real question is where I can obtain their .mum and .cat files. List of editions: Code: ServerARM64 ServerAzureCor ServerCloudStorage ServerDatacenterACor ServerDatacenterCor ServerDatacenter ServerDatacenterEvalCor ServerDatacenterEval ServerHyperCore ServerSolution ServerStandardACor ServerStandardCor ServerStandard ServerStandardEvalCor ServerStandardEval ServerStorageStandard ServerStorageStandardEval ServerStorageWorkgroup ServerStorageWorkgroupEval ServerWeb There might be more than that since I've installed only ServerStandard (not Core) edition. I can't find their .mum and .cat files in Windows\servicing\Packages directory.
Can you help me on how to get these packages? In servicing\packages directory, there're only ServerDatacenter and ServerStandard edition packages.