Eventually I tracked down it was because the device is domain joined and thus looks at our WSUS (SCCM) for the addon and can't find it so fails. Then I went into Add an Optional Feature, found Media Player and clicked add. To add it as a feature I first tried powershell Įnable-windowsoptionalfeature -featurename "windowsmediaplayer" -online -all and that fails with a 'can't find the feature with that name error'. We've recently deployed Windows 10 Education (1709) via SCCM and I've come across an annoying issue in that Windows Media Player is not added as a feature (and we've just found out it's a requirement of some testing software our teachers need to start using).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |