Needed Microsoft-Windows-ServerAzureStackHCICorEdition~ Packages Microsoft-Windows-Client-Features-SharedWithServer-Package Microsoft-Windows-Client-Features-SharedWithServer-WOW64-Package Microsoft-Windows-Desktop-Required-ClientOnly-SharedWithServer-Package Microsoft-Windows-Desktop-Required-ClientOnly-SharedWithServer-WOW64-Package Microsoft-Windows-Server-DesktopUX-Package Microsoft-Windows-Server-DesktopUX-WOW64-Package Microsoft-Win4-Feature Microsoft-Win4-WOW64-Feature UserExperience-Desktop-Package If Microsoft-Win4-Feature & Microsoft-Win4-WOW64-Feature are not installed OR Win3-Feature is installed, offline update will remove most off SystemApps packages.
Look: Code: ------------------------------------------------------------ Add Servicing Stack update to Winre image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_1000~31bf3856ad364e35~amd64~~25398.1000.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_1000 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ------------------------------------------------------------ Add Cumulative update to Winre image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.1009.1.15 [==========================100.0%==========================] The operation completed successfully. Code: Add Servicing Stack update to Enterprise image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_1000~31bf3856ad364e35~amd64~~25398.1000.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_1000 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ------------------------------------------------------------ Add Cumulative update to Enterprise image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25398.1009.1.15 [==========================100.0%==========================] The operation completed successfully. Oh, no. SSU is zwl29107's, I just expanded and repacked. CU is my old repacked. Try zwl29107's CU and see. Code: ------------------------------------------------------------ Add Servicing Stack update to Winre image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_1000~31bf3856ad364e35~amd64~~25398.1000.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_1000 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ------------------------------------------------------------ Add Cumulative update to Winre image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at z:\1.log Code: ------------------------------------------------------------ Add Servicing Stack update to Enterprise image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 Processing 1 of 1 - Adding package Package_for_ServicingStack_1000~31bf3856ad364e35~amd64~~25398.1000.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_1000 requires the current servicing session to be reloaded. All the packages will be processed again. The operation completed successfully. ------------------------------------------------------------ Add Cumulative update to Enterprise image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at z:\1.log I can remember such a case happened once. This is the second time.
That's why I told you I don't like using updates in my isos are rtm, if I need to modify I use my script, but for installation I only use update.mum e para `950 Fods` You can do concatenation already extracted by launching each folder to temp taking the path of the .mum
kkkk it was corrected just above @xinso, but when I said it you had already corrected the .mumS of life, are you aware that this is the country of samba lol
Master, why do we still need custom updates for Enterprise? You teached, that for en-US Pro-based (Enterprise is Pro based) there is no need in custom, right? I understand if we speak about fr-FR or LTSC. but Enterprise en-us? Why? Thanks!
i am using 25398 without netfx3 (because i don't need one), but i want to make Microsoft-Windows-NetFx3-OnDemand-Package~31bf3856ad364e35~amd64~en-US~10.0.25398.1.esd just in case and i have problem. i'm trying to do this with xinso instruction here https://forums.mydigitallife.net/th...struction-project.80939/page-823#post-1839311, but 50 directories (which existing in fr-fr version) are missing
Two conditions. By default [Professional SKU] Mocrosoft-Windows-ProfessionalEdition Code: Professional, Education, Enterprise, IoTEnterprise, ProfessionalCountrySpecific, ProfessionalEducation, ProfessionalSingleLanguage, ProfessionalWorkstation, ServerRdsh, CloudEdition [Language] en-US Custom? For other SKUs and Languages. e.g. By Custom [10 SKUS] Code: :: TARGET=CoreCountrySpecific :: TARGET=Core, CoreSingleLanguage :: TARGET=EnterpriseG :: TARGET=EnterpriseS, IoTEnterpriseS, IoTEnterpriseSK :: TARGET=Starter :: TARGET=CoreN :: TARGET=EnterpriseGN :: TARGET=EnterpriseSN :: TARGET=ProfessionalN, EducationN, EnterpriseN, ProfessionalEducationN, ProfessionalWorkstationN, CloudEditionN :: TARGET=StarterN [17 Languages] Code: :: With CU 18 :: LANG=cs-CZ, de-DE, es-ES, fr-FR, hu-HU, it-IT, ja-JP :: LANG=ko-KR, nl-NL, pl-PL, pt-BR, pt-PT, ru-RU, sv-SE, tr-TR, zh-CN, zh-TW e.g. Professional "ru-RU" needs Custom "ru-RU" Language.
Two sources: 1. Server install.wim (18 languages) 2. gaiium119's 25398 languagepacks.zip (37 languages)
[Feedback for zwl29107's fixed CU at #17470] Test 25398.1009 Windows 11 Home China (Retail with Edge with Store with NetFx3) amd64 zh-CN Code: ------------------------------------------------------------ Add Cumulative update to CoreCountrySpecific image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ Test 25398.1009 Windows 11 Home (Retail with Edge with Store without NetFx3) amd64 en-US Code: ------------------------------------------------------------ Add Cumulative update to Core image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ Test 25398.1009 Windows 11 Pro (Retail with Edge with Store without NetFx3) amd64 en-US Code: ------------------------------------------------------------ Add Cumulative update to Professional image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ Test 25398.1009 Windows 11 Home N (Retail with Edge with Store without NetFx3 with Media features) amd64 en-US Code: ------------------------------------------------------------ Add Cumulative update to CoreN image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ Test 25398.1009 Windows 11 Pro N (Retail with Edge with Store without NetFx3 without Media features) amd64 zh-CN Code: ------------------------------------------------------------ Add Cumulative update to ProfessionalN image ------------------------------------------------------------ Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25398.1 An error occurred trying to open - temp\1 Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. Error: 0x800f080f The package path is not valid. Specify a path to either a CAB file or a folder containing an expanded CAB file and try the command again. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ------------------------------------------------------------ [Credits] gailium119 zwl29107