Win10 1709 Add feature fails with error 0x800F0954

Question

_{Wednesday, December 13, 2017 5:20 PM}

Hi there. I read earlier today about Win10 v1709 now having a built-in SSH client available (still in beta but listed in 1709) and I wanted to give that a try. I went to Settings > Manage optional features > Add a feature > OpenSSH Client (Beta). Adding the feature fails with error 0x800F0954. I've been able to find very little about that error message other than it seems to come up with version 1709 and possibly WSUS. I am trying this on Win10 Enterprise x64 v1709, domain-joined. Event Viewer does show the following:

Event 1001, Windows Error Reporting

Fault bucket , type 0
Event Name: CbsPackageServicingFailure2
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.16299.96
P2: OpenSSH-Client-Package
P3: 10.0.16299.15
P4: amd64
P5: unknown
P6: 800f0954
P7: CBS Other
P8: Absent
P9: Absent
P10: SystemSettings

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\Critical_10.0.16299.96_1f56230eb29b797f87e391de3e956ad2d3043_00000000_37aa270a

Analysis symbol:
Rechecking for solution: 0
Report Id: af3c21d3-1ced-4661-812b-60a5851ff56b
Report Status: 4
Hashed bucket:

The above location was empty, but I did find a related file in C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.16299.96_1f56230eb29b797f87e391de3e956ad2d3043_00000000_3a8821d9, shown below.

Unsure how to interpret this. Any ideas? This was a fairly recent, clean install on this PC. Thanks.

Version=1
EventType=CbsPackageServicingFailure2
EventTime=131576581677609792
ReportType=1
Consent=1
UploadTime=131576581678463065
ReportStatus=268435456
ReportIdentifier=8f8e7b14-b89a-447a-bc61-0a31cc20ea42
Wow64Host=34404
AppSessionGuid=00000ea0-0000-001e-ee8b-5a903274d301
TargetAppId=W:0006d696ff975c94d8af5ba700c4df82fb8f00000904!00007d2855c8724fae778e44462c5694084101bf0c07!TiWorker.exe
TargetAppVer=2105//02//21:00:06:22!3ae05!TiWorker.exe
BootId=4294967295
TargetAsId=6710
Response.BucketId=abb1d176db53753c078f4c72d0c5ab04
Response.BucketTable=5
Response.LegacyBucketId=1697659640554564356
Response.type=4
Sig[0].Name=Stack Version
Sig[0].Value=10.0.16299.96
Sig[1].Name=Package
Sig[1].Value=OpenSSH-Client-Package
Sig[2].Name=Version
Sig[2].Value=10.0.16299.15
Sig[3].Name=Architecture
Sig[3].Value=amd64
Sig[4].Name=Culture
Sig[4].Value=unknown
Sig[5].Name=Status
Sig[5].Value=800f0954
Sig[6].Name=Failure Source
Sig[6].Value=CBS Other
Sig[7].Name=Start State
Sig[7].Value=Absent
Sig[8].Name=Target State
Sig[8].Value=Absent
Sig[9].Name=Client Id
Sig[9].Value=SystemSettings
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.16299.2.0.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
State[0].Key=Transport.DoneStage1
State[0].Value=1
OsInfo[0].Key=vermaj
OsInfo[0].Value=10
OsInfo[1].Key=vermin
OsInfo[1].Value=0
OsInfo[2].Key=verbld
OsInfo[2].Value=16299
OsInfo[3].Key=ubr
OsInfo[3].Value=98
OsInfo[4].Key=versp
OsInfo[4].Value=0
OsInfo[5].Key=arch
OsInfo[5].Value=9
OsInfo[6].Key=lcid
OsInfo[6].Value=1033
OsInfo[7].Key=geoid
OsInfo[7].Value=39
OsInfo[8].Key=sku
OsInfo[8].Value=4
OsInfo[9].Key=domain
OsInfo[9].Value=1
OsInfo[10].Key=prodsuite
OsInfo[10].Value=256
OsInfo[11].Key=ntprodtype
OsInfo[11].Value=1
OsInfo[12].Key=platid
OsInfo[12].Value=10
OsInfo[13].Key=sr
OsInfo[13].Value=0
OsInfo[14].Key=tmsi
OsInfo[14].Value=81846
OsInfo[15].Key=osinsty
OsInfo[15].Value=2
OsInfo[16].Key=iever
OsInfo[16].Value=11.98.16299.0-11.0.48
OsInfo[17].Key=portos
OsInfo[17].Value=0
OsInfo[18].Key=ram
OsInfo[18].Value=16217
OsInfo[19].Key=svolsz
OsInfo[19].Value=222
OsInfo[20].Key=wimbt
OsInfo[20].Value=0
OsInfo[21].Key=blddt
OsInfo[21].Value=170928
OsInfo[22].Key=bldtm
OsInfo[22].Value=1534
OsInfo[23].Key=bldbrch
OsInfo[23].Value=rs3_release
OsInfo[24].Key=bldchk
OsInfo[24].Value=0
OsInfo[25].Key=wpvermaj
OsInfo[25].Value=0
OsInfo[26].Key=wpvermin
OsInfo[26].Value=0
OsInfo[27].Key=wpbuildmaj
OsInfo[27].Value=0
OsInfo[28].Key=wpbuildmin
OsInfo[28].Value=0
OsInfo[29].Key=osver
OsInfo[29].Value=10.0.16299.98.amd64fre.rs3_release.170928-1534
OsInfo[30].Key=buildflightid
OsInfo[31].Key=edition
OsInfo[31].Value=Enterprise
OsInfo[32].Key=ring
OsInfo[32].Value=Retail
OsInfo[33].Key=containerid
OsInfo[34].Key=containertype
OsInfo[35].Key=edu
OsInfo[35].Value=0
FriendlyEventName=CbsPackageServicingFailure2
ConsentKey=CbsPackageServicingFailure2
AppName=Windows Modules Installer Worker
AppPath=C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.96_none_2c40cc7f3876f2b7\TiWorker.exe
ApplicationIdentity=00000000000000000000000000000000
MetadataHash=-912272362

