Remove-AppXProvisionedPackage -Online -PackageName Microsoft.WindowsAlarms_2015.1258.20.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.ZuneVideo_201.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.ZuneMusic_201.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.XboxApp_2016.322.258.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName _2016.325.13200.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.SkypeApp_3.2.1.0_neutral_~_kzf8qxf38zg5c Remove-AppXProvisionedPackage -Online -PackageName Microsoft.People_2016.219.2348.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName _2015.6769.45081.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName _2015.6769.17901.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.MicrosoftSolitaireCollection_.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.MicrosoftOfficeHub_2015.6811.23771.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.BingWeather_4.8.277.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.BingSports_4.8.268.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.BingFinance_4.8.268.0_neutral_~_8wekyb3d8bbwe Remove-AppXProvisionedPackage -Online -PackageName Microsoft.BingNews_4.8.268.0_neutral_~_8wekyb3d8bbwe Here are examples of removing some of the more esoteric apps: Remove-AppXProvisionedPackage -Online -PackageName Microsoft.3DBuilder_10.10.38.0_neutral_~_8wekyb3d8bbwe To remove Modern Apps on an individual basis, use the Remove-AppxPackage cmdlet. If you wanted to remove all Modern Apps from a machine (except for those that are listed as part of the operating system), use this command: Get-AppxProvisionedPackage -online | Remove-AppxProvisionedPackage -onlineīear in mind that this will also remove the Calculator app, so you may want to take a more piecemeal approach. They are specified on a device-by-device basis, so you will need to run the cmdlets on each machine from an administrative PowerShell session. PowerShell cmdlets exist to allow you to remove Modern Apps either individually or all at once.
The delivery of patches and feature updates will be significantly affected, so it is something about which you need to think carefully before taking the plunge. However, there are things you need to be aware of, as the LTSB version (only available on Enterprise) is essentially a whole different operating system.
#Windows 10 login takes 10 minutes windows
This is the option Microsoft would rather you didn’t take, but if you’re really concerned about the effects of Modern Apps, the LTSB option removes almost all of them (including bringing back the old Windows 7-style Calculator application). It may also go against policies regarding power consumption. Using a technology to start up machines prior to user arrival may help with this, but in many environments, this isn’t something that can be accurately predicted. Logging on straight after a cold boot increases logon time by approximately 30 seconds in my lab. However, the trade-off comes when you log straight on after a cold boot the operating system is still running boot processes in the background.
#Windows 10 login takes 10 minutes windows 10
This is intentional-a smoke-and-mirrors approach to make Windows 10 look like it boots up much faster. In the background, there’s still a lot of stuff going on to do with the boot process. Windows 10 doesn’t specifically finish “booting up” when the logon screen is presented. So how can you decrease logon time? Try not to log on straight after a cold boot ^ In this case, you may just want to improve the first logon time anyway, even if you’re not removing cached profile copies, so that your users don’t develop a negative perception of the new operating system you’re deploying. However, if you’re in an environment where you have “open access” machines, which remove cached local profiles after a certain period of time, then users may be exposed to the “first logon” experience a lot more often than they’d like.Īdditionally, if you use any sort of solution in which the copy of the profile is removed, this issue will keep on rearing its head. This stands to reason-they now have a local profile cached on the device.
Once a user is logged in for the first time, if they’re using a local profile, subsequent logons to this machine will be an order of magnitude faster.