Not Found

The requested URL index.php was not found on this server.

Apache/2.2.22 (Linux) Server at Port 80
1 Windows 10 Decrapifier – Win10.Guru
Go to ...

RSS Feed

March 29, 2020

Windows 10 Decrapifier

What it is?

Windows 10 Decrapifier is a PowerShell script by csand, a fellow member at It is used to clean a Windows image prior to its deployment by removing unwanted or unnecessary apps and tasks, and modifying privacy settings. Because it runs in script forms, users can modify it according to their own specific needs.

Running the script as-is with no modifications, it removes all Store apps except Store itself and other important apps such as Calculator and Sticky Notes. For most users this is OK.

Why Run the Script?

There are many Windows native apps I do not use nor want. Your mileage may vary, but I am quite sure that you, too, uninstall some apps as soon as your get to the desktop after a clean install. The same is true for some native tasks and settings as well.

After running the script, its results are immediately obvious. For instance, in my tests now, RAM usage on a VM after clean install of the latest Insider build, after letting the VM stay idle for a few minutes, is about 2.2 GB (VM with 6 GB RAM, 8 vCPU). The same VM after running the script, after reboot and a few minutes wait to let VM to “calm down” shows only 1.3 GB RAM usage. On a physical machine, deploying a fresh image with my standard settings and software uses about 4.4 GB RAM after first boot to desktop, whereas the same machine shows 3.2 GB RAM usage after boot if the script was run in Audit Mode before the image was captured.

The whole system footprint really is smaller.

How to Get It?

Download the script from Spiceworks:

In this example, I installed Windows 10 Insider build 18990 (W10 PRO x64 EN-GB) on a Hyper-V virtual machine, booting it to Audit Mode. I ran Edge and downloaded the script, saving it as CleanWindows.ps1, and opened it in the PowerShell ISE script editor to edit the script. I decided to keep two specific apps in my deployment image: namely, Feedback Hub which is essential for a Windows Insider like me, and the Microsoft Weather app (it’s simply my favourite of all weather apps; #1 in next screenshot). Apps to keep are itemized in variable $GoodApps, which appears in line 85 in the script.

I then run the script with three switches to clean the Start Menu, keep OneDrive and related settings, and keep Cortana and Windows Search (#2 in screenshot, click to enlarge):

All available switches are documented on the script’s instructions page.

My opinion?

This script does a good job, working almost as expected. I used the word almost in the previous sentence because, at least on my tests using the latest Insider build, the -cortana switch which is supposed to leave Cortana and Windows Search intact did not work. Other than that, the script really produces a nice and tidy Start:

If you really do not need Cortana, I can wholeheartedly recommend using this script. Of course, as Cortana can be reinstalled, you can also use the script to clean Windows setup and then reinstall Cortana. It’s much faster and easier than removing unwanted apps one by one. Integrating script to an MDT deployment image, you can deploy identical, clean image meeting the corporate guidelines to all devices.

Although this one switch not working for me, I will for sure start using the script, with my edits.

I have only one objection: the name. What is crap to someone, is essential to another user. Doubting my non-native English, I had to check the meaning of word crap before criticizing it:

I do not like the name, I do not like degrading and mocking names used for Windows and its features, however funny and witty they are supposed to be. This is why I also only used the name of the script seldom (and with reluctance) in this story, and mostly talked just about the script. But, as I mentioned, that’s my only objection. This is, of course, just a subjective, personal opinion.




Author: Kari Finn

A former Windows Insider MVP, Kari started in computing in the mid 80’s writing code for VAX / VMS systems. Since then, he’s worked in a variety of IT positions. He specializes in Windows image capture, customization, repair and deployment as well as Hyper-V virtualization. Kari is a proud Team Member at number #1 Windows site

5 Responses “Windows 10 Decrapifier”

  1. CountMike
    October 3, 2019 at 16:25

    I’m dead against programs like that. There are better ways to remove “crap”. most of it built into windows.

    • October 10, 2019 at 12:19

      I am not as much against this script itself, as it can be modified by user. What I am against is the name of it, the name chosen by the author. The name basically says that each and every Store app is crap, which is not true. There are users for whom Mail app is everything they need for their email accounts, those who simply like a game of Solitaire, Microsoft Weather app is the best weather app I have seen, and so on.

      However, generally speaking I must agree with you. Most of optimizers, tweakers and such are snake-oil, doing in some cases more harm than good. Windows is totally capable to take care of itself, and it is quite easy to remove and disable features and elements with just a few commands.

  2. October 20, 2019 at 19:33

    Hey guys! I wrote the script 🙂 Thank you for the write up, I’m glad you found it useful. The name was really a joke, I love Windows 10 and use the apps regularly myself. I didn’t like Candy Crush etc cluttering up the menu so that was where the “crap” part came from, haha.

    Just in response to CountMike, the script uses only built-in methods. It’s all Powershell and everything it changes (barring a few settings) you could do using the GUI, or some other manual action (removing tiles from start, etc)
    So when you talk of “a better way to remove crap, most of it built into Windows”… Powershell is literally what you are talking about 🙂 Many of the actions you perform manually in Windows, are just graphical representations of a Powershell command. Powershell is the heart of Windows these days!

    I agree many cleanup scripts out there are dangerous and asking for a re-install. It is good to be cautious and skeptical. I see cleanup directions or scripts on line that will almost certainly break Windows. I try to describe each setting in the script and provide built-in options and usage documentation, so there are no surprises. There aren’t any irreversible or deep system changes, it’s all pretty basic stuff just lined up for the user to save time doing many common setup tasks. I research and test each setting before adding it in to make sure it doesn’t mess anything up.

    For Cortana, I’ve noticed in the insider build of 1909, I can’t even find Cortana without the script being used. Not sure if they changed something but I will sort it out if I need to change something. I have tested the -cortana switch in 1809 and 1903 and it works!

    Anyways just my 2c


    • October 21, 2019 at 08:32

      Hi Csand, good to hear from you!

      The script is nice, and does what promised. The Cortana issue, it was only when I tested the script in latest Windows Insider Fast Ring builds.

      Youy said:
      I agree many cleanup scripts out there are dangerous and asking for a re-install. It is good to be cautious and skeptical. I see cleanup directions or scripts on line that will almost certainly break Windows.”

      In my opinion, a common problem in using various snake-oil tweakers and optimizers is that users do not always understand how different features, policies and services in Windows are interlaced. Disable this, and suddenly that does not work. I always advice against all of them, I even tell users (especially beginners) not to use the most popular one, CCleaner. I have for instance never seen any proof that cleaning registry with it decreases the boot time even a few milliseconds, makes Windows snappier, or improves the functionality of Windows. But, as long as users keep wanting a few more frames per second, or want to make an idle Windows 10 to use only 3 GB of their 32 GB RAM instead of current 3.6 GB, they will use these completely unnecessary “tools”.

      As you mentioned, your script is native PowerShell. I integrated it to my MDT workbench, and will most certainly use it in the future. OK, in Insider Fast Ring builds, I must reinstall Cortana, but that’s a minor inconvenience compared to what I will achieve.


  3. Some Duder
    January 5, 2020 at 09:57

    The “crap” does not refer to the applications – it refers to the practice of including all of them in a standard Windows 10 installation. That’s a “crappy” practice

Leave a Reply

More Stories From Admin Tools