Windows 10 Global Edition VS China Government https://forums.mydigitallife.net/threads/windows-10-global-edition-vs-china-government.80933/
Test manual Construction of 22000.1 Windows 11 Enterprise arm64 en-US 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.22000.1 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>dism /English /image:K: /add-package:Z:\Microsoft-Windows-Client-LanguagePack-Package_en-us-arm64-en-us.esd Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~arm64~en-US~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>dism /English /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22000.1 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\windows\system32>
Hi, is there any way that I can find or download Repair Content Packages? I would like to test unknown Windows versions like Windows 8.1 EnterpriseSubscriptionN or 32-Bit Windows Server 2012 or 2016.
A (working) 32bit modern server would be a great achievement. Years ago I tried to make a 32bit server 2008r2 using bits from Win7 and 2008, it somewhat worked but not the part I needed (the domain controller part).
Old Image VS New Platform ---> New CbsProvider & OSProvider New Image VS Old Platform ---> Some build of New Servicing Stack compatible with the Platform
I want to ask u how to remove cloudexperiencehost and client.cbs ... i read ur post in msmg forum... Sorry everyone if my post here is oot
@ zhanglin For 25300.1000 ARM64 Unstage, older Servicing Stack is not enough. It still needs older Cbs & OS Providers. Be aware: Older than the older Servicing Stack.
Q: How to do 22621.1 ARM64 Unstage base image? The 25300.1000 one will install it in full image. But unable to show EditionID Code: C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Current edition is: Error: 5023 The group or resource is not in the correct state to perform the requested operation. The DISM log file can be found at z:\1.log C:\windows\system32> until you manually reinstall it. Code: C:\windows\system32>dism /english /logpath:z:\1.log /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.22621.1 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\windows\system32>
Thank you. [Before] Code: dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml 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.22621.1 [===========================96.6%======================== ] Error: 1726 The remote procedure call failed. An error occurred closing a servicing component in the image. Wait a few minutes and try running the command again. The DISM log file can be found at z:\1.log C:\windows\system32> [After] Code: dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml ren K:\Windows\servicing\Version\10.0.25262.1000 10.0.22621.1 dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml 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.22621.1 [===========================96.6%======================== ] Error: 1726 The remote procedure call failed. An error occurred closing a servicing component in the image. Wait a few minutes and try running the command again. The DISM log file can be found at z:\1.log C:\windows\system32>ren K:\Windows\servicing\Version\10.0.25262.1000 10.0.22621.1 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.22621.1 [==========================100.0%==========================] The operation completed successfully. C:\windows\system32>
Foreign files in 22621.1 ARM64 Unstage base image: [Dism] Windows\System32\Dism\CbsProvider.dll (22000.1) Windows\System32\Dism\OSProvider.dll (22000.1) + Windows\SysWOW64\Dism\CbsProvider.dll (22000.1) Windows\SysWOW64\Dism\OSProvider.dll (22000.1) [ServicingStack] Windows\servicing\Version\10.0.25262.1000 + Windows\WinSxS\arm64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.25262.1000_none_f09754ebbb676b03 Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.25262.1000_none_9478b12e030a0531 Q: What about 22000.1 ARM64 Unstage base image? A: All 22000.1.