Jump to content

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


Recommended Posts

Posted
[ATTACH=CONFIG]49091[/ATTACH]

Does your Start Menu look the same if you delete the locally cached profile and then log in again?

  • 1 month later...
Posted
Extreme powershell noob here, trying to run the PS and returns the following error

 

[ATTACH=CONFIG]46515[/ATTACH]

 

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.

 

[ATTACH=CONFIG]46516[/ATTACH]

 

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

 

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

 

Just in case anyone else comes across this, I can confirm that the ImagePath variable in Line 120 has to match the file name. For the version I've just deployed it's:

 

Invoke-RemoveBuiltinAppsOffline -ImagePath "$PSScriptRoot\SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_Eng_Intl_-4_MLF_X21-87131.ISO"

 

For some reason in the version I have, the last line crediting CHiLL wasn't commented out - not sure if that's in the version I downloaded, or something I broke :)

 

I must have been lucky before as I just used the script as it came.....

Posted
How many images are there in 1803? Running the CandyCrusher script and it's now on the ninth! I thought when it unmounted the 6th I was done.
Posted
How many images are there in 1803?

There are now ten images (half of which are the useless 'N' editions no one actually uses).

 

To save time the best thing to do is to export the edition you need to a separate .wim.

 

TfiuEB.png

  • 2 months later...
Posted (edited)

I downloaded the ARM64 version of 1809 by mistake and ran the script to remove built-in apps and it returned the following list of apps:

 

Microsoft.BingWeather

Microsoft.DesktopAppInstaller

Microsoft.GetHelp

Microsoft.Getstarted

Microsoft.HEIFImageExtension

Microsoft.Messaging

Microsoft.Microsoft3DViewer

Microsoft.MicrosoftOfficeHub

Microsoft.MicrosoftSolitaireCollection

Microsoft.MicrosoftStickyNotes

Microsoft.MSPaint

Microsoft.Office.OneNote

Microsoft.OneConnect

Microsoft.People

Microsoft.Print3D

Microsoft.ScreenSketch

Microsoft.SkypeApp

Microsoft.StorePurchaseApp

Microsoft.VP9VideoExtensions

Microsoft.Wallet

Microsoft.WebMediaExtensions

Microsoft.WebpImageExtension

Microsoft.Windows.Photos

Microsoft.WindowsAlarms

Microsoft.WindowsCalculator

Microsoft.WindowsCamera

microsoft.windowscommunicationsapps

Microsoft.WindowsFeedbackHub

Microsoft.WindowsMaps

Microsoft.WindowsSoundRecorder

Microsoft.WindowsStore

Microsoft.Xbox.TCUI

Microsoft.XboxApp

Microsoft.XboxGameOverlay

Microsoft.XboxGamingOverlay

Microsoft.XboxIdentityProvider

Microsoft.XboxSpeechToTextOverlay

Microsoft.YourPhone

Microsoft.ZuneMusic

Microsoft.ZuneVideo

 

Features on Demand V2

Removing: Hello.Face.17658~~~~0.0.1.0

Removing: Hello.Face.Migration.17658~~~~0.0.1.0

Removing: MathRecognizer~~~~0.0.1.0

Removing: OpenSSH.Client~~~~0.0.1.0

Remember, this is from the ARM64 version. I will need to double check this when the 64-bit version is released.

Edited by CHiLL
  • 2 months later...
Posted

Sorry to be a pain but is there a script for 1803 that I can run during deployment of an image? Or can I run it just before capturing my latest image attempt?

 

Cheers all

 

Gareth

Posted
So - you just do your stuff with this and then import the custom .wim into MDT and capture before deploying?

Pretty much, although I don't bother with capturing. This allows me to swap out the image when a new version of Windows 10 is released and not have to do too much else.

 

I make my changes to a copy of the install.wim from the Windows 10 ISO (with OSBuilder) and then import this into SCCM. Applications that are installed on all computers like Office and Google Chrome are done via the task sequence. Other apps are installed post-deployment based on which collection the computer is in.

 

