Thank you very much for a really great calculator package. I incorporated your calculator into the vNext project version 0.03. There's now a "History" section where I celebrate how great your calculator is! The newly added "Known Issues" section tries to explain why even your great calculator is still not "great enough" to please Microsoft. We have to wait for Microsoft to release a new version of the calculator specific to the upcoming 20H2 release of LTSC/IoT. In the meantime, the reconstructions created by following the SPP project are updateable by using baseless psf/mum pairs. To give you an idea of what the problem is, here are just some of the calculator related hiccups taken from CBS and DISM logs which eventually led to a failed non-baseless, normal cumulative update of an installed IoT image built using your great calculator. Code: CBS/DISM log sample CBS: ================================= Info CBS: Session: 30912933_780318345 initialized by client UpdateAgentLCU, external staging directory: (null), external registry directory: (null) Info CBS: ActionList: Adding package: \\?\C:\windows\SoftwareDistribution\Download\b59d433ee08ad8605378d90c5d7a10ed\Windows10.0-KB5005565-x64.cab . . CBS: ================================= Info CBS: Checking System Update Readiness. Info CBS: Info CBS: (p) CBS MUM Corrupt (n) Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1 Info CBS: Repair failed: Missing replacement mum/cat pair. Info CBS: Info CBS: Summary: Info CBS: Operation: Detect and Repair Info CBS: Operation result: 0x800f081f Info CBS: Last Successful Step: Remove staged packages completes. Info CBS: Total Detected Corruption: 1 Info CBS: CBS Manifest Corruption: 1 Info CBS: CBS Metadata Corruption: 0 Info CBS: CSI Manifest Corruption: 0 Info CBS: CSI Metadata Corruption: 0 Info CBS: CSI Payload Corruption: 0 Info CBS: Total Repaired Corruption: 0 Info CBS: CBS Manifest Repaired: 0 Info CBS: CSI Manifest Repaired: 0 Info CBS: CSI Payload Repaired: 0 Info CBS: CSI Store Metadata refreshed: True Info CBS: Staged Packages: Info CBS: CBS Staged packages: 8 Info CBS: CBS Staged packages removed: 8 Info CBS: Info CBS: Total Operation Time: 856 seconds. Info CBS: Ensure WCP corruption flag is clear Info CBS: All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear Info CBS: Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] Info CBS: Failed to read uninitialized correlation vector [HRESULT = 0x80004005 - E_FAIL] Info CBS: Failed to get correlation vector [HRESULT = 0x80004005 - E_FAIL] Info CBS: Failed to send report on CheckSUR status [HRESULT = 0x80004005 - E_FAIL] Info CBS: Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING] Info CBS: Reboot mark cleared . . CBS: ================================= CBS (p) CBS MUM Corrupt (n) Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1 CBS Repair failed: Missing replacement mum/cat pair. CBS Repr: Could not find missing package manifest/cat for package:Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1 in the sandbox . . Info CBS: Exec: Package: Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1 is already in the correct state, current: Installed, targeted: Installed Info CBS: Exec: Skipping Package: Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1, Update: win32calc because it is already in the correct state. . . DISM: ================================= DISM: DISM Package Manager: PID=6316 TID=6044 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession DISM: DISM Package Manager: PID=6316 TID=6044 Package Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.19041.1 with CBS state 7(CbsInstallStateInstalled) being mapped to dism state 5(DISM_INSTALL_STATE_INSTALLED) - CDISMPackage::LogInstallStateMapping
To those viewing this thread who might care. The Windows 10 Enterprise IoT vNext Client Reconstruction Project vNext project has increased the version to 0.03. Of interest to those who may have struggled before, I added some more details and simplified the build process. For many MDL members, the process described in the link to a tutorial thread made by @KedarWolf is just what they "always do" for any type of build they make--"common knowledge" or "best practices". Starting with the base 19041.1 image is only something I started doing recently and, I have to say, it really makes a huge difference to the quality (stability/adaptability) of whatever image I make, reconstruction or otherwise.
I've never tested it. Windows Product Policy Editor https://forums.mydigitallife.net/threads/windows-product-policy-editor.39411/ It'd be nice if PAE patch author could make one for Kernel-MUI-Language-Allowed EMPTY.
So, there is some modified install.wim, where a policy is replaced/changed, and you can install and update? Can you please guide me to the topic?
Nice! If they start from scratch Win11 (from 22000), does Starter exist? And what is a working IOTS key for 22000 and up
1. No Starter. It is removed at the end of image creation. 2. 20348\22000's key. NOT 19041.1 product.ini which is 17763. (Unless it is renewed for 19044 release.)
You want to learn what vNext LTSC Client is to be? Keep testing 22XXX Server, and overlook ServerManager. ATM, focus on whether Microsoft.SecHealthUI_1000.22463.1000.0_x64__8wekyb3d8bbwe (Windows APP which needs Store to update) or Microsoft-SecHealth-UI-Package (System App which is updated by LCU) Q: Is there Store on LTSC?