Can you explain more, how do you restore .1 I have asked tha here: https://forums.mydigitallife.net/th...rom-windows-after-cleanup.88583/#post-1853271 but didn't get an answer, - how to roll back from updated files to .1
I need xinox for the 22000 containt os I got 2000 numbers and bananas 6 months still in error message
Can you make a zipped/packed version with run as trustedinstaller version? Because without it, it fails. but with trustedinstaller, it successed. (I removed "remove defender" section) Code: A subdirectory or file temp\mount already exists. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Mount image :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Apply mum ============================================================ 1 file(s) copied. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: install EnterpriseG :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: EnterpriseG Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.27718.1000 Processing 1 of 1 - Adding package Microsoft-Windows-EditionSpecific-EnterpriseG-Package~31bf3856ad364e35~amd64~~10.0.27718.1000 [==========================100.0%==========================] The operation completed successfully. ============================================================ Set key ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.27718.1000 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ add lang ============================================================ Deployment Image Servicing and Management tool Version: 10.0.26100.1150 Image Version: 10.0.27718.1000 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.27718.1000 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------ add license.rtf ------------------------------------------------------------ A subdirectory or file temp\mount\Windows\System32\Licenses\neutral\_Default\EnterpriseG already exists. 1 file(s) copied. ============================================================ Apply Edition ============================================================ 1 file(s) copied. ============================================================ reset base ============================================================ The system cannot find the file specified. Press any key to continue . . . However, dism.exe /online /get-currentedition gets error. Code: Microsoft Windows [Version 10.0.27718.1000] (c) Microsoft Corporation. All rights reserved. C:\Users\VMware>dism /online /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.27718.1000 Image Version: 10.0.27718.1000 Current edition is: Error: 0x800f0805 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 C:\Users\VMware>
it's normal you don't have microsoft-windows-enterpriseg-edition.num if an update arrives you will recover everything
like the 26100 we have residuals or like the hotpach we are missing .mum and .manifest for the hotpach client it is in progress
example Microsoft-Windows-Branding-Client-Package~31bf3856ad364e35~amd64~~10.0.22000.1 2021-08-31 07:03:36 UTC Microsoft-Windows-Branding-Client-Package~31bf3856ad364e35~amd64~~10.0.22000.2600 2023-11-14 18:00:33 UTC Microsoft-Windows-Branding-enterpriseG-Package~31bf3856ad364e35~amd64~~10.0.22000.2600 2023-11-14 18:00:33 UTC no exit
There is nothing as a 26100.1 hotpatch targeting package. It is just a virtual package that never exist. I do not know the aim maybe reconstruction prevention. Also there is no need to that package. Just delete that package inside mum and build whatever you want. After that again change original mum. The proof that does not exists is i used unstaged.win. I deleted hotpatch targeting package from mum and reconstructed server azure from zero. After that compared all registry with original wim. Should expect there is a registry difference that hotpatch targeting package. But there is nothing. It is acceptable that there is also no such targeting package mum and cat. It does not prevent it can exist as a real package in the future. I shared unstaged.wim at first page. If anybody do not belive can use the same way as me to prove it exists.
Are you wrong it's running after the server versions we come to the ltsc client? or all since version 26080.1 it is not clear on the Microsoft side
I searched the net, you need a basic Azure account. we do it without an Azure account, it’s one thing but not acquired
I did not understand anything from your english. That package exists until at least server 2019 as virtually. I have created all versions with gui successfully and all runs ok. No need package. I do not know client side. Under server azure virtual machine installed clients have hotpatch capability now? Anybody show evidence with screenshot? If they have maybe there should be server azure installs hotpatch capability after setup like vmware tools.
dsl You need a basic Azure account. We do it without an Azure account, it’s one thing but not acquired
To use 26100.1 you need a basic Azure account. we do it without an Azure account, it’s one thing but not acquired