Following this discussion:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/c5f2786c-ffac-4f14-b7a9-00612cdf784e/server-2016-vm-hangs-shutting-downrestarting-when-the-pagefile-is-on-a-different-vhdx?forum=winserverhyperv

The core problem is the following, for example (simple config), for Exchange or SQL servers in a HYPER-V VM under Windows 2016:

systemdrive for windows system (and sql, exchange core),
datadrive for mbx data or sql-databases
datadrive for log file
drive for pagefile

We create for all this drive a separat VHDX file and add this to the VM as SCSI drive.

The drive for pagefile (fast SSD, NVMe or other) is exclusiv for the pagefile reserved. No other data on it. The drive for pagefile is the only drive with a pagefile for this vm. No second pagefile on the systemdrive or elsewhere.
In this case a running VM can't restart or shutdown.
When you do this, the VM hangs. This did not happen with earlier versions of Windows.
It is not recommended (MS Exchange or SQL recommendations) to set up two Pagefiles (split pagefiles), as this greatly reduces performance.

So we must disable the debug funktion completely in the Windows VM - that works. But not a good way.

Please rerelease the functionality as in previous windows versions!

Windows Server 2016: Powershell Imports Appear Broken

Version:
Major Minor Build Revision
----- ----- ----- --------
5 1 14393 2339
Error:
Error: The term 'function' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was includ
ed, verify that the path is correct and try again.

Summary:
Last night, an update was implemented on our system via active directory. Today, I am unable to run file imports that work on other versions (5.1.16299.431 is working fine on my local machine, Windows 10). I'm not 100% sure that this is a bug, but I can't reproduce on other versions and there doesn't appear to be any link I could find to get an upgrade on the OS I'm using. The latest update was KB4284833 run overnight.

Does this look like an end user issue?
Is there a way to upgrade Windows Server 2016 PS to 5.1.16299.431 (working)?

Test Code:
ZipFiles.ps1

Param ($type)

$ScriptDirectory = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent
$date = get-date -UFormat %Y%m%d
$Logfile = "$ScriptDirectory\FileManagement-$date.log"
try {
. ("C:\Program Files (x86)\oneZero\Scripts\SendMail.ps1")
. ("C:\Program Files (x86)\oneZero\Scripts\LogWrite.ps1")
}
catch {
Write-Host "Error while loading supporting PowerShell Scripts"
Write-Host "Error: $($_.Exception.Message)"
exit 1
}
SendMail.ps1

function sendHTMLMail {

Param (
[string]$Body = '',
[string]$Subject = ''
)

$SMTPServer = "smtp.sendgrid.net"
$SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 587)
$SMTPClient.EnableSsl = $false
$SMTPClient.Credentials = New-Object System.Net.NetworkCredential("user", "password");
$EmailFrom = "email"
$EmailTo = "email"
$message = New-Object System.Net.Mail.MailMessage $EmailFrom, $EmailTo
$message.Subject = $Subject
$message.IsBodyHtml = $true
$message.Body = $Body
$SMTPClient.Send($message)
}
LogWrite.ps1

function LogWrite
{
Param (
[string]$logstring,
[string]$logfile)

$date = Get-Date
$log = "$date - $logstring"

if (!(Test-Path $Logfile))
{
New-Item -path $Logfile -type file
Add-content $Logfile -value $log
}
else
{
Add-content $Logfile -value $log
}
}

I've successfully installed Windows Server 2019. I've installed the following Roles: ADDS, DHCP, WDS. Active directory works fine, dhcp work proper. WDS when i try to open the WDS manager will freeze. I've installed in multiple system so it's not a problem with my VMWare Workstation 14. Also i've tried both versions. Standard and Data Center.

Second glitch it's the network settings. When you right click on ethernet icon and try to go to advance option. On the left panel click Ethernet and first option it's to change Adapter option. You will get an error which said that you don't have enough rights to do that. I've created a new user with Domain Admin, Enterprise Admin, Administrators groups yet no success. So the single way to change the ip address on the adapter you have to go to advance option and get back into the ethernet icon.

IIS services will not detect your website if you haven't created before the A record or CN in DNS. So you have to create it it first in DNS the name of the record.

Sometimes the dashboard will not close just hang in there. I assigned to my Server 16 Cores and 12 GB of RAM so i don't think it's a problem with my spec.

After installation of AD DS and automatically restart will occur when the Windows it's loading back it's take at least 10 minute to set up the new settings of AD DS.

Hope this will help in solving this Issues

I am a microsoft trainer for about 8 years so i think its important for you to hear my suggestions about windows server 2016 (the latest update).
Win server 2016 has so many bugs and you are losing your customers.
Everyone tells me that master please dont tell me about winserver 2016 any more its not reliable and has so many issues.
So if you as microsoft server team want to know about all of the problems please send me an email so i will tell you all about the problems that im sure you dont know aboute all of them.
Thaks
Mahyar safaei

If a Powershell script creates a DFSR RG and invokes the CmdLet "Set-DfsrMembership" multiple times to add several member servers then there is a high probability that the CmdLet will fail.
I have a PowerShell script than creates a new DFSR RG, adds the local server and a folder, then calls the above CmdLet.
if the script is run in a loop (deleting the RG between iterations) then the script will fail after 2 - 5 loops.

