Windows Server Summit 2024
Mar 26 2024 08:00 AM - Mar 28 2024 04:30 PM (PDT)
Microsoft Tech Community
LIVE
SOLVED

Installation of .net Framework 3.5 on build 17713 fails

Copper Contributor

I am using the following commands to install .Net Fw 3.5 on Windows server 2019 Insider preview build 17713

 

DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3ServerFeatures

DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3

 

I am unable to successfully execute the second command. Please find attached the logs from C:\windows\logs\cbs and C:\windows\logs\dism

 

Could someone please tell me whats wrong here?

 

Regards,

Kiran Hegde

11 Replies

Hello,

 

You should try with DISM, in my lab worked.

 

DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3 /Source:D:\sources\sxs

DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3ServerFeatures /Source:D:\sources\sxs

 

 

I have the same issue.
The installation failed using DISM, here is the error messages from the dism.log
2018-08-18 16:57:17, Error DISM DISM Package Manager: PID=5404 TID=4144 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0950)
2018-08-18 16:57:17, Error DISM DISM Package Manager: PID=5404 TID=4144 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x800f0950)
2018-08-18 16:57:17, Error DISM DISM Package Manager: PID=5404 TID=4144 Failed ProcessChanges. - CPackageManagerCLIHandler::Private_ProcessFeatureChange(hr:0x800f0950)
2018-08-18 16:57:17, Error DISM DISM Package Manager: PID=5404 TID=4144 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0950)
2018-08-18 16:57:17, Info DISM DISM Package Manager: PID=5404 TID=4144 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-08-18 16:57:17, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950
best response confirmed by Mary Hoffman (Microsoft)
Solution

Kiran, you should use the /source:<drive>:\sources\sxs as Ante points out.  If you don't use this, DISM will check WU, which does not have the package for a pre-release build.

Hello,

Where will i get the contents of the sxs directory from?  I am using an automated procedure to setup my Operating system environments. This involves absolutely no manual intervention whatsoever.

In a case like this, how can i ensure that the sxs directory is present?

 

Shoudn't this be available on WU? It works absolutely fine on W2k16 but not here.

 

Regards,

Kiran Hegde

The sxs directory is on the OS iso media.  So, you would need to have that shared on a network share or available locally on the system that is installing .Net.  Once the OS is released officially, this will be on WU.

I used DISM /Online /NoRestart /Enable-Feature /all /FeatureName:NetFx3 /Source:D:\sources\sxs and worked.

/all helps to install all required features

Works for me thx!

@Brent Forman This was the fix for me as well thanks

DISM worked for me. I had to add /all after /enable-feature.
1 best response

Accepted Solutions
best response confirmed by Mary Hoffman (Microsoft)
Solution

Kiran, you should use the /source:<drive>:\sources\sxs as Ante points out.  If you don't use this, DISM will check WU, which does not have the package for a pre-release build.

View solution in original post