First of all, sorry my poor English. Recently my customer bought two Windows Server 2016 Standard and I have a general group policy to disable autoplay and autorun in all computers in this network. Of course, I have an Active Directory implemented with two DCs, one with W2K8R2 and another with W2K12R2. I´ve downloaded the new ADMX files for Windows Server 2016 and Windows 10 "www.microsoft.com/en-us/download/details.aspx?id=53430" and created a Central Store and I made all steps recomended by Microsoft. This Group Policy works well in all versions of Windows 2012/8.1 and below, but doesn´t work in Windows version 2016/10. I reaserched in the Internet for a similiar problem and I didn´t find anything about this. Does anybody have a clue for this problem??? Thanks for any help.

Cross-posted from Technet forums:

I think we've identified a bug in Server 2016. Long story short:
1. Open lusrmgr.msc
2. Set an active users' properties to require password change at next logon
3. Reboot (or just logout, haven't tried that)
4. Press Ctrl+Alt+Del to logon, enter user's current password
5. Press Cancel when informed you need to change your password
6. Press Ctrl+Alt+Del again, enter user's current password, proceed 7. with password change (notice username is blank at this point)
8. Password gets changed but you are returned to the change password screen with no way to go back or proceed
9. Forced reboot appears to be the only way out but you can logon normally after this

We discovered this when running through the sysprep process and had bypassed the standard OOBE set password screen. Windows Server still wants the password set at first logon so we end up setting the password in the standard password change method instead of via OOBE. I realized this wasn't just a problem with our OOBE process though because just checking the box in user properties will make it happen. Tested this on the built-in Administrator account and a standard account I created after the fact.

Obviously most people won't hit the cancel button here, but we did it just playing around and discovered this.

A hotfix was created by Microsoft to prevent further leaked redirected printers from accumulating in the registry. https://support.microsoft.com/en-us/kb/2620656
Unfortunately, according to the script provided in that KB article the hotfix only deals with the redirected printers that have "session" in the name. The issue is that Microsoft changed this a long time ago to now have "redirected" in the name instead as well as the format of the name being different.
This means that the redirected printers with the new name format are still being leaked in the registry causing the same issue. Note that this is also proven simply by reviewing the affected registry keys after logging in and out a few times.
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts

Note that although the KB article applies to Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008, it still happens in Windows Server 2012 and Windows Server 2012 R2 and likely also in Windows 8 through Windows 10.

Please stop the leaked printer names to eliminate the problem with many software products out there.

Thank you.

Repro 1:
1) browse around the file system or any zip files, double click on any .txt files you find to read them.
2) Click 'X' in the top right of notepad to close out of notepad.

Repro 2:
1) open explorer and click on "Documents" in the treeview to show your documents (and a folder you should definitely have permissions to).
2) In the area showing your folders and files, right click and choose to create a new text document. (I named it test.txt)
3) Double click the new text file and add some text. (I wrote "hello")
4) Select 'File' -> 'Save'
5) Click the 'X' at the top right of Notepad or, Select 'File' -> 'Exit' to close it.

Result:
Notepad crashes.

Details:
Unhandled exception at 0x.... (ntdll.dll) in notepad.exe 0x... "Access violation reading location 0x0000000000000000"

Expected:
No crashing bugs.

Environment:
Clean Win Server 2016 TP5 - Build 14300.rs1_release_svc.160324-1723
the machine is joined to an AD domain.
user is logged on with a domain account.