Updated the Windows 7 Starter x64 to V2. New version fixes problem which caused upgrades from Starter to Home Basic fail with CBS_E_NO_ACTIVE_EDITION error. Thanks to @Enthousiast for reporting. Code: # dism /logpath:test.log /english /image:mount /set-edition:HomeBasic Deployment Image Servicing and Management tool Version: 10.0.17763.771 Image Version: 6.1.7601.17514 Pended operations ignored. When this image is next booted, these operations will be processed. Starting to update components... Removing package Microsoft-Windows-EnterpriseEdition~31bf3856ad364e35~amd64~~6.1.7601.17514 [==========================100.0%==========================] Finished updating components. Starting to apply edition-specific settings... Finished applying edition-specific settings. The operation completed successfully.
I gave up on the whole thing, lol, I followed everything, image was mounted and then just after when it went to do something it always came up with DISM "Error: 1168 Element not found." so I deleted everything and said frig it, lol
This happened to me on Windows 10 Starter edition. I have had success with both G editions, so what is up?
SKU seems important. Used a Core (Windows 10 Home 10563.0 rs2) and it ran through. Failed earlier with Enterprise SKU.
Sorry if this is a dumb question, but is it possible to reconstruct Windows 7 Starter N x64 from Windows 7 Home Basic N x64? I looked inside of a Windows 7 Home Basic N x64 WIM file and there is a StarterN.xml file present.
Not possible. There are no 18362/19041 EnterpriseS packages. I'm not going to build frankenbuild based on 17763 LTSC packages.
Apart from the obvious feature limitations of Windows 7 Starter x86, is there a memory limitation (x86 only supports 2 GB of RAM)? Just curious.
OK, thanks for telling me. Do I need to modify the script to perform the conversion? Or do I simply place a Home Basic N x64 install.wim file into the script directory?