Fresh Win 10 install - doesn't include crapware

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.

JaredBusch

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

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.

I am not claiming shit. I clearly documented it.

I expect you problem is because the "crap" you are seeing is not part of the items restricted. I showed a screen shot right there in post 33.
https://mangolassi.it/topic/8691/fresh-win-10-install-doesn-t-include-crapware/33

Dashrender

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

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

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.

I am not claiming shit. I clearly documented it.

I expect you problem is because the "crap" you are seeing is not part of the items restricted. I showed a screen shot right there in post 33.
https://mangolassi.it/topic/8691/fresh-win-10-install-doesn-t-include-crapware/33

FFS - I was saying you appeared to be right, geez!

Dashrender

Here is the first profile picture.

Notice the crap. (I built the machine with no network connection, put the reg key in (saw the arrows), rebooted, then logged in as this user again - installed my apps - then plugged into the network and got updates, added second user, and logged in as them - saw cleaner start menu)

JaredBusch

The image I posted in post 22 shows what it looked like after getting online and doing updates
https://mangolassi.it/topic/8691/fresh-win-10-install-doesn-t-include-crapware/22
Here is is again for you. The six apps on the right never downloaded or installed.
https://i.imgur.com/KtnDvEn.png

Dashrender

My only guess is that you didn't give them enough time.

I definitely have had the arrows hang around after several reboots, but eventually they always turned into the crap.

But the new users after the registry entry is added never have the arrows, and never have the crap.

So the end result is no crap, well - Xbox is still there, and Skype.. but at least most of the shit is gone.

JaredBusch

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

My only guess is that you didn't give them enough time.

I definitely have had the arrows hang around after several reboots, but eventually they always turned into the crap.

But the new users after the registry entry is added never have the arrows, and never have the crap.

So the end result is no crap, well - Xbox is still there, and Skype.. but at least most of the shit is gone.

Shall I prove you wrong? I still have the virtual machine pre-sysprep. I can boot it back up anytime. One of them was booted and running for over a month before I ran made a snapshot and did sysprep and it is still like that after reverting to the snapshot.

Dashrender

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

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

My only guess is that you didn't give them enough time.

I definitely have had the arrows hang around after several reboots, but eventually they always turned into the crap.

But the new users after the registry entry is added never have the arrows, and never have the crap.

So the end result is no crap, well - Xbox is still there, and Skype.. but at least most of the shit is gone.

Shall I prove you wrong? I still have the virtual machine pre-sysprep. I can boot it back up anytime. One of them was booted and running for over a month before I ran made a snapshot and did sysprep and it is still like that after reverting to the snapshot.

You still having the arrows after a month proves nothing. Only that you still have arrows. something could be broken for whatever reason.

I'm assuming the additional users are behaving like mine though, and don't have the crap.

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:

My only guess is that you didn't give them enough time.

I definitely have had the arrows hang around after several reboots, but eventually they always turned into the crap.

But the new users after the registry entry is added never have the arrows, and never have the crap.

So the end result is no crap, well - Xbox is still there, and Skype.. but at least most of the shit is gone.

Shall I prove you wrong? I still have the virtual machine pre-sysprep. I can boot it back up anytime. One of them was booted and running for over a month before I ran made a snapshot and did sysprep and it is still like that after reverting to the snapshot.

You still having the arrows after a month proves nothing. Only that you still have arrows. something could be broken for whatever reason.

It proves your clearly worded state wrong. You stated I did not wait long enough. I can tell you that you are wrong.

I'm assuming the additional users are behaving like mine though, and don't have the crap.

Dunno, don't care. Never have. The entire point has always been to be able to perform a sysprep without errors.