Default servercore:1809 image came with en-US.

- At this moment, for Server Core 2019, you have to install language pack by yourself: https://docs.microsoft.com/pt-br/windows-server/get-started-19/rel-notes-19.
- The way to do it, is using lpksetup: https://support.microsoft.com/en-us/help/4466511/cannot-configure-language-pack-for-windows-server-2019
- But lpksetup.exe crashes when running on container

I've described step by step how to reproduce lpksetup.exe error on container, **producing crash report logs** that I've extracted from container.
All here: https://github.com/sanguedemonstro/docker-playground/issues/1#issuecomment-453078549

With extra details here: https://github.com/sanguedemonstro/docker-playground/blob/master/langpack-on-servercore2019.md#why-am-i-playing-around-this-subject

But I'm not able to understand logs or fix windows base image. And I can't open support ticket once I'm not MS partner.

So if anyone could help I'm here to support.

Thanks!

It would appears I'm not the only one experiencing the issue, I did a fresh install promote it to a Windows Server 2016 Forest and Domain AD. After the reboot I realize the Start Menu settings cannot be changed, next I found that whole load of permission error whenever I try to launch anything that requires Administrator privilege including Server Manager, Settings and Control Panel. After that I went to check the permission settings of the C drive and Windows folder as compared to previous version of Windows Server, "Authenticated Users" is no longer part of the default permissions. This is a fresh install of various edition from VLSC to MSDN to retail to trial download every version media and edition use present the same issue.

If you use Hyper V Live Migration from Server 2012 R2 (not sure if any other OS) to migrate to Server 2019. The migration works but as soon as you shut down the VM and try to start it again, will no longer boot. It turns on/off 3 times and remains off.

I also did cluster to cluster migration in VMM and this is the same behaviour.

It looks like it is due the migrated MAC address, if I set the VM to get a new dynamic mac address it seems to work. If I set it to it's original mac address as a static it will no longer boot.

Hello,

I want to report one issue that is easy to reproduce, it occurs with any rdp client that connects to Windows10 Pro with enabled RDP connections, actually used mstsc.exe to connect from one Windows10 pro machine to another Windows10 pro machine with enabled RDP.

After ~100 tries to restore interrupted connection the server refuses future rdp connection tries with internal error occurred message reported by mstsc.exe.

It doesn't matter if you have logged off the session during running, as example did 20 connection restorings then logged off, logged in and did next 80 connection restorings, that was only example, only what matters is that you have only to restore any interrupted session at least ~100 times to send server to nirvana. As example after WiFi lost connection or during any network problem that requires rdp connection restoring. Only what helps to restore functionality is to restart remote desktop service in services.msc

I highly assume by restoring connection with reconnection cookie the bug counter counts up and by reaching 100 (the counter seems to be not reset by any action) so finally it completely stops to accept any future connections with internal error occurred message.

Such error doesn't exist on Windows2016 but Windows10 pro is affected.

More over few months ago this bug didn't exist on Windows10 too.

Please forward this issue to your RDP server developers, thank you!

Sincerely yours.

Get-AD* Cmdlets broken when using "-Filter *" and & or "-Properties *"
on Windows 10 1809 with Remote Server Administration Tools 1809:

Name : ConsoleHost
Version : 6.1.1
InstanceId : 376bfa55-d7c2-41ad-89dc-bc63b357ccb8
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-US
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace

Get-ADobject -Server $Forest.DomainNamingMaster -Credential $Creds.$ForestKey -LDAPFilter "(objectClass=site)" -SearchBase 'CN=Configuration,DC=contoso,DC=com' -Properties *
Get-ADobject : Object reference not set to an instance of an object.
At line:1 char:1
+ Get-ADobject -Server $Forest.DomainNamingMaster -Credential $Creds.$F ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-ADObject], NullReferenceException
+ FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.NullReferenceException,Microsoft.ActiveDirectory.Management.Commands.GetADObject

Same Windows 10 1809 system results with PoewrShell v.5.1.1.x

Get-ADobject -Server $Forest.DomainNamingMaster -Credential $Creds.$ForestKey -LDAPFilter "(
objectClass=site)" -SearchBase 'CN=Configuration,DC=contoso,DC=com' -Properties * | FT DisplayName,WhenCreated -AutoSize

DisplayName WhenCreated
----------- -----------
5/13/2002 12:27:06 PM
3/6/2002 10:40:48 AM
11/19/2004 9:59:25 AM
7/12/2002 3:51:37 PM
...

*NOTE: Format-Table pipeline intentionally excluded under PowerShell Core 6.1.1.x example for clarity. DisplyName & Whencreated attributes used in PowerShell 5.1.1.x to protect live system data.

Today (1/22 PST), Microsoft released two preview udpates for RS5 - KB4476976 and KB4481031. Thease updates are D release. But Preview of Cumulative Update for .NET Framework (KB4481031) was automatically installed to some Windows 10 ver 1809 and Windows Server 2019. This behavior is not assumed. I did not click "Check for updates". KB4481031 says

"Install this update
To download and install this update, go to Settings > Update & Security > Windows Update and select Check for updates.
This update will be downloaded and installed automatically from Windows Update. To get the standalone package for this update, go to the Microsoft Update Catalog website." (https://support.microsoft.com/ja-jp/help/4481031/)

Server Core's sconfig also detect KB4481031. (not detect 4476976)

The previous Preview CU for .Net Frameworks (KB4469041) was also the same behavior.

Because there's no "product feedback" at <https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/features-on-demand-v2--capabilities>, I'll post here. I'm the author of a popular Active Server Pages framework, ASP Xtreme Evolution (AXE), and we have a hack to leverage node.js npm packages to work inside our environment <https://github.com/nagaozen/evolved-npm2asp-bundler>.

I evaluated the Windows Server 2019 DE and the ServerCore (with FoD) on a virtual machine and they both support this trick. But we are trying to move into a container strategy and installing FoD on the <mcr.microsoft.com/windows/servercore:ltsc2019> seems impossible for the reasons already explained in this issue <https://github.com/MicrosoftDocs/windows-insider/issues/56>.

I'm sending an attachment with coverage tests to help evaluating the server.

[tests.zip](https://github.com/MicrosoftDocs/windows-insider/files/2966573/tests.zip)