# FACET4 WINDOWS 10/11
-
51 |
- Description 52 |
- Before you run! 53 |
- Liability 54 |
- Execution 55 |
- Interactivity 56 |
- Compatibility 57 |
- Known side effects 58 |
- Known issues 59 |
- Undo changes 60 |
- Final considerations 61 |
- Thanks To 62 |
Description
65 |2024: Another latency-reducing, debloating, Windows-ruining script with thousands of registry tweaks, zero solid foundation, and absolutely no studies (like ANOVA) to prove you’re doing better than the actual OS developers themselves.”
67 |“Reckless”? Nah… I’m just more into studying and removing junk and noise than chasing the “magic registry key” that’ll supposedly turn your system into something mind-blowing. Come on, give me a break!
70 |71 |
Introduction:
72 |The PowerShell script presented here automates routine tasks on Windows 10 and 11 distributions (24H2 compatible), specifically focusing on improving performance and reducing overall latency for devices with limited CPU and RAM resources. While the script does not target IT administrators or serve as an "anti-tracking" solution, it aims to balance maintaining desired functionality and optimising system performance.
Approach and Scope:
74 |Unlike conventional "debloatware" scripts available on the web, this comprehensive script encompasses various elements beyond removing unnecessary features. Acknowledging that such deletions can lighten the system, my approach combines different methodologies and best practices to explore specific areas that warrant further optimisation.
It is crucial to recognise the complexity and quality of the operating system developed by Microsoft and its collaborators. Attempting further optimisation without compromising essential functionality would be audacious. Therefore, my script identifies areas where functionality can be optimised to gain performance while retaining the system’s overall characteristics and ensuring broad compatibility.
76 |Respecting Official Distributions:
77 |My philosophy does not endorse creating a barebones and featureless system through code. Suspicious distributions like "ATLAS" or "TINY 11" are not recommended, despite acknowledging the developers’ efforts. Instead, I emphasise relying on official distributions designed to meet most users’ requirements.
Challenges and Best Practices:
79 |While tools like "NTlite" can help test scripts for optimisation purposes, I must approach this task with the utmost respect for the system’s developers and a deep understanding of its nuances. Disabling features or altering kernel behaviour without comprehensive knowledge can lead to adverse effects. Thoroughly filtering through official documentation, addressing misconceptions, and distinguishing signal from noise can be time-consuming, yet essential.
Windows Services Optimisation:
81 |Based on my experience, extensive optimisation of Windows Services proved to be a fruitless endeavour. Accepting the system as it is maybe the wiser choice for most scenarios. However, individuals seeking further customisation may explore options involving low-level programming languages and kernel customisations.
82 |Fresh installation of Windows LTSC 21H2 with all drivers and updates installed after applying this script :
85 |CPU:
86 |
Memory:
93 |
Before you run!
103 |☝ Although the author has made an effort to provide broad compatibility,
104 | this script was conceived aiming at a clean install of Windows,
105 | and if you use it outside that context, some programs may stop working.
106 | Be aware of the risk.🚫 Do not run this script if you are not familiar with the topic.
108 | Some functions may reduce security, uninstall or prevent applications from running again and disable
109 | some internal operating system functionalities. If you don't understand what a function does, don't run it.🚫 Never run scripts from strangers without checking the code first!
111 | Research indicates that a significant 76% of ransomware attacks originate from PowerShell scripts.🚫 This script can damage your operating system by forcing a complete reinstallation.
113 | It is at your discretion and risk.Liability
117 |This script has taken dozens of hours and years of experimentation on my part, self-learning, and is being shared freely for use, distribution, and study. I’m not responsible for anything. All script is provided as it is, and you can use it at your own risk.
118 |Execution
121 |The script is divided into a module with all the functions and a preset file containing only the call of the procedures to be executed. Directly running the script.cmd file solves all these complexities for you, such as elevating privileges.
122 |If you just want to run the script with the default preset, download and unpack it and then simply double-click on the script.cmd file and confirm the User Account Control prompt.
Interactivity
132 |This script is designed to run without any user interaction. Modify it as you like.
133 |Presets
135 |The preset file is a simple list of function names which should be called. Any function which is not present or commented in a preset will not be called. Thus the corresponding function will not be applied.
136 |The function name can be prefixed with an exclamation mark !, which will instead cause the function to be removed from the selection. This is useful when you want to apply the whole preset but omit a few specific functions in the current run.
Log
140 |The script automatically stores the output of the script execution in a folder like C:\Temp\facet4 .
System Restore Point
144 |The script automatically tries to create a system restore point before the functions run.
145 |System Restore is a feature designed to create a snapshot of the current working state and save it as a “restore point” when essential changes are detected on your computer. Suppose a critical issue occurs after installing an update, driver, or application or incorrectly modifying system settings in the registry, you can use a restore point to revert your laptop or desktop computer to an earlier state to resolve the issue without losing your files.
146 |Compatibility
150 |The script was developed and tested using the latest Windows 10 and 11 Home and Pro distributions in English and Portuguese languages and aims to be fully compatible with the most up-to-date version of them, you can run the script on other distributions, but the code is still designed primarily for Home/Pro and is not compatible with versions before Windows 10.
151 |-
152 |
-
153 |
-
154 |
155 |
156 |
157 | -
158 |
-
159 |
160 |
161 |
162 |
Known side effects
166 |-
167 |
- Some Windows settings will show the message
Some of these settings are hidden or managed by your organization.This is due to some functions of the script that use Group Policy Objects (GPO). The exact mechanism is used in companies so that users without administrative privileges cannot change the settings. I’m using this because, in theory, it prevents future system updates from reverting these settings without notice. If you would like to make these settings available, disable theDisableAppCompatfunction in the present file before running it.
168 | - The script disables support for legacy 16-bit applications. If you still use any apps from the Jurassic period, disable the
DisableAppCompatfunction in the present file before running it.
169 | - The script disables some functionality of the
Xboxsubsystem. If you use any games from your Xbox account, disable theRemoveXboxFeaturesfunction in the present file before running.
170 | - This script automatically changes the
Processor performance boost modeplan according to the processor brand (AMD/Intel) and computer type (Notebook/Desktop).
171 |
You can easily change this option by accessing the steps below: 1. Open Command Prompt: hold down the Windows Key, and Press R on your keyboard. 2. Type power in the window and press Enter. 3. Click on the Change advanced power settings option and scroll down to the Processor power management tab. The default state is Aggressive . 4. Follow the on-screen options to change and click on the Apply button. It is not necessary to restart the device.
Known issues
182 |When trying to change a specific key when using an Azure Active Directory account.
183 |The problem is easily worked around by performing this modification manually using Regedit.
Undo changes
187 |Reverse the entire script
189 |Based on my “limited” knowledge acquired over the years as a user, I do not believe that reversing function by function will bring your operating system to the previous state with the same behaviour in all its details. I have always witnessed several inconsistencies using this approach in addition to spending many hours trying to solve this.
190 |Based on the above, I find it advisable (which is why this built-in tool exists in Windows) to perform a System Restore Point before executing this script.
191 |To revert the entire script, follow these steps:
192 |-
193 |
- Open Command Prompt
hold down the Windows Key, and Press Ron your keyboard.
194 | - Type
rstrui.exein the window, and then press Enter.
195 | - Find a restore point with a name like
System Restore Point dated 00/00/0000 00:00:00 before running facet4 script. It should be the newest restore point there.
196 | - Follow the on-screen instructions to complete the system restore. 197 |
Revert functions
201 |To undo the effects of a specific function, you can write and add a complementary function that restores the original behavior and append it to the current file.
202 |The code at the end of each instruction contains the default values for Windows 11 22H2 and Windows 10 LTSC 21H2 distributions.
203 |You are welcome to experiment and modify the functions as you wish.
204 |Final considerations
208 |If you understand what you are doing, consider downloading and running Microsoft Autoruns to check your system.
209 |This utility, which has the most comprehensive knowledge of auto-starting locations of any startup monitor, shows you what programs are configured to run during system bootup or login, and when you start various built-in Windows applications like Internet Explorer, Explorer and media players. These programs and drivers include ones in your startup folder, Run, RunOnce, and other Registry keys. Autoruns reports Explorer shell extensions, toolbars, browser helper objects, Winlogon notifications, auto-start services, and much more. Autoruns goes way beyond other autostart utilities.
210 |https://learn.microsoft.com/en-us/sysinternals/downloads/autoruns
211 |
1.Adjust Memory Command Rate: Explore the BIOS settings for your memory and locate the “Command Rate” or similar settings such as “Nmode.” Change the value from 2T to 1T. This adjustment can lead to a perceptible improved performance.
222 |
3.Enhance GPU Performance: If using a first-rate video card, investigate whether it supports “Above 4G Decoding” or “Resizable BAR.” If compatible, research the process to enable this feature on your motherboard. It enhances graphics performance a lot.
234 |
4.Explore RAID Configuration: For users with an AMD Ryzen platform, it’s worth exploring the possibility of utilizing RAID 0 for SATA or NVMe devices. Even notebooks with locked BIOS and two NVMe ports might support this unofficially. Search how to implement this configuration for improved storage performance. It’s pure luxury, but it is fantastic!
243 | 
5.Enable Message Signaled Interrupts. Be aware that enabling MSI for a driver without support will break your Windows!
252 |
6.And lastly, don’t forget, if it’s a fresh install of the operating system, select “English (World)” as the time zone; it pretty much solves the initial bloatware problem on your new Windows. This does not apply to the LTSC or IoT distros, as it already comes with reduced OS footprint. Credits to mastermind @ThioJoe!
261 |
Thanks To
274 |The thousands of people who actively contribute to forums, websites and communities, making their knowledge available; without this, it would not be possible to waste/spend dozens of hours trying to learn things like this.
275 |I leave my thanks.
276 |