Q: How to modify Feature "display" language? A: You can change "description" and "displayName" in Windows-Defender-Client-Package~31bf3856ad364e35~amd64~xx-XX~10.0.17763.1\update.mum. Code: <update description="Windows Defender Antivirus helps protect your machine from malware." displayName="Windows Defender Antivirus" name="Windows-Defender"> <mum2:customInformation xmlns:mum2="urn:schemas-microsoft-com:asm.v3"> <ServerComponent Description="Windows Defender Antivirus helps protect your machine from malware." DisplayName="Windows Defender Antivirus" Id="1003" Type="Feature" UniqueName="Windows-Defender"/> </mum2:customInformation>
Q: Could "AntiMalware" and "Malware Removal Tool" and "Unknown Malware Feedback" be incorporated into "Windows Defender" (at least for Server)?
What good is it? (I found this from 21343.1000 microsoft-windows-userexperience-desktop-package-amd64.cab.) Code: <Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.21327.0" MaxVersionTested="10.0.32767.0"/> </Dependencies> This is practical to end users about upgrade trick: C:\Windows\servicing\Editions\UpgradeMatrix.xml. Code: <VersionRanges> <Range name="any" minVersion="*.*.*.*" maxVersion="*.*.*.*" minSPVersion="0.0"/> <Range name="winxp" minVersion="5.1.2600.*" maxVersion="5.1.2600.*" minSPVersion="3.0"/> <Range name="winxp64" minVersion="5.2.3790.*" maxVersion="5.2.3790.*" minSPVersion="2.0"/> <Range name="ws2k8" minVersion="6.0.6001.*" maxVersion="6.0.6099.*" minSPVersion="1.0"/> <Range name="WS2k8SP2" minVersion="6.0.6001.*" maxVersion="6.0.6001.*" minSPVersion="2.0"/> <Range name="vista" minVersion="6.0.6001.*" maxVersion="6.0.6099.*" minSPVersion="1.0"/> <Range name="vistartm" minVersion="6.0.6000.*" maxVersion="6.0.6000.*" minSPVersion="0.0"/> <Range name="win7" minVersion="6.1.7600.*" maxVersion="6.1.7699.*" minSPVersion="0.0"/> <Range name="win7sp1" minVersion="6.1.7601.*" maxVersion="6.1.7699.*" minSPVersion="1.0"/> <Range name="win7rtm" minVersion="6.1.7600.*" maxVersion="6.1.7600.*" minSPVersion="0.0"/> <Range name="win8" minVersion="6.2.9200.*" maxVersion="6.2.9200.*" minSPVersion="0.0"/> <Range name="win81" minVersion="6.2.9600.*" maxVersion="6.3.9600.*" minSPVersion="0.0"/> <Range name="threshold" minVersion="6.3.9651.*" maxVersion="6.4.9999.*" minSPVersion="0.0"/> <Range name="win10_rs1" minVersion="10.0.9868.*" maxVersion="10.0.14393.*" minSPVersion="0.0"/> <Range name="win10" minVersion="10.0.9868.*" maxVersion="10.0.65536.*" minSPVersion="0.0"/> </VersionRanges>
out of all of the threads that i have been reading so much of over the last week (i'm new), this is by far the most interesting. thanks, i am trying to compensate here for my lack of understanding, for i am still learning.
Q: Which Windows Defender components does Windows Update update? A: 1. Malware Definitions for Windows-Defender-AM-Default-Definitions-Package 2. Malware Removal Tool for Microsoft-Antimalware-Scan-Interface-Core-Package
17763.1 Windows 10 Professional as Enterprise LTSC amd64 Spoiler Converting 17763.1 Windows 10 Professional as EnterpriseS amd64 xx-XX Mounting image Adding EnterpriseS Removing Professional Adding xx-XX Client language pack Current Edition : EnterpriseS Removing Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~11.0.17763.1 Removing Microsoft-Windows-QuickAssist-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Removing Microsoft-Windows-WinSATMediaFiles-Package~31bf3856ad364e35~amd64~~10.0.17763.1 Removing Microsoft.GetHelp_10.1706.10441.0_neutral_~_8wekyb3d8bbwe Removing Microsoft.Getstarted_6.13.11581.0_neutral_~_8wekyb3d8bbwe Removing Microsoft.WindowsFeedbackHub_2018.822.2.0_neutral_~_8wekyb3d8bbwe Resetting base Unmounting image 17763.1 EnterpriseS in Professional style amd64 xx-XX has been created successfully WIM Information: ------------------------------------- NAME="Windows 10 Enterprise LTSC 2019" DESCRIPTION="Windows 10 Enterprise LTSC 2019" FLAGS="EnterpriseS" DISPLAYNAME="Windows 10 Enterprise LTSC" DISPLAYDESCRIPTION="Windows 10 Enterprise LTSC" ------------------------------------- Press any key to continue . . .
Q: Why Server won't install on physical device when File Server Role was removed? Fact: For physical device, both Client and Server need Storage service.
ylx must envy you. Hey hey... Ander,,, zhanglin. ME 2. xx_windows_serverdatacenter_workstation_2016_x64_dvd_1234567.iso Code: ================================================================================================== Converting 14393.0 Windows ServerDatacenter to Workstation amd64 xx-XX ================================================================================================== Mounting image Adding ServerDatacenter in ServerWeb structure Removing ServerDatacenter Enabling feature ServerMediaFoundation Enabling feature WirelessNetworking Current Edition : ServerDatacenter Resetting base Unmounting image ================================================================================================== 14393.0 Windows ServerDatacenter Workstation amd64 xx-XX has been successfully created ================================================================================================== WIM Information: -------------------------------------------------------------------------------------------------- NAME="Windows ServerDatacenter Workstation" DESCRIPTION="Windows ServerDatacenter Workstation" FLAGS="ServerDatacenter_Workstation" DISPLAYNAME="Windows ServerDatacenter Workstation" DISPLAYDESCRIPTION="Windows ServerDatacenter Workstation" -------------------------------------------------------------------------------------------------- Press any key to continue . . .
Do you know any way to rebuild Certificates in C:\Windows\System32\spp\tokens\skus for Product policy? Or Product policy emulator? There are two similar tools: 1. More than 4 GB memory for x86 2. SLIC activator
If only I can add .NET Framework 4.8 to the script... Code: if %V3% equ 14393 ( echo. echo Adding .NET Framework 4.8 mkdir temp\1 >NUL 2>&1 dism /english /quiet /scratchdir:temp /apply-image /imagefile:files\Windows10.0-KB4486129-x64.esd /index:1 /applydir:temp\1 dism /english /quiet /scratchdir:temp /image:%MT% /add-package:temp\1 ) Looking good... Code: ================================================================================================== Converting 14393.0 Windows ServerDatacenter to Workstation amd64 xx-XX ================================================================================================== Mounting image Adding ServerDatacenter in ServerWeb structure Removing ServerDatacenter Current Edition : ServerDatacenter Enabling feature ServerMediaFoundation Enabling feature WirelessNetworking Adding .NET Framework 4.8 Resetting base Unmounting image ================================================================================================== 14393.0 Windows ServerDatacenter Workstation amd64 xx-XX has been successfully created ================================================================================================== WIM Information: -------------------------------------------------------------------------------------------------- NAME="Windows ServerDatacenter Workstation" DESCRIPTION="Windows ServerDatacenter Workstation" FLAGS="ServerDatacenter_Workstation" DISPLAYNAME="Windows ServerDatacenter Workstation" DISPLAYDESCRIPTION="Windows ServerDatacenter Workstation" -------------------------------------------------------------------------------------------------- Press any key to continue . . . Good. Windows Update is updating .NET48.
Fact: Microsoft uses 14393.0 .NET Framwork 4.8 for 14393.0\15063.0. 16299.15 .NET Framwork 4.8 for 16299.15\17134.1\17763.1 Interesting... Q: If Windows 8.1 can use .NET48 (I am not sure because I never touch it), why not 10586 and 10240? Q: If 14393.0 .NET Framwork 4.8 can be used for 15063.0, why not 10586 and 10240? Q: How does Microsoft make 14393.0 applicable to 15063.0?