Q: Does WirelessDisplay require Media Features? If not, is it possible to make it applicable to all Client Editions with\without Media Features?
That's not my post. It's RobrPatty Post #1443 Code: forums.mydigitallife.net/threads/guide-discussion-windows-editions-reconstructions.88605/page-73#post-1868957
@Ace2 We can install packages in this simple way. e.g. Code: echo. echo ------------------------------------------------------------ echo Add FoD echo ------------------------------------------------------------ echo. for /f %%i in ('dir /b files\Fod\Neutral') do (echo %%i&dism /english /quiet /image:%MT% /add-package:files\Fod\Neutral\%%i) echo. echo ------------------------------------------------------------ echo Add %LANG% FoD language echo ------------------------------------------------------------ echo. for /f %%i in ('dir /b files\Fod\Lang\*%LANG%*') do (echo %%i&dism /english /quiet /image:%MT% /add-package:files\Fod\Lang\%%i) ---> Code: ------------------------------------------------------------ Add FoD ------------------------------------------------------------ Microsoft-Windows-WirelessDisplay-FOD-Package-amd64 ------------------------------------------------------------ Add en-US FoD language ------------------------------------------------------------ Microsoft-Windows-WirelessDisplay-FOD-Package-amd64-en-us ---> Code: ------------------------------------------------------------ Get Capabilities ------------------------------------------------------------ App.StepsRecorder~~~~0.0.1.0 | Installed App.WirelessDisplay.Connect~~~~0.0.1.0 | Installed Browser.InternetExplorer~~~~0.0.11.0 | Installed DirectX.Configuration.Database~~~~0.0.1.0 | Installed Language.Basic~~~en-US~0.0.1.0 | Installed Language.Handwriting~~~en-US~0.0.1.0 | Installed Language.OCR~~~en-US~0.0.1.0 | Installed Language.Speech~~~en-US~0.0.1.0 | Installed Language.TextToSpeech~~~en-US~0.0.1.0 | Installed MathRecognizer~~~~0.0.1.0 | Installed Media.WindowsMediaPlayer~~~~0.0.12.0 | Installed Microsoft.Windows.MSPaint~~~~0.0.1.0 | Installed Microsoft.Windows.Notepad~~~~0.0.1.0 | Installed Microsoft.Windows.PowerShell.ISE~~~~0.0.1.0 | Installed Microsoft.Windows.WordPad~~~~0.0.1.0 | Installed OpenSSH.Client~~~~0.0.1.0 | Installed Windows.Client.ShellComponents~~~~0.0.1.0 | Installed ---> Code: App.WirelessDisplay.Connect~~~~0.0.1.0 | Installed We just provide target packages in a folder, and let script detect and install for us.
20348, FodMetadata is identical between Client and Server. Open Server install.wim and check it out. Now. sakatgg must be wondering about the way to add WirelessDispay packages into script. [location] 20348.1_ServerDatacenter_to_Professional_amd64_en-US\files\Fod\neutral\ Microsoft-Windows-WirelessDisplay-FOD-Package-amd64 + 20348.1_ServerDatacenter_to_Professional_amd64_en-US\files\Fod\en-us\ Microsoft-Windows-WirelessDisplay-FOD-Package-amd64-en-us [script] Ahead of "Add VCLibs" echo. echo ------------------------------------------------------------ echo Add Wireless Dispaly echo ------------------------------------------------------------ echo. for /f %%i in ('dir /b files\Fod\Neutral') do (echo %%i&dism /english /quiet /image:%MT% /add-package:files\Fod\Neutral\%%i) echo. echo ------------------------------------------------------------ echo Add en-US Wireless Dispaly language echo ------------------------------------------------------------ echo. for /f %%i in ('dir /b files\Fod\Lang\*en-US*') do (echo %%i&dism /english /quiet /image:%MT% /add-package:files\Fod\Lang\%%i) echo. echo ------------------------------------------------------------ echo Add VCLibs echo ------------------------------------------------------------ echo. . . . PS: You can add as many "package folders" as you wish.
You are correct, i have just checked by extracting \3\Windows\servicing\FodMetadata\FoDMetadata_Client.cab & \3\Windows\servicing\FodMetadata\metadata\DesktopTargetCompDB_Neutral.xml.cab
Q: How to Reconstruct 20348.1 Client LTSC with Server image? Possible? These things are unnecessary in 20348.1_ServerDatacenter_to_Professional_amd64_en-US.7z: 1. Create.cmd Code: :: Add Driver dism /english /quiet /image:%MT% /Add-Driver /Driver:files\VMDriver /recurse echo. echo ------------------------------------------------------------ echo Add VCLibs echo ------------------------------------------------------------ echo. for /f %%x in ('dir /b files\amd64fre\*.appx') do ( echo %%x dism /english /quiet /image:%MT% /Add-ProvisionedAppxPackage /PackagePath:files\amd64fre\%%x /SkipLicense ) 2. files\ Code: amd64fre
No. It will faill for hash issue of Microsoft-Windows-Shell32-OEMDefaultAssociations-Legacy-Package~31bf3856ad364e35~amd64~~10.0.20348.1.cat. Q: Can I use AC's Microsoft-Windows-Shell32-OEMDefaultAssociations-Package~31bf3856ad364e35~amd64~~10.0.20348.1? A: Yes. It is just Default Associations of App.
Q: Which Apps are not compatible with 20348.1 System? A: At least four. 1. Xbox. 2. Windows Clock. 3. Microsoft photos. 4. Phone Link. I did not install Xbox, it appeared....