(Since you cannot run slmgr /rilc, I have a question.) Speaking of cululative update, how did you get it? Thru Windows Update, or inatalled manually? (I get it thru Windows Update.)
slmgr /rilc did run, but it didn't change, Read the Microsoft Software License Terms in Control Panel\System and Security\System. windows10.0-kb3176495-x64 Windows Update. windows10.0-kb3176931-x64 Manually.
No server components/packages are more featurized in client, only two packages have visible features that can be disabled - Founation-Package, which holds the normal optional features - the edition product package (i.e. Microsoft-Windows-ProfessionalEdition), which usually have: Spoiler Code: Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Features listing for package : Microsoft-Windows-ProfessionalEdition~31bf3856ad364e35~x86~~10.0.14393.0 ----------------------------------------------------- | ------- Feature Name | State ----------------------------------------------------- | ------- Microsoft-Hyper-V-ClientEdition-Package | Enabled Microsoft-Hyper-V-Common-Drivers-Package | Enabled Microsoft-Hyper-V-Guest-Integration-Drivers-Package | Enabled Microsoft-Windows-NetFx3-OC-Package | Enabled Microsoft-Windows-NetFx4-US-OC-Package | Enabled Microsoft-Windows-NetFx3-WCF-OC-Package | Enabled Microsoft-Windows-NetFx4-WCF-US-OC-Package | Enabled Microsoft-Windows-NetFx-VCRedist-Package | Enabled Microsoft-Windows-Printing-PrintToPDFServices-Package | Enabled Microsoft-Windows-Printing-XPSServices-Package | Enabled Microsoft-Windows-Client-EmbeddedExp-Package | Enabled
Is there any news (or already a reliable date) about when Windows Server 2016 Essentials will be available?
Forget the leak ... Are you saying I can't have lunch until the end of September? I know I need to diet but come on that can't be healthy.
The mui file that cause ServerManager to function abnormally is Microsoft.Windows.ServerManager.Common.resources.dll in C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.Windows.FileServer.Management.Common.resources\v4.0_10.0.0.0_xx-XX_31bf3856ad364e35
To be pedantic, this isn't a mui, this is a resource dll which doesn't pair perfectly with the older related mui from 14300
To be clear there are two files involved in that specific problem Microsoft.Windows.ServerManager.Common.resources.dll and Microsoft.Windows.ServerManager.Common.resources.dll.mui The former is a normal resource file (it may contain not translatable strings, icons, backgrounds and whatever a program needs) The second is an extension of the former which includes the translations only (MUIs are just renamed dlls). If the former has mismatched references to the latter the program may crash. Clearly there was a change happened between 14300 and 14393 that mismateched part of the resources. Hence you have to choices, delete the mui and keep the server manager in english until the official mui will be released Or replace the parent resource to match the older mui There is a third option, use a resource editor and translate the en-US mui yourself, something I don't mind to do, but that's just matter of patience rather han skills
normally on servers you need to install Desktop Experience (server manager - features) for that, and login images and themes.