https://forums.mydigitallife.net/threads/turn-off-defender-in-22h2.87471/page-2#post-1808106 Thanks for letting me know my method of removing Defender breaks CU updates, i have tested and can confirm you are correct and i have removed the info.
April 11, 2023—KB5025221 (OS Builds 19042.2846, 19044.2846, and 19045.2846). Volume, amd64, OK. How about x86 and arm64? Test Reconstruct 19044.2846 Windows 10 IoT Enterprise LTSC (without Store) x86 zh-TW Code: ------------------------------------------------------------ Set IoTEnterpriseS key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.2846 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : IoTEnterpriseS (Volume:GVLK) ============================================================ Test Reconstruct 19044.2846 Windows 10 IoT Enterprise LTSC (without Store) arm64 zh-TW Code: ------------------------------------------------------------ Add Cumulative update to IoTEnterpriseS image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~19041.2846.1.6 [==========================100.0%==========================] The operation completed successfully. ------------------------------------------------------------ Set IoTEnterpriseS key ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.19044.2846 Starting to install product key... Finished installing product key. The operation completed successfully. ============================================================ Current Edition : IoTEnterpriseS (Volume:GVLK) ============================================================
What is the difference between IoT Enterprise and IoT Enterprise LTSC? I mean how can an edition be said to be LTSC?
https://forums.mydigitallife.net/th...-enterprise-iot-enterprise-n-ltsc-2021.84509/ AC Microsoft-Windows-ProfessionalEdition (Default Edition: Enterprise) [Parent Professional & Virtuals] Professional, Education, Enterprise, IoTEnterprise, ProfessionalCountrySpecific, ProfessionalEducation, ProfessionalSingleLanguage, ProfessionalWorkstation, ServerRdsh, CloudEdition (10 Editions sharing 1 Image) LTSC Microsoft-Windows-EnterpriseSEdition (Default Edition: EnterpriseS) [Parent EnterpriseS & Virtuals] EnterpriseS, IoTEnterpriseS, IoTEnterpriseSK (3 Editions sharing 1 Image) Microsoft-Windows-EnterpriseSNEdition (Default Edition: EnterpriseSN) [Parent EnterpriseSN] EnterpriseSN (1 Edition 1 Image) To Reconstruct\Construct, use Parent Edition mum + Target Edition key. e.g. To Construct Professional, Construct Microsoft-Windows-ProfessionalEdition + Professional key To Construct IoTEnterpriseS, Construct Microsoft-Windows-EnterpriseSEdition + IoTEnterpriseS key
I'm jus from that thread. As a construction expert, you definitely have a deeper understanding of these differences. Thanks to make this clear enaugh for me.
So quick the OEM\VOL? Once solved, no more mystery. So, returning to the essence of Reconstruction is the way to go. 1. Edition Structure -------------------------------------------------------------- 2. Package Structure 3. Component Structure 4. Feature and Package -------------------------------------------------------------- 5. On Demand Feature and Package 6. Store
@xinso, I have updated the script now to disable defender updates and also change display name, description and flags as you suggested.
Test manual Construction of 23560.1000 Windows 11 Enterprise amd64 en-US Code: C:\WINDOWS\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.23516.1000 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /logpath:z:\1.log /image:K: /add-package:Z:\winsxs\Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.23560.1000.mum Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.23560.1000 Processing 1 of 1 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.23560.1000 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /english /image:K: /set-skuintldefaults:en-us Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.23560.1000 Set SKU default settings for: en-us The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.23560.1000 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32>
Can you be more detailed on how to get neutral Win32Calc packages from a Next Server desktop experience ? (installed Windows 11 Insider Preview 25951.1000 , and no win32calc) Got Microsoft-Windows-EditionSpecific-EnterpriseS-removable-Package~31bf3856ad364e35~amd64~~10.0.22621.1, but when try install package online Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum, dism error. Spoiler: dism error 2023-10-05 16:06:00, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2023-10-05 16:06:00, Info DISM DISM.EXE: 2023-10-05 16:06:00, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22621, Running architecture=amd64, Number of processors=2 2023-10-05 16:06:00, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.1 2023-10-05 16:06:00, Info DISM DISM.EXE: Executing command line: dism /online /add-package /packagepath:Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 physical location path: C:\ - CDISMManager::CreateImageSession 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 Event name for current DISM session is Global\{F3ECF64D-74A2-4D66-8D6B-7AE79B9755E7} - CDISMManager::CheckSessionAndLock 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 Create session event 0x220 for current DISM session and event name is Global\{F3ECF64D-74A2-4D66-8D6B-7AE79B9755E7} - CDISMManager::CheckSessionAndLock 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 No Sandbox was created, DISM running in-place. - CDISMManager::CreateImageSessionFromLocation 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 Successfully loaded the ImageSession at "C:\Windows\System32\Dism" - CDISMManager::LoadRemoteImageSession 2023-10-05 16:06:00, Info DISM DISM Image Session: PID=472 TID=1352 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore 2023-10-05 16:06:00, Info DISM DISM OS Provider: PID=472 TID=1352 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect 2023-10-05 16:06:00, Info DISM DISM OS Provider: PID=472 TID=1352 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect 2023-10-05 16:06:00, Info DISM DISM Provider Store: PID=472 TID=1352 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect 2023-10-05 16:06:00, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2023-10-05 16:06:00, Info DISM DISM Provider Store: PID=472 TID=1352 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2023-10-05 16:06:00, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2023-10-05 16:06:00, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 Image session successfully loaded from location: C:\Windows\System32\Dism - CDISMManager::CreateImageSession 2023-10-05 16:06:00, Info DISM DISM.EXE: Target image information: OS Version=10.0.22621.1413, Image architecture=amd64 2023-10-05 16:06:00, Info DISM DISM.EXE: Image session version: 10.0.22621.1 2023-10-05 16:06:00, Info DISM DISM Transmog Provider: PID=472 TID=3100 Current image session is [ONLINE] - CTransmogManager::GetMode 2023-10-05 16:06:00, Info DISM DISM Transmog Provider: PID=472 TID=3100 Audit Mode: [No] - CTransmogManager::Initialize 2023-10-05 16:06:00, Info DISM DISM Transmog Provider: PID=472 TID=3100 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType 2023-10-05 16:06:00, Info DISM DISM Transmog Provider: PID=472 TID=3100 Product Type: [WinNT] - CTransmogManager::Initialize 2023-10-05 16:06:00, Info DISM DISM Transmog Provider: PID=472 TID=3100 Product Type ServerNT : [No] - CTransmogManager::Initialize 2023-10-05 16:06:00, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.1344_none_e953938a42d5ff76\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2023-10-05 16:06:00, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.1344_none_e953938a42d5ff76\wcp.dll' : got STATUS_SUCCESS 2023-10-05 16:06:00, Info DISM DISM Driver Manager: PID=472 TID=3100 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=3100 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=3100 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\CBS\CBS.log - CDISMPackageManager::Initialize 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=3100 Loaded servicing stack for online use. - CDISMPackageManager::CreateCbsSession 2023-10-05 16:06:00, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.1344_none_e953938a42d5ff76\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2023-10-05 16:06:00, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.22621.1344_none_e953938a42d5ff76\wcp.dll' : got STATUS_SUCCESS 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=7788 Processing the top level command token(add-package). - CPackageManagerCLIHandler:rivate_ValidateCmdLine 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=7788 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=7788 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=7788 Encountered the option "packagepath" with value "Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum" - CPackageManagerCLIHandler:rivate_GetPackagesFromCommandLine 2023-10-05 16:06:00, Error DISM DISM Package Manager: PID=472 TID=7788 Failed opening package. - CDISMPackageManager::Internal_CreatePackageByPath(hr:0x800b0109) 2023-10-05 16:06:00, Error DISM DISM Package Manager: PID=472 TID=7788 Failed to get the underlying CBS package. - CDISMPackageManager::OpenPackageByPath(hr:0x800b0109) 2023-10-05 16:06:00, Error DISM DISM Package Manager: PID=472 TID=7788 Failed to open the package at location: "Microsoft-Windows-win32calc-Package~31bf3856ad364e35~amd64~~10.0.22621.1.mum" - CPackageManagerCLIHandler:rocessPackagePath(hr:0x800b0109) 2023-10-05 16:06:00, Error DISM DISM Package Manager: PID=472 TID=7788 Failed to get the count of packages from the command line. - CPackageManagerCLIHandler:rocessCmdLine_AddPackage(hr:0x800b0109) 2023-10-05 16:06:00, Error DISM DISM Package Manager: PID=472 TID=7788 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800b0109) 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=7788 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine 2023-10-05 16:06:00, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800B0109 2023-10-05 16:06:00, Info DISM DISM Package Manager: PID=472 TID=7788 Finalizing CBS core. - CDISMPackageManager::Finalize 2023-10-05 16:06:00, Info DISM DISM Manager: PID=7576 TID=5544 Closing session event handle 0x220 - CDISMManager::CleanupImageSessionEntry 2023-10-05 16:06:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2023-10-05 16:06:00, Info DISM DISM.EXE: 2023-10-05 16:06:00, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2023-10-05 16:06:00, Info DISM DISM.EXE: