Windows 10 Decrapifier

Page 3 of 4 FirstFirst 1234 LastLast

  1. Posts : 5,048
    Windows 10/11 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #21

    lx07 said:
    No it doesn't - read the description again. It is asking if you trust it - same as any other with your settings.

    I would not run a massive script doing god knows what without absolutely trusting the source though.
    I totally agree.

    Hope you made a full, restorable backup should you wish to proceed!

      My Computer


  2. Posts : 5,478
    2004
       #22

    Compumind said:
    I totally agree.

    Hope you made a full, restorable backup should you wish to proceed!

    Why?
      My Computer


  3. Posts : 5,442
    Windows 11 Home
       #23

    One man's trash is another man's treasure.

    Just disabling onedrive's sync can break a lot of stuff. Windows 10 Decrapifier is simply someone's custom config. It is not one-for-all config. Some might like, some not, some will hate it. Use with caution.

    Lance1 said:
    Interesting on first run Powershell Gives me this warning...
    The script mentions: Remember to set your execution policy back!

    But such a cool script should do it by itself, like to run a script at the next boot to set it back.
    Anyway, even a child can bypass PS execution policy or __PSLockDownPolicy, so whatever.
      My Computer


  4. Posts : 5,048
    Windows 10/11 Pro x64, Various Linux Builds, Networking, Storage, Cybersecurity Specialty.
       #24

    lx07 said:
    Why?
    If you have the speed and time, there's nothing like a full image before you venture into the unknown.
    Now, I'm biased, as all my systems have SSD's and the backup drives as well.
    So for me, it's a few clicks and piece of mind, lol.

    On a HDD, you might not have the patience.

    FWIW.
      My Computer


  5. Posts : 1,728
    Windows 10 Pro (+ Windows 10 Home VMs for testing)
       #25

    I've used the Windows 10 Decrapifier script over a dozen times now without any issues. It says it's just for Windows 10 Pro/Enterprise versions 1803/1809 but works just as well with Win 10 Home and 1903. (There's also an earlier script for 1709 and earlier.)

    My only reservation is that the Spiceworks group is not particularly active so queries tend to go unanswered for long periods of time. Other than that, I love the results of the script, i.e. removing the built-in bloatware and leaving a nice clean Start menu so quickly and easily.

    Note that the script's purpose is primarily for use during the OOBE (Out Of the Box Experience) process of a clean install, not an upgrade. (Whilst it can also be used after installation of Win 10, it's less effective because the default account template has already been configured.)

    See Customize the initial Windows 10 installation for more info/walkthrough.

    Hope this helps...
      My Computer


  6. Posts : 4
    win 10 pro
       #26

    Lance1 said:
    Hi all and good day to ya. Well I was just randomly looking through the net today and ran across the this post at Spiceworks =-=> Windows 10 Decrapifier for 18XX/19XX Great site. Tuns of interesting stuff there. Anyway I just wanted to see if anyone has run this script? I just found it and wanted to show you all and see what you think of it. here's the script in a PHP.
    Hi everyone, I'm the author of that script!

    Sorry to resurrect this thread, I see some good concerns in here though and thought I would chime in.


    Many cleanup scripts are built with little consideration for what they are changing, the authors just choose every setting they think sounds bad and throw it in. People in this thread are right to treat stuff like this with caution and I know plenty of folks who have "cleaned up" Windows only to have to reinstall. You should always read through them. A problem is most scripts out there don't have descriptions to tell you what they are doing. If you read through my script, I have done my best to put a description by each setting so you know exactly what is happening.

    I test each setting. It has taken me days and days of work to get to that point, and every new setting I also test before releasing it.

    It's been an ongoing project which I started on the initial build of Windows, when I first got it back in 2015, and decided I really hated all the extra apps I didn't want. Initially i had no idea what I was doing. I made this script and like many others it broke stuff. This was before I released it, it was just for myself. I looked online for resources, I started to notice a lot (most?) of cleanup scripts that really did some damage and found it to be terribly irresponsible on the part of the authors to put them out there for regular folks to use, essentially breaking their system and potentially costing money for a repair!

    I have learned a lot over the years of working on this one and have been meticulous in testing to ensure a balance where it cleans the system, but avoids heavy handed potential "system breakers". Almost every setting it changes is a setting you can change in somewhere in Windows' GUI, and a small handful are GPO settings. Another small handful aren't available in the GUI and require a registry change, but I have kept those
    to a minimum. The purpose here isn't to drastically alter Windows under the hood, it is just to set an initial experience with a medium-light touch that doesn't feel like a cheap Android phone :)

    It is in regular use by large community of people on Spiceworks and that has provided me with great feedback on any problems. I also provide "best I can" support to anyone who needs it through the Decrapifier group on Spiceworks.

    To answer some of the concerns I have seen here:
    - it is best run on a brand new machine, before OOBE (audit mode) per the instructions in the link within the script. It applies settings to the default profile so it really is best if you haven't logged in yet.
    - it is quite customizable
    - it will remove all those default apps and bloatware and de-clutter the initial start menu, but won't remove anything that Windows requires to function.
    - Windows powershell always asks for the execution policy to be changed before a unverified script is run, so that is even more reason to read through it if you are feeling uncertain
    - it can be used (and is by many) as part of an enterprise deployment to get a nice clean UI right off the bat.
    - so far there have been very few issues that aren't just a case of people running without reading (IE, someone runs it with -allapps switch and removes the store, then wants the store back)
    - it creates a log file if you want for troubleshooting


    Anyhow, with all that said, DON'T TRUST ME. Read it yourself, test it, see if it fits. It is not for everyone, but so far everyone who's used it has been very happy with the result. If you need help, the Decrapifier Group on Spiceworks has a bunch of great people who have experience, as well as myself, who can provide some support. I don't get on other places often (like here) so Spiceworks really is the best way to get me if you have a question or request for it. My username there is the same as here

      My Computer


  7. Posts : 1,728
    Windows 10 Pro (+ Windows 10 Home VMs for testing)
       #27

    @csand - It's an AWESOME script and I love it. Thank you so much!

    I now use it on every new device I set Windows 10 up for family and friends... and every time I carry out a clean install on my own devices. (I always clean install instead of upgrade to each new major version now I have scripts to automate a lot of it.)

    I know that you developed your script for use within a work environment but my own experiences show that it's just as useful for home use. What I like about it is that it's simple to use - I just amended the existing XML $StartLayoutStr within the script (which was easy) to create my own preferred Start menu, set my three $GoodApps (store|calculator|miracast) that I wanted to keep and I was away!

    I'm experimenting with adding my own tweaks to a copy of your script but I'm no PowerShell coder... so I'm taking this very slowly and testing in a VM each step of the way.

    Currently I tend to just use REG files (many from here - thank you, @Brink et al) and my own AutoHotkey scripts to augment your script whilst I try to learn the rudiments of PowerShell.

    Anyway, thank you once again. I appreciate the cautious approach you have taken.
    Last edited by RickC; 01 Oct 2019 at 16:52.
      My Computer


  8. Posts : 4
    win 10 pro
       #28

    Hey Rick

    Glad you are enjoying the script! Honestly, I had first made it for use on my personal computers, but a few people asked me to "make it bigger" so I embarked on that and learned Powershell as I went. Lots of Googling and trial and error to begin with. Once you get the syntax down it is actually a pretty user-friendly language (has saved me TONS of tedious clicking at work let me tell you.)

    And you know, the best way to learn Powershell is just to mess with scripts like this! (Helps that you have a VM for testing.. those checkpoints come in handy )

    Anyways thanks for the nice comments, it is much appreciated and look out for future updates to the script (with 1909 coming soon).
      My Computer


  9. Posts : 1,680
    X
       #29

    I don't understand. Why bother with such a script?

    I have had two 98's, four XP's, two 7's, and two 10's ... and they never needed any decrapification.

    Have I somehow been lucky?
      My Computer


  10. Posts : 1,728
    Windows 10 Pro (+ Windows 10 Home VMs for testing)
       #30

    margrave55 said:
    I don't understand. Why bother with such a script?
    Freedom of choice.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:38.
Find Us




Windows 10 Forums