Test 10586.1000 Windows Longhorn SERVERWEB ARM64 en-US (with official solution) Code: C:\WINDOWS\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10586.1000 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /add-package:Z:\WinSxS\update.mum Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10586.1000 Processing 1 of 1 - Adding package Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~arm64~en-US~10.0.10586.1000 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>
My dear teacher and friendI @xinso, I had just one question to do. Why do you always write something and after a few minutes, you delete it and change the text almost completely? Wouldn't it be fairer to place an observation below what has already been said, ratifying or correcting what was said above? I always thought this was unfair to other users, so much so that I don't do it, after that, I stand by my statements and if necessary I apologize if anyone felt offended. A hug and may God be with you, my friend, there are no enemies here, but friends, sharing their knowledge and goodwill. Best Resgards. @JeepWillsy58
Test 10586.1000 Windows Longhorn SERVERARM64 ARM64 en-US (with zhanglin's solution) Code: C:\WINDOWS\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10586.1000 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /add-package:Z:\WinSxS\update.mum Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.10586.1000 Processing 1 of 1 - Adding package Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~arm64~en-US~10.0.10586.1000 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32> [Credits] zhanglin
Hi dear friend @Yarrak31 This package is for version 22000.xxxx, I downloaded it in 2022... Spoiler: 22000.1.cab I remember that there were instructions given by several users on how to modify it, but I don't remember what the post was, because when I saved it I must have forgotten to create the reference text file, So I honestly don't know how to solve this, you'll have to ask and see if any of our other friends can help you. I hope you can resolve this. Best Regards. @JeepWillys58
Code: 10586.0.151029-1700.TH2_RELEASE_CLIENTSTARTER_NOAPPS_X64FRE_EN-US Windows 10 Starter 10586 archive.org/details/10586starter
Very good idea. This would be very useful. I wonder if a .mum, .manifest and catalog file generator tool would not be another idea.
I completed very early version of ConvertNT6SKUs. Since it is a prototype, it can't generate .mum, .manifest or catalog files. It can assemble unstaged install.wim files. As for reconstruction of staged images, you have to put required assembly files to sxs folder. I'll give it a try for each staged (ServerEnterpriseIA64) and unstaged (6469) images before some more improvements. After that I'll add the support for checked/debug versions.
Ok, after several tries, ServerEnterpriseIA64 6001.18000 succeeded while EnterpriseN 6469.1 failed. It has to be something with version. It looks like Package Manager requires both host and offline image to share the same version, unlike DISM. And no, I tried copying pkgmgr.exe from 6469, but it didn't run at all. Spoiler: Windows Longhorn ServerEnterpriseIA64 Don't ask me how did I install IA64 OS on VM. It is simple, I didn't. I took assemblies from IA64, changed architecture values in both .mum and .manifest files as well as renaming required files and creating new catalog files and signing. After a few tries and file renaming I got it. At the first try with the tool, I got BSOD, and that was because of mismatched EditionID registry key. Now, the BSOD shouldn't happen again, because I added a registry tweak to fix the problem. If ServerEnterpriseIA64 SKU can be ported to x86 and x64, Starter edition can definitely be ported to x64. You just need some modding skills and patience. The only way to port ServerEnterpriseIA64 SKU was taking files from IA64 ISO and modding those files. You have two alternatives for Starter x64; modding files from x86 Starter assembly files or using files from leaked unstaged beta versions.
example12345678912345678 looks like your skills are way above normal reconstruction, seems like your a real master.