Hello, I try to add support of the media devices on Windows Server Core (20h2). The goal is make work DVB-T USB key. I not need the GUI. I'm happy with ServerCore.AppCompatibility. I tried to add: Microsoft-Windows-Client-Features-Package ~ 31bf3856ad364E35 ~ AMD64 ~~ 10.0.16299.15.mum But it did not work. I did not understand the part of the .esd I took the ISO Windows 10 (20h2) same version as the server to extract: \windows\winsxs \Windows\Servicing\Packages Can you help me please?
u are trying to add the driver of it ? i guess u need the audio card also working right? adding different build package should not work or might cause problems the best way i found to do that is overwriting deploying u deploy windows 10 and then server 20h1 to same vhd copying the packages and manfiest to winsxs folder and start the adding
I can not install the driver, I guess it's the media class is unknown (not support on core) I am not sure to have fully understand the procedure. what I have done: 1) installe server core 2) extract file of 10 3)add package on offline server core u deploy windows 10 and then server 20h1 -> apply install.wim of 10 and on this apply install.wim of server // not installed just apply ? 20h2 not work ? i have to downgrade to 20h1 ?
yea server core doesnt have audio class installed i will show u in cmds [more or less] dism apply-image install-win10.esd 1 F:\ cd f:\windows\winsxs\ copy manfiest\ copy f:\windows\servicing\packages\ dism appy-image install-servercore.esd 1 f:\ cd f:\windows\winsxs dism add-package packagepath:Windows.feature.require.mum dism add-package packagepath:Windows.feature.require-en-us.mum
New try: Code: Mount-WindowsImage -ImagePath .\install.wim -Name "Windows 10 Professionnel pour les Stations de travail" -path G:\W10\ Xcopy G:\W10\windows\winsxs\*.* G:\pkg\ /E Xcopy G:\W10\windows\winsxs\manfiest\*.* G:\pkg\ /E Xcopy G:\W10\\windows\servicing\packages\*.* G:\pkg\ /E Mount-WindowsImage -ImagePath .\install.wim -Name "Windows Server Datacenter" -path G:\Ws\ Xcopy G:\Ws\windows\winsxs\*.* G:\pkg\ /E /y Xcopy G:\Ws\windows\winsxs\manfiest\*.* G:\pkg\ /E /y Xcopy G:\Ws\\windows\servicing\packages\*.* G:\pkg\ /E /y cd pkg G:\pkg> Dism /Image:F:\ /add-Package /PackagePath:Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.19041.1052.mum Outil Gestion et maintenance des images de déploiement Version : 10.0.19041.844 Version de l’image : 10.0.19042.1052 Traitement de 1 sur 1 - Ajout du package Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~10.0.19041.1052 [==========================100.0%==========================] Une erreur s’est produite - Microsoft-Windows-Client-Features-Package Erreur : 0x800736cc Erreur : 14028 Un fichier du composant ne correspond pas aux informations de vérification présentes dans le manifeste du composant. Le fichier journal DISM se trouve à l’emplacement C:\WINDOWS\Logs\DISM\dism.log I have an error mismath fille vs manifeste Where are wrong ? What is the most recent version where you have been successful working audio devices ?
cos the files are not in <Drive>:\windows\winsxs\ it will output this error use sxs expend.exe* for bring it back to cab form but it will take so much time or download the cab / esd from uup dump
I think that the only server coming with a definite package for TV/BDA and media streaming stuff is Server 2012 essentials, in everything else they are missing 2003/2008 and 2008R2 or buried inside other drivers packages (home Server 2011/2012R2/2016 and so on). Which means that what you're trying to do is not convenient, because packages are like cherries: one calls another to the point that (if successful) you will end with an installation that isn't that smaller than server 2019/22 and have the full GUI. Better to start from server 2016/19/22 with full gui, then remove the paiload of the unused roles/features and, if you don't want the GUI, just set the shell to cmd.exe or powershell.exe instead of explorer.exe or start from server core 2012 (not r2) and add the tv pack and streaming stuff grabbed from server 2012 essentials (never tested that path personally)
If you want to watch the TV locally using a basic TV program, yes the BDA drivers should be enough. If you want to use WMC and/or share the TV over the network, no
It depends. My home server, which is also an HTPC, is not rock solid on server 2019 while Server 2016 works very well but lacks a couple of features I need. Server 2022 is also stable but genius Microsoft removed the Remote FX vGPU, which is likely one of the best thing released by MS (they acquired the company that developed it) So I use either Server 2017 or 2018, which don't exist "in nature" and they do what I need while being rock solid since 2017 or 2018 respectively.
Hi.LiteOS, I got error like this An error occurred - Microsoft-Windows-Server-Shell-Package Error: 0x80073701 Error: 14081 The referenced assembly could not be found. ---===---- I use copy datacenter files , and add package on core. However, got this error. I saw you did it to core+gui on 2022. Would you please help? Thanks.
Hey check the cbs log file see which package in this mega package is cause the error then try to avoid installing it
Hello LiteOS I saw you made it on 2008 r2. I am trying to do it on server 2016 tp4 10586 which can't be found on uup. Would you please help to make it detail on how to use expand function? I tried, however, it seemed just moving files only. Thanks
Hey i didn't use it for so long i might forgetting something but i check for old bat and i use it like this: c:\windows\System32\cscript.exe //NoLogo SxSExtract.vbs /IMAGE:f:\tm\Windows /VICIOUSHACKS $x $X.CAB where $x is mum file like Microsoft-Windows-IIS-WebServer-Core-ServerCommon-Package~31bf3856ad364e35~amd64~en-US~10.0.20348.1.mum it gonna just make the package into cab file with all the files that needed which cmd u run ?