question

BillRyan-7769 avatar image
0 Votes"
BillRyan-7769 asked AJTek-Adam-J-Marshall commented

Error Code 0x800F0954 when is this getting fixed

Hello,

When are we going to see WSUS support Windows 10 Feature updates? Since the deployment of Windows 10, the options for feature adds has become significantly worse by not allowing systems to rely on CAB files already on the workstation to be used to add them on. For years now the error 0x800F0954 has been a plague for users trying to simply install .NET who work on a computer that uses WSUS for updates, which is a Microsoft product and it downloads updates for .NET to deploy to workstations and servers alike within its environment which it updates successfully but for some reason can't be the source for install. Since our stations, most likely the majority of people who use WSUS this will also apply to, use Group Policy to define the WSUS configuration, at reboot the manually changed policy is reset to then use WSUS again and the registry hack that is always listed as the answer does not work...

Where it is a long known issue, I want to know when it's actually going to be addressed and not by "temporarily bypassing WSUS" because that's not a fix, that's a work around using an unacceptable procedure to bypass the group policies of our organization for something as simple as an added feature. It's also impractical to do when trying to deploy a feature via power shell to 500+ stations in our organization and have to modify that many stations and then make sure they get the configuration back after. WSUS needs to support this, if features have to talk to an update server to deploy, it should be from here where all the updates are coming from. This will also significantly help in scenarios where networks get updates only from WSUS and have no internet access at the workstation level such as protected SCADA networks.

windows-10-generalwindows-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.

@BillRyan-7769
Thank you for posting on this forum.

When the error code 0x800F0954 occurred? Please consider sharing the KB number of the .net updates with us.

In addition, please help to confirm whether there are any other error code in the windows update log on the clients.

BTW, please refer to this link to get the .net framework 3.5 if you want to. There are several methods to deploy, but WSUS is not supported as a source for feature installation.

0 Votes 0 ·

Thanks for following up RitaHu-MSFT, the issue isn't just .NET, it is adding any feature that isn't natively deployed, I simply referenced .NET as it's the most common that people run into this with. For example, if I want to add any of the RSAT features, it all results in the same error code when attempting to install because we use WSUS and WSUS currently doesn't have the functionality to house and share that data directly like it does with updates which is why nearly every solution I've ever seen says to temporarily disable WSUS on the workstation and get the features directly from the Microsoft Windows Update servers which isn't always possible and may be a work around for some people but simply doesn't work as a long term solution.

I suppose what I'm really asking for is an added feature for WSUS to support hosting the source\sxs cab files for the versions of Windows we select it to support and work natively without work arounds.

0 Votes 0 ·

I totally understand that WSUS server should as the source option to get the new features, but it can't right now. We're very sorry for any inconvenience that may caused. But there are several alternative methods to help. Please refer to this link to deploy by using Group Policy.

Reference picture:
100435-33.png

In addition, I found the following error code to share with you. This may help.
100423-34.png

0 Votes 0 ·
33.png (6.0 KiB)
34.png (85.6 KiB)
AJTek-Adam-J-Marshall avatar image
1 Vote"
AJTek-Adam-J-Marshall answered BillRyan-7769 commented
· 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.

Thanks, this info is helpful in making a long term work around. It still would be nice if Microsoft actually just made this a function to add to WSUS, I simply put the share on our WSUS and set the source for the share which works in our test cases quite nicely, I'll work on the group policy change and deployment shortly.

0 Votes 0 ·

You're welcome. I agree, WSUS should handle FoDs...

1 Vote 1 ·
BillRyan-7769 avatar image BillRyan-7769 AJTek-Adam-J-Marshall ·

You're also the only one who told me how to get the Feature on Demand ISOs, I had been searching for several days online and no one pointed to Business Center or VLSC to get it, I was assuming it was an open free download for anyone and never considered looking there. Really appreciate it, thanks for scouring all the forums, you've helped me on a few now with different issues over the years!

1 Vote 1 ·
md-hare avatar image
0 Votes"
md-hare answered AJTek-Adam-J-Marshall commented

Thanks to @AJTek-Adam-J-Marshall for helping explain this error. That said, I have a much more elegant and secure fix for this problem.

As explained in other places, this caused because 3.5 .net is 'feature on demand' which is not supported by WSUS. HOWEVER, one can adjust gpos and securely publish this file to alleviate the issue without allowing external file sources for updates.

Steps:
1) Publish a share on your WSUS or fileserver with read rights for domain users. Find a Windows 10 iso, copy the two netfx3-ondemand packages from the \sources\sxs folder and save those in the new fileshare.
2) Update your GPO for Computer Configuration | Policy | Administrative Templates | System, 'Specify settings for optional component installation and component repair' and specify the directory you just used as 'Alternative source file path' and choose enable.

You mileage may vary and please test on your own.

· 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.

This works as long as you have the same version across all systems. If you end up having multiple versions, (2004, 20H2, 21H1, 21H2, 22H2), this CAN get problematic.

0 Votes 0 ·