All replies (28)

_{Wednesday, December 13, 2017 8:00 PM}

Hello,

I have windows 10 1709 pro at home and i was able to install the feature.

you say that your computer is domain joined so maybe a group policy prevents you from installing features.

are you able to install other features just for the test?

Tomer

_{Thursday, December 14, 2017 3:39 PM}

Hmm, I have Win 10 1709 Pro, and I can't install the feature...
John

_{Thursday, December 14, 2017 3:50 PM}

Hi Momominta

I just tried your procedure, and was able to install the OpenSSH client.  BITS and the Windows Update Service (wuauserv) did not stop, but the procedure worked anyway.  My next step would have been to rename the two files and reboot, but I didn't need to.

thanks
John

_{Thursday, December 14, 2017 8:40 PM}

I'm having the same issue running Win 10 Pro 1709 joined to a domain.

_{Thursday, December 14, 2017 8:40 PM}

Hi Sir_Timbit,

Well let's try this procedure below

1.Open an elevated command prompt or windows powershell admin (winlogo + X)

2.Run the following command:

  net stop bits

  net stop wuauserv

  net stop appidsvc

  net stop cryptsvc

  ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

  ren C:\Windows\System32\catroot2 catroot2.old

  net start bits

  net start wuauserv

  net start appidsvc

  net start cryptsvc

3. Exit command prompt and check if the issue persists

Momominta

I attempted this process to no avail. Still getting the same error.

_{Tuesday, January 30, 2018 10:24 PM}

Does not fix the issue for me, and I just got done doing a clean 1709 install.

_{Friday, February 9, 2018 4:03 PM | 49 votes}

Had the same issue with clean Windows 10 Ent in domain. Here is the fix:

1. regedit

2. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

3. UseWUServer -> 0

4. net stop wuauserv && net start wuauserv from cmd

Hope this helps.

_{Wednesday, February 21, 2018 3:01 PM}

itezlo, thank you!

Your solution helped me. It seems, there are some problems with WSUS.

_{Thursday, February 22, 2018 5:18 AM}

