/W10-Optimize-and-Harden

Optimize, Harden, and Debloat Windows 10 Deployments to Windows Best Practices and DoD STIG/SRG Requirements. The ultimate Windows 10 security and privacy script!

Primary LanguageHTML

Optimize, Harden, and Debloat Windows 10 Deployments

Download all the required files from the GitHub Repository

We are seeking help with the following .Net issue

Introduction:

Windows 10 is an invasive and insecure operating system out of the box. Organizations like PrivacyTools.io, Microsoft, Cyber.mil, the Department of Defense, and the National Security Agency have recommended configuration changes to lockdown, harden, and secure the operating system. These changes cover a wide range of mitigations including blocking telemetry, macros, removing bloatware, and preventing many physical attacks on a system.

Notes:

This script is designed for operation in both Commercial and Personal Use environments. With that in mind, certain settings are not implemented. This script is not designed to bring a system to 100% compliance. Rather it should be used as a stepping stone to complete most, if not all, the configuration changes that can be scripted while skipping past issues like branding and banners where those should not be implemented even in a hardened personal use environment.

This script is designed in such a way that the optimizations, unlike some other scripts, will not break core windows functionality.

  • Features like Windows Update, Windows Defender, the Windows Store, and Cortona have been restricted, but are not in a disfunctional state like most other Windows 10 Privacy scripts.

If you seek a minimized script targeted only to commercial environments, please see this GitHub Repository

Requirements:

Recommended reading material:

A list of scripts and tools this collection utilizes:

Additional configurations were considered from:

STIGS/SRGs Applied:

How to run the script

The script may be launched from the extracted GitHub download like this:

.\W10-Optimize-and-Harden-master\optimize-standalone.ps1

The script we will be using must be launched from the directory containing all the other files from the GitHub Repository