Windows 10 hangs on Black Screen when logging in


 Windows 10 hangs on Black Screen when logging in. This normally happends on a normal domain account (but can be any account).


 Windows 10 Bug


If on Black screen, press CTRL + ALT + DEL and log out

Sign in with a local admin account

Run Services.msc

Right click App Rediness > Properties

Set startup type to disabled.

Reboot machine and log into effected user.

Once logged in Install all windows updates as this issue was resolved in an anniversary updatre.

Reference, Links and Images 


Which switches to use for ROBOCOPY

robocopy "D:\source_folder" "D:\dest_folder" /e /r:5 /w:10 /COPY:DATSOU /LOG:C:\Copyresults.txt


robocopy "\\servername\sharename" "E:\Data Folder\Target Folder" /MIR /W:10 /R:1 /LOG:E:\ROBOCOPY\Copyresults.txt



Copies subdirectories. Note that this option includes empty directories.


Specifies the number of retries on failed copies.


Specifies the file properties to be copied. The following are the valid values for this option:
D Data
A Attributes
T Time stamps
S NTFS access control list (ACL)
O Owner information
U Auditing information
The default value for CopyFlags is DAT (data, attributes, and time stamps).


Writes the status output to the log file (overwrites the existing log file).

WSUS Crashing - WSUSPOOL Stopping in IIS


 WSUS MMC Crashes and WSUS Generally unreliable.


 Application Pool "WSUSPool" Stopped in IIS


To improve WSUS availability, you need to increase IIS Private Memory Limit. The default limit is set to 1843200KB. And when an IIS worker process uses more than 2GB WSUS crashes and the problem occurs.

Change Private Memory Limit (KB) to a higher number that fits your server specifications or simply 0 , which means no limit, instead of the hard-coded 1843200. Follow this path to find the setting:


WSUS Application Pool IIS Advanced Settings

Internet Information Services (IIS) Manager → Server → Application Pools → Select “WSUSPool” → Actions Advanced → Recycling → change “Private Memory Limit (KB)“.

This’ll improve WSUS availability.

Outlook 2016 (365) connects directly to Office 365 and ignores AutoDiscover or On Premise Exchange


 If you have a user with Outlook 2016 who are not yet in Office 365 but have mailboxes provisioned in Office 365 you may find Outlook automatically connects to Office 365 and ignores Auto Discover or the on premise Exchange server.


 Starting in Outlook 2016 version 16.0.6741.2017, Microsoft enabled a new feature called Direct Connect to Office 365.  It was designed to quickly connect Outlook 2016 to Office 365.


 A registry key can be added on the PC which will disable the Direct Connect feature and allow either Auto Discover or the On Premise Exchange to configure Outlook.

  1. Go to Registry Edit on the PC. REGEDIT.MSC
  2. Go to the following path: HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover  (I had to create the AutoDiscover Key)
  3. Create a DWORD: "ExcludeExplicitO365Endpoint" to Value : 1

List of common ports

This is not a full list of ports, just a list of common ports to scan when looking to see what ports may be open to avoid having to scann every single port.