Jump to content

How to get rid of Candy Crush Soda Saga and other Windows 10 Start Menu junk for good!


Recommended Posts

Posted
Interesting, I have a test laptop set-up with 1703 and haven't had any major problems so far.

 

I suppose that's part of the issue, everybody wants it to do different things, or get it to work how they want. It's a shame but I guess they cannot easily be all things to all people, as much as they are trying to cram it with as many features as possible and future proof it.... All they need to do is work out a way that it's all easily removed (hard when the apps come as a core part of the OS with many dependacies, but not impossible surely) without all of the reg hacks, removal scripts, etc...

 

 

 

Yeah, I do understand what you mean. However, it's all down to very individual needs and school IT ethos. We don't even use OneDrive and unless there is a dramatic change in the way we work, which with nearly 7 years of Win 7 and no major issues - (all nicely locked down with minimal GPO's and no extra crud needing to be removed) would prove doubtful, then I think missing out on 'features' which a lot of people are trying to remove, is something we'll live with.

 

And by 2023 we'll be worrying about Windows 11 or something (unless 10 is the last Windows version ever)...

Microsoft did say that Windows 10 will be the last 'version' of Windows. The updates will now always come in the form of two major updates per year.

Posted

 

And by 2023 we'll be worrying about Windows 11 or something (unless 10 is the last Windows version ever)...

 

If I haven't converted us to a Google School by then I'll be doing a different job. I've had enough of forcing MS products into a fit for purpose state

Posted

Before I lose it completely and turn to the dark side (LTSB, I'm looking at you)...

 

Could anybody please link me to the app removal script for 1607 please?

 

Specifically this one:

 

WIN 10 EDU 1607.jpg

 

I appear to be a little bit lost in this thread now, somewhere around page 7... :confused:

 

I have one that works on the US-EN version, but not the GB, as I'm getting a lot of 'not found' results on app removal.

 

I also read in the thread somewhere it would work on the 'July' release, but I can't see that on my VLC downloads.

Posted
Before I lose it completely and turn to the dark side (LTSB, I'm looking at you)...

 

Could anybody please link me to the app removal script for 1607 please?

 

Specifically this one:

 

[ATTACH=CONFIG]46155[/ATTACH]

 

I appear to be a little bit lost in this thread now, somewhere around page 7... :confused:

 

I have one that works on the US-EN version, but not the GB, as I'm getting a lot of 'not found' results on app removal.

 

I also read in the thread somewhere it would work on the 'July' release, but I can't see that on my VLC downloads.

@Arthur's post on page 11 is the one you want I think: http://www.edugeek.net/forums/windows-10/165029-how-get-rid-candy-crush-soda-saga-other-windows-10-start-menu-junk-good-11.html#post1620538

 

Even though it is works for 1703 and 1709, I believe it also works for old versions, including 1607 and 1610.

 

I would imagine that you can ignore the 'not found' messages, as the script will be looking to remove features in the newer versions...but obviously 1607 doesn't have them. I would have thought that it would still remove the non-whitelisted apps that it does have installed.

Posted

I'm not using an ISO but using an in-place upgrade to 1709 on some new Dell laptops that we purchased with W10 preinstalled. Being a PS novice what would I need to adjust in your PS script to lock our machines down please so that the various apps are no longer available, please?

 

it

Arthur,

 

Does it still add in the updates?

I seem to recall the last script required an Updates folder with sub-folders named "CU", "Flash Player" and "Servicing Stack" with relevant updates downloaded from the Microsoft Update Catalog.

 

 

 

 

 

 

--------------------------------------------------------------------------------

Join Date:Feb 2007Location:51.5044937,-0.0860132Posts:15,337Thank Post:556Thanked 5,507 Times in 3,791 Posts Rep Power:1433

 

 

 

 

 

 

@
3s-gtech
, @
jmak
. Here's the new script...

 

Download: CandyCrusher.zip

 

This works slightly differently to the old script so I have written some instructions.

 

1.Save the script into the root of a new folder. e.g. D:\W10x64.

 

 

2.Copy your Windows 10 v1607 July '16 ISO into this folder (same location).

 

 

3.Create an Updates subfolder (e.g. D:\W10x64\Updates) containing three subfolders (CU, Servicing Stack and Flash Player).

 

 

4.Download the updates linked below that match the architecture of your Windows ISO and save each .msu into its relevant subfolder within the Updates folder.

 

 

 

Code:

Cumulative Update (Janaury 2017, 14393.726)

x64:
http://download.windowsupdate.com/c/msdownload/update/software/crup/2017/01/windows10.0-kb3216755-x64_eba0675fd22087449c80b4d26df6b7035e9fb91f.msu

x86:
http://download.windowsupdate.com/d/msdownload/update/software/crup/2017/01/windows10.0-kb3216755-x86_0706d23dba493b295a32b9b56604aa0b08971ac7.msu

 

 

Code:

Servicing Stack (Janaury 2017)

x64:
http://download.windowsupdate.com/d/msdownload/update/software/crup/2017/01/windows10.0-kb3211320-x64_2abc94fceb4d1cdd908b3bdba473e28e0c061a3d.msu

x86:
http://download.windowsupdate.com/c/msdownload/update/software/crup/2017/01/windows10.0-kb3211320-x86_b450a744674c27bf2871f8db28f0e2e13e874582.msu

 

 

Code:

Flash Player (MS17-005)

x64:
http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows10.0-kb4010250-x64_fa7ad44be8dd1c65b51f07efbee478b0fbf82f5c.msu

x86:
http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/02/windows10.0-kb4010250-x86_8e6459131457bd164eee5160d316d223ba599c2f.msu

 

5.Amend the $AppsToKeep and $ISO variables on lines 17 & 18 of the script.

 

 

6.Run the script from an elevated PowerShell or PowerShell ISE prompt on a Windows 10 PC. When it finishes you should end up with an image that contains the latest updates and no unwanted apps.

 

Thanks.

Posted
Just tried this on the latest (November 2016) Edu ISO, but I get:

 

[ATTACH=CONFIG]41742[/ATTACH]

 

Does this latest ISO not have these apps in it? Or more likely, is something else amiss? The same Powershell script worked on a slightly older Windows 10 Edu ISO.

 

It worked fine for me at the time, but I think I will do some more testing. :D

 

Are you using the Jan 2017 1607 ISO now?

 

No, November 2016 (January 2017 isn't showing on VLSC for me). The other thing that may be slightly different is I'm using the English International version, but the script still sees the apps correctly.

 

The November 2016 ISO was released in January 2017. That's the one I meant. :)

 

Woops, then yup it is that version. When I run the script on that version, but the US English ISO this time, it works. That would suggest either an issue with version numbers of the apps somehow, or the English International version doesn't come with these apps installed somehow (I haven't installed it to check). Worth noting anyway - the script doesn't (at present) work on the English International version of the November 2016 ISO/wim. That's a pain, as I don't want to roll out the wrong localisation as it bugs me, and I don't want to roll out the apps in the images either.

 

@3s-gtech, @jmak. Here's the new script...

 

[*]Copy your Windows 10 v1607 July '16 ISO into this folder (same location).

 

 

Sorry for the ridiculous abuse of the multi-quote, but I am just trying to put all the relevant info in one place.

 

To me it reads that the script worked on the 'July' 1607 eng-intl iso, but didn't work on the 'Nov' 1607 eng-intl iso. However, it DID work on any version of the eng-us version of the 1607 iso. I have read through a couple of times and don't see any other way around it. No mention is made of getting it to work on anything other than on the 'July' version. Then everybody moves on to 1703....

 

I have confirmed that running the script on the (only versions available for me to download) 1607 eng-us iso removes apps as expected and yet running it on the eng-intl iso, it cannot find those SAME apps...

 

WIN_10_EDU_1607_ENG_US.jpg

 

WIN_10_EDU_1607_ENG_INTL.jpg

Posted
That's right. The July ISO was the last one done - updates after that were just rolled into the July ISO for deployment and the November one wasn't used. It's a decent enough solution really, as you're just building your own 'up to date' ISO with July as the base.
Posted
Ah, that's a shame as I can't find the July iso

I have another (much improved) script that works with the latest 1703 and 1709 ISOs from VLSC.

 

1703 (x64) = SW_DVD9_WIN_EDU_10_1703.1_64BIT_Eng_Intl_MLF_X21-47828.iso
1709 (x64) = SW_DVD5_Win_Pro_Ent_Edu_N_10_1709_64BIT_Eng_Intl_MLF_X21-50145.iso

 

If you would like to test it out before I post details in this thread I can PM you a link? :)

 

I'm not using an ISO but using an in-place upgrade to 1709 on some new Dell laptops that we purchased with W10 preinstalled. Being a PS novice what would I need to adjust in your PS script to lock our machines down please so that the various apps are no longer available, please?

How would you be doing the in-place upgrade? Existing .wim file, update from the Internet/WSUS etc?

Posted (edited)
I have another (much improved) script that works with the latest 1703 and 1709 ISOs from VLSC.

 

Thanks @Arthur, but I am trying (unsuccessfully) to track down the 'July' release of the .ISO for the eng_intl version of 1607 that is mentioned.

 

I don't think the script is at fault at all, just that it didn't work on the version released after that (November) - unfortunately that is the only one available for me to download.

 

I just want to deploy 1607 and have done with it until 2023...

 

It's not life or death that it has to be the eng_intl version as the previous script works on the en_us version (even the November one) and if i really have to I will deploy that.

 

Edit: Unless you are saying that the new script will work with the Nov 1607 eng_intl iso...?

Edited by Koldov
Posted
Unless you are saying that the new script will work with the Nov 1607 eng_intl iso...?

I will test it with 1607 tonight and let you know.

  • Thanks 1
Posted
Any joy with this?

I've tested it with the current 1607 ISO on VLSC (SW_DVD5_WIN_EDU_10_1607.1_64BIT_Eng_Intl_MLF_X21-27255.iso) and it didn't work unfortunately. :(

 

I have found an older ISO and will test that one shortly.

 

SW_DVD5_WIN_EDU_10_1607_64BIT_Eng_Intl_MLF_X21-07236.iso

MD5: 5f44218999f77d05b1e9dac4b633d1a2
SHA-1: b09af2afb921782031055f60ff0f2a705a78dc6a
SHA-256: c072cc86d84722befc09273308f775b703a079e78494caed55380f67f6611128

  • Thanks 1
  • 3 weeks later...
Posted

Extreme powershell noob here, trying to run the PS and returns the following error

 

pserror1.JPG

 

I have the PS script in the same folder as the ISO. Am I missing something here or have I completely misunderstood what I am supposed to be doing.

 

pserror2.JPG

Posted
Extreme powershell noob here, trying to run the PS and returns the following error

Are you using the PowerShell ISE or the regular PowerShell console?

 

If the former, it might have something to do with the $PSScriptRoot variable.

Posted (edited)

Running as admin?

 

Have you got a different .ISO name than the one in the script (it was about line 30 in the old script) ?

 

Or is this the script that works on the .WIM and not the .ISO?

 

What is the script name you are running?

 

I didn't go the 'invoke-removebuiltinapps blah blah' route when running the script, I just CD into the directory and ran ./removeapps.ps1 iirc

 

Edit: Sorry haven't had my coffee yet.... Can see most of that is correct now....

Edited by Koldov
Posted

Thanks for your help guys. I couldnt get the script to run locally on my machine so I ran it in a completely fresh install of Windows 10 on a VM, I was then able to run the script.

 

It seemed to be running ok and I could see apps being romved but when it came to doing hte unmounting I got alot of what can be seen below. Is this normal or not?

 

pserror3.JPG

  • Thanks 1
  • 2 weeks later...
  • 1 month later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...