setuperr.log Code: 2022-03-17 21:16:40, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490] 2022-03-17 21:24:10, Error IBS Callback_Locale_InstallLocales:dism.exe failed. Process exit code is [0x57]. setupact.log Code: 2022-03-17 21:16:28, Info [0x0601a4] IBS LoadWorkerModules:Successfully added worker module ErrorHandler in winsetup.dll 2022-03-17 21:16:38, Warning [0x070026] DIAG Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0 2022-03-17 21:16:40, Error [0x060126] IBS CallBack_ImageWasSelectedInUi: An error occurred while removing the MultiEdition key from the blackboard.[gle=0x00000490] 2022-03-17 21:16:40, Warning [0x07008d] DIAG Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106 2022-03-17 21:16:42, Warning [0x070026] DIAG Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0 2022-03-17 21:17:40, Warning IBS InstallEditionPackages: Failed to set ProductType [WinNT] under [{bf1a281b-ad7b-4476-ac95-f47682990ce7}E:/Windows/System32/config/SYSTEM\ControlSet001\Control\ProductOptions]; Error = 0x57.
[QUOTE="xinso, post: 1727367, member: 60494" Yes, the one you have made and shown to me. You just need to learn how to make it fully functional.[/QUOTE] Unstaged install.wim (17 MB) is a good thing to use as a template to make any image you want. There is no need to convert on other mirrors as before. 22000Unstaged ISO Although the installation on the VM was unsuccessful, after reading it, the package was basically installed successfully. I don’t know why the language package was not installed? Spoiler
I don't understand on how to use this script. I tried to open as Administrator and here are the results: Code: ............................................................................... ..............................Downloading FODs...................................... ............................................................................... deleting fods.. ......Moving install files......... Deployment Image Servicing and Management tool Version: 10.0.17763.1697 Mounting image [==========================100.0%==========================] The operation completed successfully. .......................... ...Creating vhd... .......................... .......................... ...Releasing esd.. .......................... Deployment Image Servicing and Management tool Version: 10.0.17763.1697 Error: 2 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log .......................... ...Copying Packages.. .......................... 1 dir(s) moved. .............................................. ...Creating Barebone wim.. ............................................. Invalid path The system cannot find the file specified. Invalid path .............................................. ...Creating ALL editions.. ............................................. This process cannot access the file because the file is being used by another process. This process cannot access the file because the file is being used by another process. 7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21 Scanning the drive for archives: This process cannot access the file because the file is being used by another process. 7-Zip 19.00 (x64) : Copyright (c) 1999-2018 Igor Pavlov : 2019-02-21 Scanning the drive for archives: This process cannot access the file because the file is being used by another process. ......Creating Packages............ Could Not Find C:\Users\Admin\Desktop\Unstaged\Unstaged\_work\mount3\packages\update.mum Could Not Find C:\Users\Admin\Desktop\Unstaged\Unstaged\_work\mount3\packages\*$filehash* The system cannot find the path specified. Press any key to continue . . . Press any key to continue . . . sed: can't read .\editions\Professional.mum: No such file or directory sed: can't read .\editions\Professional.mum: No such file or directory The system cannot find the file .\enterpriseg1.mum. sed: can't read .\editions\ProfessionalN.mum: No such file or directory sed: can't read .\editions\ProfessionalN.mum: No such file or directory The system cannot find the file .\EnterpriseGN1.mum. The system cannot find the file specified. The system cannot find the file specified. The system cannot find the file specified. 1..... 2... The filename, directory name, or volume label syntax is incorrect. Creating Langpack Of de-de.......... ERROR: The system cannot find the file specified. ..\lp\microsoft-windows-client-languagepack-package_de-de-amd64-de-de.esd System ERROR: The system cannot find the file specified. Creating Langpack Of en-us.......... ERROR: The system cannot find the file specified. ..\lp\microsoft-windows-client-languagepack-package_en-us-amd64-en-us.esd System ERROR: The system cannot find the file specified. Creating Langpack Of tr-tr.......... ERROR: The system cannot find the file specified. ..\lp\microsoft-windows-client-languagepack-package_tr-tr-amd64-tr-tr.esd System ERROR: The system cannot find the file specified. Deployment Image Servicing and Management tool Version: 10.0.17763.1697 Image File : C:\Users\Admin\Desktop\Unstaged\Unstaged\unstaged.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17763.1697 Error: 0xc1420127 The specified image in the specified wim is already mounted for read/write access. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log .......................... ...Creating vhd... .......................... .......................... ...Releasing esd.. .......................... Deployment Image Servicing and Management tool Version: 10.0.17763.1697 Error: 2 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log .............................................. ...Creating Barebone wim.. ............................................. Invalid path The system cannot find the file specified. Invalid path This process cannot access the file because the file is being used by another process. Creating de-de.......... Retrieving aria2 script... The system cannot find the file specified. Exception caught Exception: [Logger.cc:73] errorCode=1 Failed to open the file ..\files\aria2_download.log, cause: n/a The Exception: Logger.cc:73 line loops infinitely. I don't know if anyone gets this aswell.
https://forums.mydigitallife.net/th...struction-project.80939/page-351#post-1727342 https://forums.mydigitallife.net/th...struction-project.80939/page-351#post-1727343 Learn to do Reconstruction good should be more useful, IMHO.
They are not seen in official iso. I see the Unstaged 1. expands whole system mum\cat into C:\Windows\servicing\Packages 2. expands whole system files into C:\Windows\WinSxS 3. installs system 4. installs system language pack Outcome: Barebone system Code: PerfLogs Program Files Program Files (x86) ProgramData sources (this is created by system language pack, useless) Users Windows
The Unstaged ISO (or created Unstaged image ) --> ISO boot to install --> sysprep \generalize \oobe \shutdown --> capture --> normal image This is regular sequences before you can boot an image which has been applied to a partition. I don't know if you have followed it. PS: Unstaged ISO has license.rtf and other issues. Created Unstaged image, no problem at all, alike normal image, just could not apply to a partion and boot to OOBE.
As stated at #7025, yes. Be aware: Without full functionalities, Unstaged "Windows 11" is not possible to be working fine after installed. Unstaged barebone image is fresh creation from scratch by you. UUP image is already-made full image by Microsoft --> splitted by Microsoft --> restored by you. PS: DO NOT apply pressure to yourself about Unstaged ISO script.
S Strange.Same image that has been staged by unattend, when using setup.exe to install instead of dism++/winntsetup, it works
I assume there need a registry tweak Question: What if I directly capture the partition installed via setup? Like: Unstaged.wim->iso\sorces\install.wim->C:->Capture.wim It WILL boot ,right?
Hmmm, black screen. And when you press Ctrl+Shift+F3, you can see OOBE and reboot. Then error popped up: Code: Windows Setup could not configure Windows to run on this PC's hardware. PS: The solutions on the web is for normal image which has been generalized, NOT Unstaged.
You didn't see what I've said. I mean capture the partition that iso-boot installs the system to wim.