This is a BUG
Why when attempting to launch desktop icons from settings do I get a rundll32.exe error 'Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item'
EH WHAT? Fix your bugs and test your software

robocopy needs to be able to refresh folder attributes.

It appears that if I change attribute settings on the source folders, it is not reflected on the destination folders if I run updates in Robocopy.

Settings is OK on the first run, but it will not update on subsequent runs.

Options : *.* /S /E /DCOPY:DAT /COPY:DATSO /SECFIX /PURGE /MIR /ZB /MT:128 /R:10 /W:30

If the option "Network Connections -> Ethernet ?? -> Properties -> ipv4 -> advanced -> dns -> register this connection's address with dns" is disabled , then a DC will fail to recreate the _msdcs delegated domain. This option would appear to be responsible for the first CNAME entry in _msdcs , if that is missing then _msdcs will not be reconstructed. And might have been responsible for deleteing it in the first place

Server 2016 replication worked to secondary server. Now, both machines are upgraded to 2019. Replication works for hours and then fails. Requires restart of machine (and killing VM tasks as they won't shutdown gracefully) to get replication working again only to have it fail again.

You create an SMB Bandwidth limit using the "Set-SMBBandwidthLimit" cmdlet.

You then attempt to remove the previously created SMB Bandwidth Limit using the "Remove-SMBBandwidthLimit" cmdlet.

The machine will then immediately blue screen with Bugcheck 0x0000003b. Analyising the memory dump that is generated presents the following:

PRIMARY_PROBLEM_CLASS: 0x3B_SmbBandwidthLimitFilter!SchedDispatchDeviceControl

Tested on Server 2016 Standard and Datacenter 1607 (14393.2791) - February Cumulative Update.

See here for original Technet Forum post: https://social.technet.microsoft.com/Forums/en-US/4283c98e-4326-4a99-ac73-5357d9c60909/removing-smb-bandwidth-limits-results-in-bsod?forum=ws2016

Matt Hibberd

In enter - pssession to Windows Server Insider Preview 18334, when get - windowsfeature is executed, the following message appears.
-----
Remote host method get_WindowSize is not implemented.
     + CategoryInfo: ResourceUnavailable: (:) [out-lineoutput], PSRemotingDataStructureException
     + FullyQualifiedErrorId: System.Management.Automation.Remoting.PSRemotingDataStructureException, Microsoft.PowerShell.Commands.OutLineOutputCommand
-----
Although the installation itself has been successful, the install-Windows feature-name "Data-Center-Bridging", "Failover-Clustering", "Hyper-V", "RSAT-Clustering-PowerShell", "Hyper-V-PowerShell" "FS-Data-Deduplication" -IncludeManagementTools
The same message is also displayed in the execution.

There is no problem for get-windowsfeature running locally in Windows Server Insider Preview 18334.

I create a task that monitor Eventlogentries by EventID.
I create 4 triggers listen to 4 different eventIDs (AD Group created, alterted, deleted) but only on action to start a powershell script.

Each time one event occurs (only one evententry) the action will be performend 4 times

I dual boot VMware and Hypervisor enabled versions of the OS and deleted a checkpoint while the hypervisor service wasn't running. The disk therefore did not merge, and when I rebooted with the hypervisor there was an id mismatch for some reason. Please prevent the deletion or atleast create a notification to confirm informing the disk merge won't occur while the hypervisor isn't running.

We’ve had a nightmare experience with Storage Spaces Direct on 2016, on brand new HPE Gen 10 kit. We have a detailed account we can share.

There is no way to keep ARM64 and Itanium updates out of WSUS because one can only choose between x86 and x64 updates but there is no limitation to other architectures that do not belong to classic Intel or AMD64 architectures just like Itanium and ARM64. These should be filtered in WSUS as a seperate category.

Just make it work

Under 2019, the Hyper-V management service stops listening (Server was upgraded from 2016). Shutting down the service hangs.

Hyper-V was stable under 2016.

I have installed WS2016 with PL region, OS in English. I wanted to switch to all English - when trying to change the locale in Region, got this message: SystemSettingsAdminFlows.exe : Windows cannot access the specified device, path, or file. You may not have appropriate permissions

Unable to change WINS Server, IP Binding in Windows Server 2016. In the MMC of WINS Server, you can see an IP Address which suggests that the WINS Service is only listing on this Network Adapter. Even you change the Network Adapter metric, the IP will be not changed in the WINS MMC Gui. It's only changing, if you disable the used interface. With a netstate you can see that the WINS Service is listening on all Interfaces. This is confusing

When restoring another state (and discarding the current state) the machine "Saves" the current memory to the disk first, and then discards what it saved.

This started with Server 2016.

To reproduce the issue restore a previous machine state and discard the current state ... "saving" will come up before it restores the selected state.

This is silly and adds quite a lot of overhead (when dealing with ~200GB in memory), to the point that it is quicker for me to turn off the machine first, restore the state, then start the VM.

The powershell add-ipamaddress cmdlet takes a number of parameters related to dhcp/dns, such as dhcp server, dns zones, etc... but does not sync this information to dhcp or dns.

The cmdlet is mostly useless without the ability to register this info automatically.