Win Server 2019 (17733) - Adding an optional feature from GUI fails with unhelpful error message

%3CLINGO-SUB%20id%3D%22lingo-sub-271367%22%20slang%3D%22en-US%22%3EWin%20Server%202019%20(17733)%20-%20Adding%20an%20optional%20feature%20from%20GUI%20fails%20with%20unhelpful%20error%20message%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271367%22%20slang%3D%22en-US%22%3E%3CP%3EAttempting%20to%20add%20an%20optional%20feature%20in%20Windows%20Server%202019%20using%20the%20GUI.%20I%20get%20to%20the%20%22Manage%20optional%20features%22%20page%20in%20Settings%20and%20click%20on%20'Add%20a%20feature'.%20It%20fails%20with%20another%20non-obvious%20error%20as%20shown%20here%3A%3C%2FP%3E%3CP%3E%3CIMG%20src%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fgetfile%2F1347477%22%20border%3D%220%22%20alt%3D%22%22%20%2F%3E%3C%2FP%3E%3CP%3EI%20can't%20help%20but%20ask%3A%20did%20anyone%20actually%20test%20these%20kinds%20of%20features%20before%20this%20build%20was%20released%3F%20It%20seems%20to%20me%20that%20these%20kinds%20of%20errors%20just%20should%20not%20happen%20-%20the%20installer%20really%20ought%20to%20be%20able%20to%20give%20Enterprise%20Admin%2C%20running%20on%20the%20forest%20root%20DC%2C%20adequate%20access%20to%20enable%20simple%20settings%20to%20be%20updated.%20And%20when%20they%20do%20crop%20up%20(I%20know%20builds%20can%20be%20semi-broken%20-%20the%20joys%20of%20pre-release%20testing)%2C%20surely%20the%20simple%20things%20are%20tested%20and%20the%20build%20not%20released%20if%20these%20simple%20things%20fail.%20And%20where%20there%20is%20either%20a%20workaround%20or%20a%20known%20issue%20-%20it%20should%20be%20noted%20in%20the%20release%20notes.%20In%20my%20environment%2C%20this%20build%20is%20just%20not%20ready%20for%20prime%20time.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-271367%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGeneral%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

Attempting to add an optional feature in Windows Server 2019 using the GUI. I get to the "Manage optional features" page in Settings and click on 'Add a feature'. It fails with another non-obvious error as shown here:

I can't help but ask: did anyone actually test these kinds of features before this build was released? It seems to me that these kinds of errors just should not happen - the installer really ought to be able to give Enterprise Admin, running on the forest root DC, adequate access to enable simple settings to be updated. And when they do crop up (I know builds can be semi-broken - the joys of pre-release testing), surely the simple things are tested and the build not released if these simple things fail. And where there is either a workaround or a known issue - it should be noted in the release notes. In my environment, this build is just not ready for prime time. 

0 Replies