Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, August 22, 2019 3:35 PM
Hi,
We deploy Windows 10 using MDT/WDS combo. Since build 1903 we're getting an alert saying "we couldn't install some optional features". What does this error relate to as that particular code seems non-existent on Google.
We do customize the vanilla WIM from Microsoft (it's not a captured WIM) to remove some bundles features and AppX packages:
Microsoft.Microsoft3DViewer_5.1902.20012.0_neutral_~_8wekyb3d8bbwe
Microsoft.BingWeather_4.25.20211.0_neutral_~_8wekyb3d8bbwe
Microsoft.DesktopAppInstaller_2019.125.2243.0_neutral_~_8wekyb3d8bbwe
Microsoft.GetHelp_10.1706.13331.0_neutral_~_8wekyb3d8bbwe
Microsoft.Getstarted_7.3.20251.0_neutral_~_8wekyb3d8bbwe
Microsoft.Messaging_2019.125.32.0_neutral_~_8wekyb3d8bbwe
Microsoft.Microsoft3DViewer_5.1902.20012.0_neutral_~_8wekyb3d8bbwe
Microsoft.MicrosoftOfficeHub_18.1901.1141.0_neutral_~_8wekyb3d8bbwe
Microsoft.MixedReality.Portal_2000.19010.1151.0_neutral_~_8wekyb3d8bbwe
Microsoft.Office.OneNote_16001.11126.20076.0_neutral_~_8wekyb3d8bbwe
Microsoft.OneConnect_5.1902.361.0_neutral_~_8wekyb3d8bbwe
Microsoft.People_2019.123.2346.0_neutral_~_8wekyb3d8bbwe
Microsoft.Print3D_3.3.311.0_neutral_~_8wekyb3d8bbwe
Microsoft.SkypeApp_14.35.152.0_neutral_~_kzf8qxf38zg5c
Microsoft.StorePurchaseApp_11811.1001.1813.0_neutral_~_8wekyb3d8bbwe
Microsoft.Wallet_2.4.18324.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsAlarms_2019.105.629.0_neutral_~_8wekyb3d8bbwe
microsoft.windowscommunicationsapps_16005.11029.20108.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsFeedbackHub_2019.226.2324.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsMaps_2019.108.627.0_neutral_~_8wekyb3d8bbwe
Microsoft.WindowsSoundRecorder_2019.105.618.0_neutral_~_8wekyb3d8bbwe
Microsoft.Xbox.TCUI_1.23.28002.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxApp_48.48.7001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxGameOverlay_1.32.17005.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxGamingOverlay_2.26.14003.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxIdentityProvider_12.50.6001.0_neutral_~_8wekyb3d8bbwe
Microsoft.XboxSpeechToTextOverlay_1.17.29001.0_neutral_~_8wekyb3d8bbwe
Microsoft.YourPhone_2018.1128.231.0_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneMusic_2019.18111.17311.0_neutral_~_8wekyb3d8bbwe
Microsoft.ZuneVideo_2019.18111.17311.0_neutral_~_8wekyb3d8bbwe
This is what history shows, on a complete brand new machine deployed with MDT:
All replies (8)
Thursday, August 29, 2019 7:26 AM ✅Answered
Hi,
There is a GPO setting that instructs the machine to pull Optional Feature content from Windows Update directly, rather than try to obtain it from your WSUS:
Computer Configuration\Administrative Templates\System
"Specify settings for optional component installation and component repair"
You need to enable the option "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)"
This will then allow clients to communicate with WSUS as required, whilst still being able to install these annoying optional components.
Hope above information can help you.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, September 10, 2019 2:56 PM ✅Answered
I ended up embedding these optional updates into the WIM file.
Thursday, August 22, 2019 6:38 PM
Can you upload the following logs?
%WINDIR%\TEMP\DeploymentLogs
The logs of most interest for troubleshooting a failed install will be:
BDD.LOG – This is an aggregated log of all the MDT Logs.
SMSTS.LOG – This log would be used to troubleshoot Task Sequence errors.
Also note that each MDT script creates its own log files during execution (example: ZTIGather.log, ZTIDiskpart.log, ZTIDrivers.log, etc)
SCCM Admin
Monday, August 26, 2019 2:05 AM
Hi,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Farena
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tuesday, August 27, 2019 10:21 AM
The deployment summary screen does come back OK; no errors or warnings. It's only the first login after a reboot where this comes. I assume because we use WSUS and these optional features are not in the WSUS store.
There isn't a SMSTS.log file in this folder.
Tuesday, August 27, 2019 1:25 PM
If you are using MDT for OS deployment. You can refer to these logs to troubleshoot.
BDD.log. This is the aggregated MDT log file that is copied to a network location at the end of the deployment if you specify the SLShare property in the Customsettings.ini file.
LiteTouch.log. This file is created during LTI deployments. It resides in %WINDIR%\TEMP\DeploymentLogs unless you specify the /debug:true option.
Scriptname*.log. This file is created by each MDT script. Scriptname represents the name of the script in question.
SMSTS.log. This file is created by the Task Sequencer and describes all Task Sequencer transactions. Depending on the deployment scenario, it may reside in %TEMP%, %WINDIR%\System32\ccm\logs, or C:\SMSTaskSequence, or C:\SMSTSLog.
Wizard.log. The deployment wizards create and update this file.
WPEinit.log. This file is created during the Windows PE initialization process and is useful for troubleshooting errors encountered while starting Windows PE.
DeploymentWorkbench_id.log. This log file is created in the %temp% folder when you specify a /debug when starting the Deployment Workbench.
For WDS Logging you can refer to this site.
/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc730906(v=ws.10)
SCCM Admin
Wednesday, August 28, 2019 9:34 AM
Thanks. But as I said the actual deployment is 100% fine. No errors or warnings on the final summary screen.
This is outside of deployment. It's when the first user logs in that we get this warning. We don't want these optional features to even attempt to install - we haven't blocked this in MDT or WSUS.
Tuesday, September 3, 2019 1:28 PM
Thanks Farena.
Even better would be to totally prevent these 'On Demand Features' completely - I don't really want hundreds of machines going out to the internet to get them after mass deployment.
Is that possible? I tried setting it to 'Never attempt to download payload from Windows Update' but it still tries at first login and fails.