Answered by:
Windows 10 1607 to 1903 upgrade

Question
-
Hello all,
We are upgrading from windows 10 1607 to 1903. After the upgrade all the windows inbuilt applications are back?
we are deploying through SCCM task sequence.
Any thought or suggestions?
Regards
EDGE
Thursday, October 3, 2019 9:56 PM
Answers
-
Hi,
Hope things are going well. Here are some articles for future benefit:
OSDBuilder
How to keep apps removed from Windows 10 from returning during an update
Thanks for your time.
Best regards,
SimonPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marked as answer by DJ3094 Wednesday, February 5, 2020 8:47 PM
Monday, October 14, 2019 6:05 AM
All replies
-
This behavior is fixed in later versions of Windows 10, but if you're coming from 1607, you'll have to remove the apps again during the the post-processing phase of the feature update task sequence (unless you recreate your upgrade media with the apps already removed). See here for details:
Edit: Actually, it looks like you can use the method in that doc for 1607, but you'll have to create your own registry keys:
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/888#issuecomment-395231486
https://ccmcache.wordpress.com/ | @kevmjohnston
- Proposed as answer by Simon RenMicrosoft contingent staff Friday, October 4, 2019 3:12 AM
- Edited by KevinMJohnston Monday, October 7, 2019 2:25 PM
Friday, October 4, 2019 12:47 AM -
Hi EDGE,
Please use DISM.exe tool or the DISM cmdlets in Windows PowerShell to remove the apps after the upgrade task to have a try.
This is a known issue that was fixed in Windows 10, version 1803. When you update a computer running Windows 10, version 1607, 1703 or 1709, you might see provisioned apps that you previously removed return post-update. The apps might reappear if you removed the packages in one of the following ways:
If you removed the packages while the wim file was mounted when the device was offline.
If you removed the packages by running a PowerShell cmdlet on the device while Windows was online. Although the apps won't appear for new users, you'll still see the apps for the user account you signed in as.
When running a previous Windows 10 version, to prevent these apps from reappearing at the next update, manually create a registry key for each app to tell Windows not to reinstall or update that app the next time Windows is updated, then update the computer.
For more detailed information, please refer to official article: How to keep apps removed from Windows 10 from returning during an update
Hope my answer could help you. Thanks for your time.
Best regards,
Simon RenPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Proposed as answer by Simon RenMicrosoft contingent staff Friday, October 4, 2019 3:12 AM
Friday, October 4, 2019 3:12 AM -
This behavior is fixed in later versions of Windows 10, but if you're coming from 1607, you'll have to remove the apps again during the the post-processing phase of the feature update task sequence. See here for details:
Edit: Actually, it looks like you can use the method in that doc for 1607, but you'll have to create your own registry keys:
https://github.com/MicrosoftDocs/windows-itpro-docs/issues/888#issuecomment-395231486
https://ccmcache.wordpress.com/ | @kevmjohnston
Thanks Kevin, I do remember this when working with previous client, we have added those reg keyson 1709 upograde. I checked the regkeys and there are for 1709, I have to make my own regkeys the 2nd link does not have any info.
can you please guide me.
EDGE
Friday, October 4, 2019 1:22 PM -
Hi EDGE,
Thanks Simon, If i remove apps from wim then it will be custom wim file. Can we create upgrade package in SCCM with custom wim file, I read we cannnot use. could you please confirm.
Please use DISM.exe tool or the DISM cmdlets in Windows PowerShell to remove the apps after the upgrade task to have a try.
This is a known issue that was fixed in Windows 10, version 1803. When you update a computer running Windows 10, version 1607, 1703 or 1709, you might see provisioned apps that you previously removed return post-update. The apps might reappear if you removed the packages in one of the following ways:
If you removed the packages while the wim file was mounted when the device was offline.
If you removed the packages by running a PowerShell cmdlet on the device while Windows was online. Although the apps won't appear for new users, you'll still see the apps for the user account you signed in as.
When running a previous Windows 10 version, to prevent these apps from reappearing at the next update, manually create a registry key for each app to tell Windows not to reinstall or update that app the next time Windows is updated, then update the computer.
For more detailed information, please refer to official article: How to keep apps removed from Windows 10 from returning during an update
Hope my answer could help you. Thanks for your time.
Best regards,
Simon Ren
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.EDGE
Friday, October 4, 2019 1:23 PM -
Use PowerShell to find the package names. Example:
Get-AppxProvisionedPackage -Online
Then, using the template provided in the doc for 1709, replace the package names in the registry keys with the ones from 1607
https://ccmcache.wordpress.com/ | @kevmjohnston
Friday, October 4, 2019 4:25 PM -
You can use a custom, serviced WIM, you just can't use a custom sysprepped/captured WIM. Many people in the SCCM/MDT/OSD community are now using OSDBuilder for this purpose. You should check it out:
https://osdbuilder.osdeploy.com/
https://ccmcache.wordpress.com/ | @kevmjohnston
Friday, October 4, 2019 4:28 PM -
Hi EDGE,
Thanks for your reply. I concur with Kevin here.
We can use the PowerShell module OSDBuilder to configure the Operating System, it can then be imported in MDT or SCCM and used like any other OS Deployment. This includes being able to use in an Upgrade Task Sequence, which you cannot do with a Captured Image.
Please refer to: OSDBuilder
Thanks and regards,
SimonPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Monday, October 7, 2019 3:18 AM -
Hi,
May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Thanks and regards,
SimonPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Wednesday, October 9, 2019 2:36 AM -
Hi,
May we know the current status of the problem? Or is there any other assistance we can provide?
If there are no other questions, would you please help close this case? Thanks for your time.
Thanks and regards,
SimonPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.Friday, October 11, 2019 3:09 AM -
Hi,
Hope things are going well. Here are some articles for future benefit:
OSDBuilder
How to keep apps removed from Windows 10 from returning during an update
Thanks for your time.
Best regards,
SimonPlease remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.- Marked as answer by DJ3094 Wednesday, February 5, 2020 8:47 PM
Monday, October 14, 2019 6:05 AM