Working with Windows Server 2016 on a PC has been a solid process.
Working with Windows Server 2016 on a PC has been a solid process.
I'm a college student who recently assembled a Ryzen 7 gaming PC for entertainment and a Microsoft Surface Pro 4 for study. As is common knowledge, Windows 10 isn't as reliable or secure as older versions: unexpected shutdowns can disrupt your tasks, odd issues pop up after updates, and Microsoft collects user data unnoticed. However, if you opt for a system built after Kaby Lake, you're left with no choice but to use Windows 10. Technically, you can install any Windows version using DISM, but it won't get updates. I was looking for a stable OS that doesn’t track your information. After some research, I discovered Windows Server 2016 fits the bill: built on Windows 10, with no app store or data collection concerns, and offering solid stability. A quick online search shows most applications run smoothly on Windows 10 but not necessarily on Windows Server 2016 (except a few exceptions). With a bit of tweaking, Windows Server 2016 can function well as a desktop environment—far less demanding than previous releases. I installed it on both my Ryzen machine and Surface Pro; the former performed flawlessly, while the latter had minor quirks. Here’s a summary of my steps:
1. Acquire a Windows Server 2016 copy—free options are available for students via Microsoft Imagine.
2. Set up the system with simplified settings: use Administrator account, disable unnecessary privileges, and create a dedicated user.
3. Install drivers from reputable sources; ensure the SATA controller driver is updated.
4. Adjust advanced system settings for performance and visuals.
5. Configure audio and security options in Control Panel and Internet Explorer.
6. Disable IE Enhanced Security and adjust browser settings.
7. Turn off Protected Mode in Internet Options.
8. Add required services via Server Manager.
9. Create a new administrator account and adjust permissions.
10. Install necessary programs with admin rights.
11. Temporarily disable the Administrator account after setup.
12. Reboot and log in as the newly created user.
After testing everything, I confirmed it worked for games, office apps, and general use.
4. Set up Windows Server 2016 on your Surface Pro.
Updating an operating system that isn’t Windows 10 on a Surface can be challenging, since the device might fail to boot without an official Windows 10 ISO. A quick fix involves restarting the device into command prompt mode. Be aware this approach carries risks—backup is essential to avoid permanent data loss. If you skip backups, you risk voiding warranty and possibly damaging the hardware. Proceed with caution.
(1) Retrieve the Windows Server 2016 ISO file and transfer the install.wim file onto a USB drive.
(2) If you’re not comfortable using Dism commands, look for user-friendly GUI utilities; I rely on "Dism++". Transfer that tool as well.
(3) In the Surface Pro 4, navigate to Settings > Advanced Startup/ Restart Now.
(4) After rebooting, select "Advanced Options" and then "Command Prompt".
(5) Connect your USB drive containing install.wim and Dism++ (if available).
(6) Execute the Dism command to extract the install.wim file onto the SSD.
(7) Once extraction finishes, power on the computer to run a Windows Server 2016 installation.
(8) Insert the ISO disk and begin the re-installation process.
(9) Search the Microsoft website for Surface-specific drivers.
(10) Follow the setup instructions as described.
This method can theoretically install any Windows version after Vista, though official support ends with Windows Vista. For legacy systems, you may need to locate custom drivers.
If issues arise—everything functions except certain hardware components that don’t communicate properly with Windows Server. Windows Hello is available, but enabling it isn’t straightforward.
Yes, but LTSB releases are difficult to locate and you lack the ability to opt out of all feature updates. You won't receive any updates at all—like an LTSB 2015 version always being 10.0.10240. I dislike those data collection practices, yet I still need a kernel upgrade. Also, obtaining licenses for LTSB versions is tough. Lastly, I have a free Windows Server key, so whatever you say.
They can find updates on MSDN each year. I prefer staying with a stable kernel version that remains secure. I received my 20-seat LTSB2016 key for free, so it’s the same?
Most companies still rely on Server 2012 R2 or Server 2016 as the operating system for their employees, though this is mainly due to licensing challenges with Windows 7/8/10 for virtual desktops, which can be expensive. Using Server editions is generally more affordable, whether for terminal services or full virtual desktop infrastructure.