This is what I use for removal - easily edited to add or remove apps for removal:

$File = New-Item -type File "C:\kworking\app-remove.txt"
$PackagesToRemove = @(
"Microsoft.Advertising.Xaml"
"*windowsalarms*"
"*getstarted*"
"*CandyCrushSaga*"
"*Appconnector*"
"Microsoft.3DBuilder"
"Microsoft.BingFinance"
"Microsoft.BingNews"
"Microsoft.BingSports"
"Microsoft.BingWeather"
"*windowscamera*"
"Microsoft.CommsPhone"
"Windows.ContactSupport"
"Microsoft.ConnectivityStore"
"Microsoft.Getstarted"
"Microsoft.Messaging"
"Microsoft.MicrosoftOfficeHub"
"*officehub*"
"Microsoft.MicrosoftSolitaireCollection"
"*Office.Sway*"
"Microsoft.Office.Sway"
"Microsoft.People"
"*skypeapp*"
"*Netflix*"
"*Twitter*"
"*Messaging*"
"*money*"
"*solitairecollection*"
"*zunevideo*"
"*xboxapp*"
"*windowsphone*"
"*bingnews*"
"*bingfinance*"
"*bingsports*"
"*bingweather*"
"*PandoraMediaInc*"
"Microsoft.WindowsAlarms"
"Microsoft.WindowsCamera"
"Microsoft.windowscommunicationsapps"
"Microsoft.WindowsFeedback"
"Microsoft.WindowsStore"
"Microsoft.WindowsPhone"
"Microsoft.XboxApp"
"Microsoft.XboxGameCallableUI"
"Microsoft.XboxIdentityProvider"
"Microsoft.WindowsZuneVideo"
"Microsoft.ZuneMusic"
"Microsoft.ZuneVideo"
)

#Uninstall from current user and default user
#This also prevents these packages from being installed on new users

Start-Transcript -path $File

ForEach ($package in $PackagesToRemove)
{
Get-AppxPackage | where-object {$_.packagename -like $package} | Remove-AppxPackage
Get-AppxProvisionedPackage –Online | where-object {$_.packagename -like $package} | Remove-AppxProvisionedPackage -Online
Start-Sleep -s 4
Get-AppXPackage -allusers | Remove-AppxPackage
}

Stop-Transcript
$File.close

This is what I use for restoring apps to the original - if I screw something up and need to put it back:

Get-appxPackage -AllUsers| ForEach {Add-appxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppxManifest.xml"}

Zippo, did you use it for some time, did you have some problems with widows after performing it, maybe some dependency or something like that?

I've been using it since we began deploying Win10 and still use it for every machine we deploy. No issues, to date. It does not remove everything but does do a great job of getting the majority of the bloatware out of there.

Zippo, why do you use this line  because this removes all builds in packages , not only listed in an array. correct me if I'm wrong

"Get-AppXPackage -allusers | Remove-AppxPackage"

That's correct. If I miss including anything in the list this will get it. If they add new garbage, this should get it. You can comment it out (or remove it) if you prefer.

If that case you don't need this

Get-AppxPackage | where-object {$_.packagename -like $package} | Remove-AppxPackage

just this

Get-AppxPackage -allusers | Remove-AppxPackage

in Get-appxpackage you can't have $_.packagename but $_.name.

Besides that when you execute get-appxpackage | remove-appxpackage you can't remove all apps but most of them because there are some that can't be removed as I tested it.

Yes, you are correct. Sorry if I gave the impression that this would remove every bit of bloatware from a WIN10 machine. There will be some that will need to be removed manually and some that will not be able to be removed and, what I consider bloatware, you may consider invaluable application programming. The script works well for us but YMMV...

As I could see , Microsoft often add new unwanted software here, my solution is delete all except stated in order not to check if any new software is added every time. I want to keep photos, weather.. everything else want to delete

Get-AppxPackage | where-object {{$_.name -notlike "*soundrecorder*"} -or `

{$_.name -notlike "*weather*"} -or `

{$_.name -notlike "*photos*"}  | Remove-AppxPackage

We have only one user per computer so I don't use

Get-AppxProvisionedPackage –Online | where-object {$_.packagename -like "*photos*"} | Remove-AppxProvisionedPackage -Online

I finally succeeded in running this via procedure. 

I needed to put "set-executionpolicy -executionpolicy bypass -force" in ps script itself. 

Before that I was putting the same command in agent procedure properties but didn't work for me.