OSBuilder can also integrate the latest updates (servicing stack, cumulative updates, Flash Player and dynamic updates) which is good because the same image can also be used for in-place upgrades (which I don't think is possible when using a captured image).

Posted
Pretty much, although I don't bother with capturing. This allows me to swap out the image when a new version of Windows 10 is released and not have to do too much else.

I make my changes to a copy of the install.wim from the Windows 10 ISO (with OSBuilder) and then import this into SCCM. Applications that are installed on all computers like Office and Google Chrome are done via the task sequence. Other apps are installed post-deployment based on which collection the computer is in.

OSBuilder can also integrate the latest updates (servicing stack, cumulative updates, Flash Player and dynamic updates) which is good because the same image can also be used for in-place upgrades (which I don't think is possible when using a captured image).

 

Ahhh that SCCM step is where I fail. We do not have SCCM and I do it all via MDT so at the moment until I can get time to install all my apps silently via script then it's going to be import, install and capture.

 

Shame really. I'm sure it would be great and it's something I may work on in future as we do not really install a lot of apps.

 

Gareth

Posted

You don't need to capture with just MDT, do you?

I used to just deploy stock .iso's, with a few custom steps in the task sequence (things like setting backgrounds that only needed to be done the once) and let group policy take care of the rest. Never once did I ever capture a machine.

Or is that WDS?

Is there event a difference?

I dunno..

 

Only real difference between my old MDT/WDS setup and the SCCM setup I use now is that I deploy .wim's rather than .iso's and there's no optional applications step (how I wish that were a thing in SCCM).

Posted
You don't need to capture with just MDT, do you?

I used to just deploy stock .iso's, with a few custom steps in the task sequence (things like setting backgrounds that only needed to be done the once) and let group policy take care of the rest. Never once did I ever capture a machine.

Or is that WDS?

Is there event a difference?

I dunno..

Only real difference between my old MDT/WDS setup and the SCCM setup I use now is that I deploy .wim's rather than .iso's and there's no optional applications step (how I wish that were a thing in SCCM).

 

You are correct of course - but I have apps than need installing and I cannot get them to go on silently during deployment. It's something I will try and work out.

 

Gareth

Posted
Ahhh that SCCM step is where I fail. We do not have SCCM and I do it all via MDT so at the moment until I can get time to install all my apps silently via script then it's going to be import, install and capture.

 

Shame really. I'm sure it would be great and it's something I may work on in future as we do not really install a lot of apps.

 

Gareth

I'm still reading the documentation, but certainly looks like it'll work with MDT.

 

I had some success with deploying applications through the task sequence (coming at it from a position of zero knowledge). However, I now just deploy Office with MDT/WDS and do the rest with group policy. I've ditched everything that I can't find an MSI for [emoji16] (I do appreciate that's not an option for everyone.)

 

OSBuild does look like it has the capability to deploy applications as well, but the documentation for that bit like incomplete.

Posted
I'm still reading the documentation, but certainly looks like it'll work with MDT.

 

I had some success with deploying applications through the task sequence (coming at it from a position of zero knowledge). However, I now just deploy Office with MDT/WDS and do the rest with group policy. I've ditched everything that I can't find an MSI for [emoji16] (I do appreciate that's not an option for everyone.)

 

OSBuild does look like it has the capability to deploy applications as well, but the documentation for that bit like incomplete.

 

I'm having a bit of a nightmare with it at the moment. I'm importing the media but when trying to update it I'm being told there is no media and that I have to import it.

 

Strange. No help online.

 

Gareth

Posted (edited)
I'm importing the media but when trying to update it I'm being told there is no media and that I have to import it.

Try the following (change the bits in red if necessary)...

 

$ISO = "[color="#FF0000"]X:\ISOs\W10\1809\SW_DVD9_Win_Pro_Ent_Edu_N_10_1809_64-bit_English_International_MLF_X21-91481.iso[/color]"

$Drive = Mount-DiskImage -ImagePath "$ISO" -ErrorAction Stop
Import-OSMedia -ImageName "[color="#FF0000"]Windows 10 Education[/color]" -SkipGridView
$Drive | Dismount-DiskImage -ErrorAction Stop

 

Once the image has been imported, download the latest updates...

 

Get-OSBuilderUpdates -UpdateCatalogs -HideDetails

'Adobe', 'Component', 'Cumulative', 'Servicing', 'Setup' | ForEach-Object {
   Get-OSBuilderUpdates -Catalog $_ -Download -FilterOS "Windows 10" -FilterOSArch x64 -FilterOSBuild [color="#FF0000"]1809[/color] -RemoveSuperseded -HideDetails
}

 

Update your OSMedia...

 

Update-OSMedia -Execute -SkipWinpeCU

 

Create a new build task (this is the bit where you can select which apps you want to remove etc.)...

 

New-OSBuildTask -TaskName "[color="#FF0000"]Windows 10 Education v1809 x64[/color]" -EnableNetFX3 -DisableWindowsOptionalFeature -EnableWindowsOptionalFeature -RemoveAppxProvisionedPackage -RemoveWindowsCapability -RemoveWindowsPackage

 

Then execute the build task to create the new image (which you can then import into MDT/SCCM)...

 

New-OSBuild -Execute -SkipWinpeCU -ByTaskName "[color="#FF0000"]OSBuild Windows 10 Education v1809 x64[/color]"

 

There are some additional things I do, but that should get you started. :)

 

Strange. No help online.

Have you already seen the following page?

 

www.osdeploy.com/osbuilder/quick-instructions

Edited by Arthur
  • Thanks 1
Posted

Hi @Arthur - thanks for this. I get down to the 'Update-OSMedia - Execute -SkipWinpeCU' command and I'm getting the same error. OSMedia content not found.

 

Yes I've been reading the quick-instructions. It's the one I have been following whilst trying to learn about it.

 

Gareth

Posted
Are you using a Windows 10 Education v1803 or v1809 ISO from VLSC?

 

Hi there @Arthur - thanks for all the help. It's sorted now. I've spoken to the dev - David Segura on Twitter. Really nice chap who has helped. Send him screen shots and he spotted it straight away.

 

The issue was being caused by registry editing permissions being disabled. "Why was this?" I hear you cry - well we've moved to a new GPO structure within the LEA and I simply hadn't enabled it when bringing my old GPOs over. Silly me - all my fault.

 

I currently have my image being built with updates being added.

 

So - thanks for the help.

 

Gareth

Posted

Evening @ADMaster - yes you are correct. However there are some apps that do not come as MSI or do not come with silent installer switches.

 

Any idea how to install VBExpress 2010 with. Silent switch?

 

May need to create a fat image after all. :-(

 

Cheers

 

Gareth

Posted
thanks for all the help. It's sorted now. I've spoken to the dev - David Segura on Twitter. Really nice chap who has helped. Send him screen shots and he spotted it straight away.

Glad to hear you got it sorted. David is a really nice guy. Very helpful! He also added some features I requested to OSBuilder. :)

 

The issue was being caused by registry editing permissions being disabled.

I would have never guessed that. 🤯

Posted (edited)
Any idea how to install VBExpress 2010 with. Silent switch?

VB Express 2010 is relatively easy. The silent install command is:

 

setup.exe /q /norestart

 

However, I had a quick look myself and noticed that setup.exe runs additional installers in the background, but exits the bootstrapper immediately. This may cause issues with MDT (or SCCM) since they will think the installation has completed when in fact it is still in progress.

 

The easiest way around this is to use the PowerShell App Deployment Toolkit (PSADT) with the -WaitForMsiExec parameter. e.g.

 

Execute-Process -Path 'setup.exe' -Parameters '/q /norestart' -WindowStyle 'Hidden' -PassThru -WaitForMsiExec -ContinueOnError $false

 

I therefore created a PSADT script for you which you will find attached. :)

 

All you need to do is copy the VB Express 2010 installation files into the .\Files subfolder (making sure setup.exe is at the root of that folder), add your product key to the [Product Key] section of setup.sdb to automatically register the software (as mentioned here) and then import it into MDT as an 'Application'. The quiet install command will be:

 

Deploy-Application.exe Install NonInteractive

 

The working directory should be the folder that contains Deploy-Application.exe.

 

Hope this helps?

VB Express 2010 (PSADT) v1.0.7z

Edited by Arthur
  • Thanks 2
  • 2 months 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...