Fresh Win 10 install - doesn't include crapware

JaredBusch

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

@JaredBusch said in Fresh Win 10 install - doesn't include crapware:
@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.
Twitter also broke sysprep.
snippity snip

That looks like part of one of the big decrappify scripts. I don't care about that.

Obsolesce

@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:
@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.
Twitter also broke sysprep.
snippity snip
That looks like part of one of the big decrappify scripts. I don't care about that.

Yeah, I made that before we started any Win10 sysprep'd images. It was quite useful then.

I only need to use that on regular installs, which is rare now.

Obsolesce

It's odd your sysprep is failing. That hasn't happened in my experience.

JaredBusch

Looks like maybe that registry key is workign a little? those six in the right on my screenshot are still not populated after multiple updates and reboots.

0_1495752015526_upload-73ff1afe-bcf3-48da-a5ed-5c6eac4b4955

JaredBusch

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

It's odd your sysprep is failing. That hasn't happened in my experience.

Hasn't failed yet, but did when I made my original images last year prior to AU coming out.

JaredBusch

Here we go.. Time to find out.
0_1495752279769_upload-770cd0da-cfd6-4fb0-82d6-a607a4dd7922

I have a bunch of software to install but wanted to verify this first..

JaredBusch

Hot damn, it did work. I was acting like @Dashrender and getting over excited about shit before trying. All because the twitter icon popped in.

0_1495752427632_upload-893f953c-203f-4a39-be4d-aecaac6d5910

stacksofplates

Wow reading through this makes my head hurt.

Dashrender

That Reg fix in the OP stopped working in 1607.

Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

JaredBusch

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

That Reg fix in the OP stopped working in 1607.

Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

You would be incorrect as I just clearly showed it working in 1703

Dashrender

@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

That Reg fix in the OP stopped working in 1607.

Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

You would be incorrect as I just clearly showed it working in 1703

Maybe they added it back in 1703 due to complaints. Also, so now that you've got the image, have you deployed it and none of those crappy apps came back?

JaredBusch

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

That Reg fix in the OP stopped working in 1607.

Perhaps what was fixed was that MS fixed the issues Sysprep was having with the pre installed apps.

You would be incorrect as I just clearly showed it working in 1703

Maybe they added it back in 1703 due to complaints. Also, so now that you've got the image, have you deployed it and none of those crappy apps came back?

I've never cared about them coming back.

JaredBusch

@Dashrender said in Fresh Win 10 install - doesn't include crapware:

Maybe they added it back in 1703 due to complaints.

I never made a 1607 - Anniversary Update image, so no idea.

NerdyDad

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.

I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

Obsolesce

@NerdyDad said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.
I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.

I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:

Get-AppxPackage -AllUsers | Select Name | FT

and

Get-AppxProvisionedPackage -Online | Select DisplayName | FT

black3dynamite

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

@NerdyDad said in Fresh Win 10 install - doesn't include crapware:
@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.
I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.
I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:
Get-AppxPackage -AllUsers | Select Name | FT
and
Get-AppxProvisionedPackage -Online | Select DisplayName | FT

Any harm removing all AppxPackages and AppxProvisionedPackages?

Obsolesce

@black3dynamite said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@NerdyDad said in Fresh Win 10 install - doesn't include crapware:
@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.
I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.
I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:
Get-AppxPackage -AllUsers | Select Name | FT
and
Get-AppxProvisionedPackage -Online | Select DisplayName | FT
Any harm removing all AppxPackages and AppxProvisionedPackages?

Yes don't do it.

JaredBusch

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

@black3dynamite said in Fresh Win 10 install - doesn't include crapware:
@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@NerdyDad said in Fresh Win 10 install - doesn't include crapware:
@Tim_G said in Fresh Win 10 install - doesn't include crapware:
@JaredBusch said in Fresh Win 10 install - doesn't include crapware:

@Tim_G said in Fresh Win 10 install - doesn't include crapware:

I made a PowerShell script to run that cleans it all up automatically. Well a .bat that runs it. I have it somewhere on SW, but it's out of date. I'll find the one I have that's more up to date and edit this post.

I honestly do not care if the crap is there or not.

But sysprep fails with some of it there. That is the problem I have with it. I just want a fucking image with my basic stuff pre-installed. I could care less if the user has Candy Crush. That is a managerial issue.
Get-AppxPackage -AllUsers *Candy* | Remove-AppxPackage
Get-AppxProvisionedPackage -Online | Where-Object {$_.PackageName -Like "*Candy*"} | ForEach-Object { Remove-AppxProvisionedPackage -Online -PackageName $_.PackageName}
That's basically all the powershell script contains. Removes about 30 different things. Probably more with the Creators update. But you need to uninstall it from both the "allusers" and "online". You'll have to reboot for it to be completely gone.

If you don't remove the app using the bottom "-online" part, it'll be there for new users.
I'm going have to update my scripts as I just gave a presentation on this last night. Thanks.

Also, if you look at the fullpackagename property of the appx, if the suffix is cw5n1h2txywey then it is system dependent and cannot be removed. The some of the XBox appx packages are that way.
I noticed that if you want to keep an up to date list of Crapware MS sticks on, like after big updates such as 1703 and the like, you'll need to run a command to get a new list of apps to see if you need to add any to the list. This is what I use:
Get-AppxPackage -AllUsers | Select Name | FT
and
Get-AppxProvisionedPackage -Online | Select DisplayName | FT
Any harm removing all AppxPackages and AppxProvisionedPackages?
Yes don't do it.

Can you not do a regular expression to match everything not like that specific version of that key

black3dynamite

Windows Configuration Designer seems to be the tool that helps with removing pre-installed software.

Dashrender

So @JaredBusch claimed that using the registry entry listed in the first post would prevent the crap from coming back in 1703, but I couldn't get the same results.

Today while creating a new image again, I noticed that the account created during logon had most, if not all of the crap, in spite of the registry key, but now I'm noting a followup user logon to the system does not have the crapware listed in the start menu.