Q: What's the difference between these two: Code: wimlib-imagex optimize install.wim and Code: dism /english /export-image /sourceimagefile:1.wim /sourceindex:1 /destinationimagefile:install.wim /Compress:max /CheckIntegrity
Windows 10 License does not have Windows 11 WinX menu Product policy. This is why any Windows 11 activated with Windows 10 License does not have WinX menu. Activation is one thing; Functionality is another.
I found Skylined speaks the least. Once there is any problem, he\she will lend a hand if he\she can. Now. I focus on three members: 1. gailium119 2. Skylined 3. zwl29107 I want to learn from them. Unfortunately, I am not able to follow most oftenly. Too deep to me.
Try it and got a couple error Spoiler Code: Select Desired edition (with Store): [1] Windows 11 Enterprise LTSC [2] Windows 11 IoT Enterprise LTSC Please enter the number of the desired edition: 2 Converting 22000.1 Windows 11 Professional to IoT Enterprise LTSC (with Store) amd64 en-US Mounting image Deployment Image Servicing and Management tool Version: 10.0.26100.1 Mounting image [==========================100.0%==========================] The operation completed successfully. Removing Notepad-FOD-Package (Professional) Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Removing package Microsoft-Windows-Notepad-System-FoD-Package~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Creating EnterpriseS Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Integrating Language Pack en-US Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Starting to install product key... Finished installing product key. The operation completed successfully. Current Edition : IoTEnterpriseS (OEM) Setting up and copying license files Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 The operation completed successfully. Removing Apps Integrating Notepad-FOD-Package (IoTEnterpriseS) Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-Notepad-FoD-Package~31bf3856ad364e35~wow64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Error: 87 No packages were found that require processing. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Integrating FOD Packages (IoTEnterpriseS) Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-MSPaint-FoD-Package~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-MSPaint-FoD-Package~31bf3856ad364e35~wow64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Error: 87 No packages were found that require processing. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Processing 1 of 1 - Adding package Microsoft-Windows-SnippingTool-FoD-Package~31bf3856ad364e35~amd64~~10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 Error: 87 No packages were found that require processing. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log Adding PhotoViewer Updates Not Found Reset Base Image. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 [==========================100.0%==========================] The operation completed successfully. Integrating New Microsoft Store + Dependencies Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image Version: 10.0.22000.1 The operation completed successfully. Unmounting image Deployment Image Servicing and Management tool Version: 10.0.26100.1 Image File : C:\22000.1_EnterpriseS_with_New_Store_x64\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Using LZX compression with 4 threads Archiving file data: 7075 MiB of 7075 MiB (100%) done Deleted file - C:\22000.1_EnterpriseS_with_New_Store_x64\install.wim Setting the NAME property of image 1 to "". Setting the DESCRIPTION property of image 1 to "". Setting the FLAGS property of image 1 to "". Setting the DISPLAYNAME property of image 1 to "". Setting the DISPLAYDESCRIPTION property of image 1 to "". Setting the NAME property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". Setting the DESCRIPTION property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". Setting the FLAGS property of image 1 to "IoTEnterpriseS". Setting the DISPLAYNAME property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". Setting the DISPLAYDESCRIPTION property of image 1 to "Windows 11 IoT Enterprise LTSC 2021 (with Store)". 22000.1 Windows 11 IoT Enterprise LTSC (with Store) amd64 en-US has been successfully created Press any key to continue . . . but install.wim created and I haven't try to install it yet
Has this been checked? choice 1 or 2 the result is the same Windows 11 IoT Enterprise LTSC Code: [1] Windows 11 Enterprise LTSC [2] Windows 11 IoT Enterprise LTSC I'm also experiencing the same error Code: Error: 87 No packages were found that require processing. Is it related to wofadk.sys?
I had done these checks before and they worked, maybe I forgot to adjust something in the IFs. I will re-upload the script with the correction to this. Maybe I'm not expressing myself well, you should download the language packs FODs that I mentioned so that there are no errors. example: Extract the script file to the location C:\ Copy the files "microsoft-windows-notepad-fod-package-wow64-bg-bg.cab" to the script folder C:\22000.1_EnterpriseS_x64\files\FOD\Notepad-FOD This is the same with all other FOD packages as only the language pack is required for them. When you download the language pack (lp) you must extract its contents into the lp folder of the script.
Due to some issues with some users, it seems that some are not following the instructions, some are getting the error "No packages were found that require processing." because they are simply not placing the fod language packs in their correct locations. others are downloading the esd client language pack and not extracting it into the script's lp folder.. so it seems that I will have to re-upload the script with some implementations that may be able to automate some things.