Windows 10 Setup Script has a new name and is now easier to use
Remember Windows 10 Setup Script? I reviewed the PowerShell script in August 2020; it was designed to be run right after the installation of Windows 10 on a device to adjust more than 250 different settings and features. One of the main issues back then was that everything, meaning code and switches, was integrated into a single script.
Since it was advised to go through the script before running it to customize it to make sure that features that you wanted to use remained enabled, it was problematic as you'd have to identify the switches that did that and ignore the surrounding code.
The developer of the script has renamed Windows 10 Setup Script to Sophia Script. More interesting than the new name is the fact that it is now easier to use as the switches or presets have moved to a new script.
Take a look at the screenshot below; the new preset script lists descriptions for each option and the actual function only, but no code. All you have to do is put a comment symbol in front of any preset that you don't want executed by the script, and remove the comment symbol if it is already in place. Not all functions are executed by default, and it is definitely necessary to go through the list once to customize the functionality accordingly.
While that still means that you have to go through the list of presets before you run the script, it is easier now and less confusing, especially to users who don't use PowerShell or inexperienced when it comes to scripting or coding languages.
To get started, download the latest version of the script from the project's GitHub website. Extract the archive on the local system, and edit the preset file in a text editor or editor that supports PowerShell.
You may run the script then once you have saved it, e.g. by copying it to the new Windows 10 machine right after installation. To do so, open an elevated PowerShell window, change the Execution policy for PowerShell scripts for the current session by running Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process -Force, and then run the script by executing .\Preset.ps1.
The developer published a video on YouTube that shows the script in action:
The script supports Windows 10 version 1903 to 2004 (Home, Pro, Enterprise), and Windows 10 version 1809 (Enterprise) currently.
Now You: do you modify newly installed operating systems? Which tools do you use for that, if any? (via Deskmodder)
Nice articel, And a really nice improvement of a really great product almost perfect.
But personlly I think that I am quit sure I will go anouther way. A 2GB less way!
Wow-what an improvement of your Microsoft o.s. https://m.youtube.com/watch?v=nwkiU6GG-YU
Its called Windows 10 Ameliorated – https://ameliorated.info/
With all due respect, it’s a kind of bullshit and cannot be compared with this module. Just take a look what does it do. LOL. A primitive batch file.
https://git.ameliorated.info/attachments/8bdf2c4c-413b-4155-9379-ee02410464bd
I looked at Ameliorated, and honestly you’re better off just going Linux, bcos it breaks windows. Sure you can use the batch file, but when you have to load another OS to butcher the primary, it’s not worth the hassle dealing with it… no Office, no xbox controller, no MS store for junk like Alienware CC, no DX12…
I’ve been on LTSC, but it’s getting a little too old, so I’m looking for PS scripts to fix windows.
LTSC and GPEdit is all I need <3
Yeah, but what if Microsoft finally discover rounded corners and proper Aero/Blur for all of its interface and they update the newest Windows 10 so it looks less ugly and blocky like an early Alpha placeholder UI as it does now? You’ll be stuck with it looking a swollen monkey’s ass while the latest looks more pleasing to the eyes.
I know looks aren’t everything, but I simply cannot get over how ugly stock Windows 10 looks, I have been trying to get used to it for 5 years already and I still can’t. I’ve tried skinning it, but it still feels sloppy. I really miss the elegant design of Windows 7 and in a way that of Vista, I will Microsoft finally add rounded corners and overall make the UI more beautiful.
And LTSC is the last to get those, and from what I understand LTSC is only useful in big work environments where they need stability and whatnot.
I don’t mind the looks, I actually prefer squared corners over rounded ones, both for software and physical objects.
@ Allwynd
“I really miss the elegant design of Windows 7”.
I know what you mean ..and that’s why I install Classic Shell on most of my clients Windows 10 PCs. Most cannot believe what a difference Classic Shell makes to appearance and ease of use, and most (including myself) wonder if Microsoft has intentionally gone out of its way to create the most user-un-friendly design in Windows 10 (for example, where a right click is required on the Start button to access essential items..which normally -in the past- have been easily visible).
http://www.classicshell.net/
@RobG:
I don’t know that this has caused any real problems on recent Windows 10 builds (yet?), but Classic Shell ceased active development in December 2017. It might be safer to use the actively developed fork Open-Shell instead. Open-Shell’s most recent update was released less than a month ago.
When I moved from Windows 7 to Windows 10 last March, I tried to use Windows 10’s native Start Menu for a good four months, just to see if I could stand it. I *couldn’t*, and I’ve been reasonably happy with Open-Shell since then.
Still, Open-Shell doesn’t fix everything. I found Windows 7’s GUI a lot more attractive and a lot more usable. For starters, I could always tell which tab was active and I could see the caption buttons (Minimize, Maximize/Restore, and Close) without hovering over them.
I just don’t understand why “flat” is now considered better and more modern than “3D.” With today’s high-resolution displays and integrated graphics power, there can’t be *that* much of a performance or battery penalty associated with providing a bit of 3D texture in the GUI. (And it’s not just Windows; the Cinnamon desktop environment went flat, too. Thank goodness there’s still KDE Plasma.)
Hi Martin:
I am not going to use the script, because I don’t run Windows 10, but your screenshot isn’t particularly readable, and the video goes much too quickly for it to be useful, IMHO.
Thanks for the information.
@Anonymous: Ghacks covered this yesterday. Open the screenshot in a new tab and click on it to go full-size.
Interesting that one thinks he/she can write a perfect script that will eliminate quasi-systemic issues [where none exist] without affecting the rest of the system in a negative way. Only metaphor I can think of: Any doctor or pharmacist or patient on medications will explain how changing one medication necessarily affects all of the other medications entering the system–sometimes in unforeseen ways. An OS is no different.
It’s a great script, and I would trust the work of Mark Eugene Russinovich; yes, the script is a great piece of work . . . until . . . . Then what will the user do?
I rarely modify Windows 10 unless I know exactly why I think I need the modification; will the supposed modification actually eliminate a “real” system problem; am I able to quickly and effortlessly undo the modification without resorting to image backups and system restore points.
I do admire such coding skills; why doesn’t Microsoft hire Dmitry Nefedov. As it is, if the script is decidedly beneficial, Dmitry just lost over $1,000,000 or more.
If you have to restort to using metaphors to describe these supposed “quasi-systemic issues [where none exist]” i suspect you don’t know what the issues are. If you don’t understand what the medication necessarily affects that the doctor or pharmacist or patient is taking it’s probably better to remain silent and be thought a fool than to speak and remove all doubt.
“it’s probably better to remain silent and be thought a fool than to speak and remove all doubt”.
We’d have hardly any comments on any topic if everyone followed that advice!
;-)