question

Daniel-7846 avatar image
0 Votes"
Daniel-7846 asked Daniel-7846 commented

Specify source service for specific classes of Windows Updates breaks installation of .net 3.5, languages, optional features...

Hi,

Since configuring the new Windows Update Policy setting "Specify source service for specific classes of Windows Updates" I am experiencing issues installing certain windows features.

.net 3.5 framework fails with 0x800f0950
languages fail with 0x800f0954

It can temporarily be solved by changing the data of SetPolicyDrivenUpdateSourceForQualityUpdates from 1 to 0, basically telling the client to download and install quality updates from microsoft update instead of WSUS, which is obviously not what I want.

So it looks like pointing SetPolicyDrivenUpdateSourceForQualityUpdates to WSUS, causes the setting Specify settings for optional component installation and component repair to no longer work.

Can this be fixed somehow?



windows-group-policywindows-server-update-services
· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Is it possible to forward this issue to a Microsoft employee directly? I think it is a pretty severe bug that should be fixed in a timely manner and it is also pretty easy to reproduce.

0 Votes 0 ·

Anyone know if this is still an issue?

0 Votes 0 ·

This issue is still not solved.

0 Votes 0 ·
AJTek-Adam-J-Marshall avatar image
0 Votes"
AJTek-Adam-J-Marshall answered Daniel-7846 edited

Do you have "Do not allow update deferral policies to cause scans against Windows Update" enabled? If so, set it to Not Configured.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for your reply. In the past, before playing around with the new setting "Specify source service for specific classes..." it has always been set to "disabled". In order for the new setting to work at all, I had to change it to "not configured", otherwise it did not have any effect at all. Basically I am only pointing the driver and firmware updates to "Windows Update", the other sources are set to WSUS.

0 Votes 0 ·
AJTek-Adam-J-Marshall avatar image
0 Votes"
AJTek-Adam-J-Marshall answered Daniel-7846 commented

This is where I got the info from. I haven't read it all, but it was released yesterday by Aria.
https://techcommunity.microsoft.com/t5/windows-it-pro-blog/why-you-shouldn-t-set-these-25-windows-policies/ba-p/3066178

You may find the reason in this link

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I disabled all unnecesarry windows update policies and configured only the bare minimum. As soon as I set SetPolicyDrivenUpdateSourceForQualityUpdates to 1, the error comes back. Therefore I am quite sure, that this problem has been introduced with the new windows update policies. Hope that can be fixed in the near future.

0 Votes 0 ·
LimitlessTechnology-2700 avatar image
0 Votes"
LimitlessTechnology-2700 answered Daniel-7846 commented

Hello Daniel,

Can you check the next thread, it may give you the solution and explanation of the error for .NET error related to the Developer Mode: https://social.msdn.microsoft.com/Forums/en-US/44f648dd-e1cd-42a9-91de-29d3e654459d/activating-developer-mode-error-code-0x800f0950?forum=windowsgeneraldevelopmentissues

All in all I would suggest for both issues to enable the next policy as it would be required for certain updates and downloads not supported by WSUS:

Enable download of “Optional features” directly from Windows Update:

Open the group policy editor on your domain
Create a new GPO, or modify an existing one. Make sure it applies to the computers you’d like
Navigate to “Computer Configuration”, “Policies”, “Administrative Templates”, and then “System”.
Double click or open “Specify settings for optional component installation and component repair”
Make sure “Never attempt to download payload from Windows Update” is NOT checked
Make sure “Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)” IS checked.
Wait for your GPO to update, or run “gpupdate /force” on the workstations.



--If the reply is helpful, please Upvote and Accept as answer--

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

Those settings are already set. As I mentioned above, they are ignored as soon as SetPolicyDrivenUpdateSourceForQualityUpdates is pointed to WSUS.

167235-image.png



0 Votes 0 ·
image.png (10.6 KiB)
skay-9803 avatar image
0 Votes"
skay-9803 answered Daniel-7846 commented

Same problem here, highly disappointed the issue has not been acknowledged by Microsoft...

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Yes, it is getting ridiculous. This issue has existed for over a year now.

0 Votes 0 ·