Event Name: CbsPackageServicingFailure2

Use the timestamp of this event as an index into the CBS log (or archived piece) to find out what this was about.

Robert Aldwinckle

_{Saturday, March 24, 2018 7:24 AM}

Excellent! I was also having issues with installing this feature to a Windows domain joined computer that downloads updates from a WSUS server. Your solution was the ONLY one that fixed. Now I have direction towards the continuous errors we received against installing other optional features also.

Thanks loads!

_{Monday, April 9, 2018 1:21 PM}

I tried all sorts of stuff to fix it, and this finally did the trick. Thank you! 

_{Sunday, April 15, 2018 8:03 AM}

Had the same issue with clean Windows 10 Ent in domain. Here is the fix:

1. regedit

2. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

3. UseWUServer -> 0

4. net stop wuauserv && net start wuauserv from cmd

Hope this helps.

This is it! Changing UseWUServer -> 0 finally resolvew the issue. Thanks, Eli!

_{Wednesday, June 13, 2018 3:20 AM}

Does this 'fix' stop the use of having a WSUS server in the environment ?

_{Thursday, June 14, 2018 1:35 PM}

This is the solution we decided on, because we don't want to bypass our WSUS server. We did this in the script that we use to install the application that needs it, but probably could be added to a logon script:

Copy this folder to NETLOGON share and point to it for the DISM command:

C:\Windows\Microsoft.NET\Framework64\v3.5

dism /online /enable-feature /featurename:netfx3 /LimitAccess /source:\<domain nam>\NETLOGON\NET35

_{Thursday, July 5, 2018 8:54 AM}

This worked for me. Thanks ! 

_{Tuesday, July 17, 2018 7:14 PM | 6 votes}

I found a GPO setting that will allow you to install optional features even when on the domain without changing these Reg keys. It allow only optional features access to windows update. 

Computer Configuration > Administrative Templates > System, "Specify settings for optional component installation and component repair" Enable this and also enable the option "Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)"****

_{Thursday, July 26, 2018 9:43 AM}

This answer solved the issue for me - and it will not bypass WSUS in general. Thanks to speet42!

_{Tuesday, August 14, 2018 7:09 PM}

Had the same issue with clean Windows 10 Ent in domain. Here is the fix:

1. regedit

2. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

3. UseWUServer -> 0

4. net stop wuauserv && net start wuauserv from cmd

Hope this helps.

Perfect!! Thanks!!

_{Tuesday, September 4, 2018 9:36 PM}

Thank you. This is the only thing that worked for me.

_{Wednesday, October 3, 2018 9:41 AM}

Thanks, also worked in 1809

_{Friday, October 5, 2018 4:50 PM}

Had the same issue with clean Windows 10 Ent in domain. Here is the fix:

1. regedit

2. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

3. UseWUServer -> 0

4. net stop wuauserv && net start wuauserv from cmd

Hope this helps.

This works! great!

_{Friday, October 19, 2018 5:57 AM}

Itezlo, Your solution fixed my issue for me! 

Thanks

_{Wednesday, October 31, 2018 5:52 PM | 1 vote}

Had the same issue with clean Windows 10 Ent in domain. Here is the fix:

1. regedit

2. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

3. UseWUServer -> 0

4. net stop wuauserv && net start wuauserv from cmd

Hope this helps.

It worked for me too. stand alone windows 10 computer. Thank you

_{Friday, November 16, 2018 1:35 PM}

TNX, work fine.

_{Sunday, November 18, 2018 6:00 PM}

Had the same issue with clean Windows 10 Ent in domain. Here is the fix:

1. regedit

2. HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

3. UseWUServer -> 0

4. net stop wuauserv && net start wuauserv from cmd

Hope this helps.

it works...thnksD!!!!

_{Thursday, June 20, 2019 11:04 AM}

You Level is GOD? thanks!

_{Monday, October 7, 2019 11:25 PM}

What a relief! This worked perfectly! Thank you so much!!

_{Tuesday, October 15, 2019 10:53 PM}

THANK YOU!!! you are amazing!!  Works like a charm!