If you check the cbs.log, and there are no errors in the [SR] entries, then it shouldn't be a problem. Code: findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt"
Q: Is it possible to reconstruct 17763 Enterprise LTSC arm64? A: Absolutely not if without initial LTSC packages. Q: Is it possible to make Custom Update? A: Yes.
Tell you one joke. I failed to reconstruct EnterpriseSN all night. You know what the problem is? Code: Microsoft-Windows-Branding-EnterpriseSN-Package~31bf3856ad364e35~arm64~~10.0.117763.1.mum
From ServerDatacenter, not Client, by packages taken out of kibkalo's official Windows Server 2022 Datacenter Azure Edition image.
[17763.2330 EnterpriseSN] Code: WIM XML Information: --------------------------- <WIM> <IMAGE INDEX="1"> <DIRCOUNT>32717</DIRCOUNT> <FILECOUNT>117125</FILECOUNT> <TOTALBYTES>13523080348</TOTALBYTES> <HARDLINKBYTES>6098575143</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D7ECC7</HIGHPART> <LOWPART>0x483B6615</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D7ECC7</HIGHPART> <LOWPART>0x483B6615</LOWPART> </LASTMODIFICATIONTIME> <WIMBOOT>0</WIMBOOT> <WINDOWS> <ARCH>12</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>EnterpriseSN</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <SERVICINGDATA> <GDRDUREVISION>0</GDRDUREVISION> <PKEYCONFIGVERSION>10.0.17763.2028;2016-01-01T00:00:00Z</PKEYCONFIGVERSION> <IMAGESTATE>IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE</IMAGESTATE> </SERVICINGDATA> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>en-US</LANGUAGE> <DEFAULT>en-US</DEFAULT> </LANGUAGES> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>17763</BUILD> <SPBUILD>2330</SPBUILD> <SPLEVEL>0</SPLEVEL> <BRANCH>rs5_release</BRANCH> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 Enterprise N LTSC 2019</NAME> <DESCRIPTION>Windows 10 Enterprise N LTSC 2019</DESCRIPTION> <FLAGS>EnterpriseSN</FLAGS> <DISPLAYNAME>Windows 10 Enterprise N LTSC</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 10 Enterprise N LTSC</DISPLAYDESCRIPTION> </IMAGE> <TOTALBYTES>3558144279</TOTALBYTES> </WIM>
For some reason /get-packages stops after listing powershell v2 (i must try to remove that package). But features installs nicely with /enable-features Everything works from AD Controller to RRAS. Like I said the removal of the VDI role makes it not great for my purposes (on servers the VDI role is needed to RemoteFX, just for one), but that is a stupid decision on MS part not my fault. The only RD role left is the licensing server.
There is several way...If from my post, need use with updated unattend (1.xml & 3.xml) can be found around next few post... Use SxSv1 extract from (LCU-Baseless-19041.1149 & LCU-19041.1200)The first post for reconstruction EnterpriseS with all details here: https://forums.mydigitallife.net/th...struction-project.80939/page-224#post-1683692
I did not understand what I was doing wrong. I keep getting element not found error 1168. Log: Code: C:\Users\Admin\Desktop\Reconstruction>dism /image:C:\Users\Admin\Desktop\Reconstruction\Mount /apply-unattend:unattend.xml Deployment Image Servicing and Management tool Version: 10.0.22000.1 Image Version: 10.0.21382.1000 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.21382.1000 Removing package Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~amd64~~10.0.21382.1000 [==========================100.0%==========================] Error: 1168 Element not found. The DISM log file can be found at C:\Windows\Logs\DISM\dism.log XML file: Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.21382.1000" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> <package action="install"> <assemblyIdentity name="Microsoft-Windows-ContainerOSPlusEdition" version="10.0.21382.1000" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="C:\Users\Admin\Desktop\Reconstruction\CAB\Microsoft-Windows-ContainerOSPlusEdition~31bf3856ad364e35~amd64~~10.0.21382.1000.mum" /> </package> </servicing> </unattend>
You could try with this command instead: Code: C:\Users\Admin\Desktop\Reconstruction>dism /image:C:\Users\Admin\Desktop\Reconstruction\Mount /apply-unattend:unattend.xml /loglevel:1 /logpath:log1.log And read the log, find out which is missing: Code: C:\Users\Admin\Desktop\Reconstruction>log1.log May the right configuration for unattend.xml should be: install - remove (just revert each others) like this: Code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <servicing> <package action="install"> <assemblyIdentity name="Microsoft-Windows-ContainerOSPlusEdition" version="10.0.21382.1000" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> <source location="C:\Users\Admin\Desktop\Reconstruction\CAB\Microsoft-Windows-ContainerOSPlusEdition~31bf3856ad364e35~amd64~~10.0.21382.1000.mum" /> </package> <package action="remove"> <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.21382.1000" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" /> </package> </servicing> </unattend>