I've used .NET Reflector to debug the DfsrPowershell, DfsObjectModel and DfsrHelper DLL's and I found that the error is as follows:
Set-DfsrManagement attempts to modify the Replication Group object under the target computer in Active Directory. It first attempts to perform the operation using the currently logged on user's credential and when that fails it retries using using the target computer account. This normally succeeds however, when it does fail the LDAP response is invalidAttributeSyntax
Examining the modifyRequest command I see one of the attributes is:
modification item operation: delete (1)
modification msDFSR-DfsLinkTarget
type: msDFSR-DfsLinkTarget
vals: 1 item
AttributeValue:
And the AttributeValue is empty - which is invalid!
Now the modifyRequest that was sent using the logged on user's credentials is correct:
modification msDFSR-DfsLinkTarget
type: msDFSR-DfsLinkTarget
vals: 0 items
The difference is the first modifyCommand is built and sent by the DfsObjectModel DLL while the failing command is sent by the DfsHelper DLL which is native code and described in the MS-DSFRH document.
I have debugged the code as far as the interface into DfsrHelper and confirmed that the attributes passed into the DLL are correct i.e. the msDFSR-DfsLinkTarget attribute operation is "delete" and there are no values set. Therefore I am of the opinion that there is a defect in the DfsrHelper DLL implementation that incorrectly appends an empty value when constructing the LDAP command.
I opened a MSDN case with the breakfix group who confirmed it was a bug but were unable (due to internal policy??) to submit their findings to the DFSR dev team.

In a certain powershell script i'm working on i get the following error when i try and debug:

E:\logs\Invoke-IISGraphInteractive_V1_4.ps1 :
Exception : System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: length
at Microsoft.VisualStudio.Text.Span..ctor(Int32 start, Int32 length)
at Microsoft.PowerShell.Host.ISE.ISEEditor.MarkPosition(Int32 lineNumber, Int32 startPosition, Int32
endPosition, String marking)
at Microsoft.PowerShell.Host.ISE.ISEFile.SetDebuggerCurrentPosition(Int32 lineNumber, Int32
startColumn, Int32 endColumn)
at Microsoft.PowerShell.Host.ISE.PowerShellTab.DoEnterDebugger()
at Microsoft.PowerShell.Host.ISE.PowerShellTab.DoEnterNestedPrompt(Object context)
at
Microsoft.Windows.PowerShell.Gui.Internal.WPFHelper.<>c__DisplayClass9.<SendToUIThread>b__8(Object obj)
TargetObject :
CategoryInfo : OperationStopped: (:) [Write-IISResponseCharts], ArgumentOutOfRangeException
FullyQualifiedErrorId : System.ArgumentOutOfRangeException,Write-IISResponseCharts

here is the code block:

$DataToUse = $data.data |Where {$_['time']}| where $CoreFilterSB | where $FilterSB
$TransformedData = $DataToUse |
select @{n='Series';e={Invoke-Command $seriesSB -ArgumentList $_}},
@{n='Time-taken';e={
[int]$TimeSec = [Math]::Round(([double]($_['time-taken'])/1000.),0)
if ($HistogramLogScale)
{
if ($TimeSec -eq 0)
{
0
}
else
{
#round down the call time as a log base 2, then re-raise so get original scale but bucket by powers of 2
#e.g. 0.5,3,5,6,8 --> 1,4,8
([math]::Pow(2,[math]::Floor([math]::Log($TimeSec,2))))
}
} else {
$TimeSec
}
}}
$DataArray = $TransformedData |
Group-Object Series,Time-Taken |
select @{n='Series';e={$_.Group.Series | select -first 1}},
@{n='time-taken';e={$_.Group.'time-taken' | select -first 1}},
@{n='Count';e={$_.Group.Count}} | Sort Series,'time-taken'

it crashes when i put the break point on $TransformedData = ... line

Name Value
---- -----
PSVersion 4.0
WSManStackVersion 3.0
SerializationVersion 1.1.0.1
CLRVersion 4.0.30319.42000
BuildVersion 6.3.9600.18773
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0}
PSRemotingProtocolVersion 2.2

Hello, after applying the below listed patches this past Sunday on Windows Server 2016 dedicated to File / Print services, searching for files on Windows Server 2016 results in the search that appears to be searching but unable to display properly.

If possible I'll send a picture comparing Windows Explorer search results from both Win10 & Win7 (both systems are up to date with latest patches, though the same view from Win 10 happens on Win 2016), a description of what I'm seeing can be described as follows:

Win 10 / 2016; you see the file name only, the rest of the search area is blank (normally it shows content and meta-data) and unlike before, right click doesn't bring up any menu options (such as opening the folder the file is saved in);
Win 7; you see blank lines, as if the fonts were white on white background, so it appears to bringing up similar results as the Win 10, but you only see the light grey line separating each search result;
Running the same search from both client machines on a Windows 2008 older file server (is also up to date on patches) shows the expected results (File name, content below file name, Meta data on the right), which is what I was seeing last week on the Win 2016 server / before applying the patches.
Look forward to feedback and confirmation if there's something else that needs to be enabled on the 2016 file print server.

Thank you,

Updates Applied on Sunday, March 4th:

Update for Windows Defender antimalware platform - KB4052623 (Version 4.12.17007.18022)
2018-02 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4074590).
Windows Malicious Software Removal Tool x64 - February 2018 (KB890830)