On the other hand,
Does anyone have any Tweaks that they performed themselves ? it would be great to hear about how it worked for you here.
Since you asked, I have been running Win10 Pro OEM on Display PC for a few months now. My Win 10 is updated up to v1607 (Anniversary Update), and disconnected from the net since. However, my laptop's Win 10 is up to date with all updates as of today, used as a Prodn PC and have not had much problems except one, mentioned below.
Win 10 as Prodn PC
This is a laptop using the free upgrade from Win 7. Version is Win 10 Home Single Language 64-bit with all auto updates as Microsoft sees fit.
No problems with Watchout 6.1.x and the 6.1.2 beta 16 except in Remote Access of another Win 10 Pro Display PC. Needs to 're-launch' Watchpoint via the remote access after accessing otherwise Watchpoint runs but with a black screen(s). A re-launch solves the problem. This does not happen with remote accessing Win 7 Pro Display PCs.
Win 10 Pro OEM as a Display PC v1607
Basic PC specs: ASRock Z270M Pro4 with i7-7700 (I screwed up the K version trying to manually de-lid it), 128GB PNY SSD for OS, 512GB Samsung SM951 M.2 on PCIe Adapter for Watchpoint data, Firepro W4100, Noctua NH-L12 Air Cooling with single fan, 450w SFX power supply, all in a 19" 2U chassis.
Surprisingly, very little tweaking of Win 10 is required to operate it as a Display PC if you do not mind the multitude of apps that comes with the OS. One could of course run through the Start Menu, right-click on any app you do not want or do not intend to use, and if allowed, delete/uninstall it. Some apps do not allow un-installation, but I have not had a problem with them being present in the PC maybe because the Display PC has never been online since initial install and updates (before Creator's Updates).
Standard stuff to disable, of course, are the Firewall and Auto Update of OS, and manual setting of IPV4 Address.
Windows Defender can be disabled, but it will enable itself later or after a re-start. I understand, there is a procedure via Command Prompt as Admin to disable it but I did not venture that way, and let Defender run to see if it interferes. I did set Defender not to run in real time though. So far no problems, no interference with Watchpoint running, over an hour long test show/loop more than once.
For initial installation from a CD, I performed the following actions -
1. Choose Customise setup (not Express Settings)
2. Turn off all :
- Connectivity and error reporting
- Browser, protection and update (especially Smartscreen)
3. When Cortana pops up, answer 'Not now'
4. Thereafter, proceed as normal/auto.
Note: Steps 2 and 3 above can be done after install one by one, but doing it here is easier.
Edit 1: forgot to add that in multi-monitor mode, the Task Bar by default appears on all displays. You can set it to Monitor 1 only in the multi-monitor settings.
Edit 2: Win 10 boots up really fast, IMO, at least 3 times faster than Win 7 even with the disparity between an i7-7700 (Win 10), and an i7-6800K (Win 7). I notice this with my laptop too, an i5. And network connectivity seems to have gone to the top of the boot process in priority versus Win 7. However, I have not checked out how this affects the amount of delay to startup Watchpoint in an autostart situation.