This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 87%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hello guys!
I may need some help after endless googling for couple days.
I just couldn't fix the error when adding a new feature of .Net Framework 3.5 to my VM as follows:
The features trying to add:
.NET Framework 3.5
This virtual machine is a domain controller, and the OS version is:
Windows Server 2022 Standard 21H2 20348.1906
Error message:
The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The referenced assembly could not be found. Error: 0x80073701.
I've done the following measures but all without any luck:
This post may resolve the problem, but I couldn't identify which package to download via the CBS log. https://thatonecomputerguy.wordpress.com/2015/10/06/windows-update-fails-with-error-code-0x80073701-error_sxs_assembly_missing-solved/
The output of DISM /Online /Enable-Feature /FeatureName:NetFx3 /All:
C:>DISM /Online /Enable-Feature /FeatureName:NetFx3 /All
Deployment Image Servicing and Management tool
Version: 10.0.20348.681
Image Version: 10.0.20348.1906
Enabling feature(s) [==========================100.0%==========================]
Error: 14081
The referenced assembly could not be found.
CBS Log from trying to add features from Manage / Add Roles and Features :
2023-08-31 06:19:38, Info CBS Reporting package change completion for package: Microsoft-Windows-NetFx3-Server-OC-Package~31bf3856ad364e35~amd64~~10.0.20348.1, current: Installed, original: Installed, target: Installed, status: 0x80073701, failure source: Resolve, failure details: "(null)", client id: DISM Package Manager Provider, initiated offline: False, execution sequence: 78, first merged sequence: 78, pending decision: InteractiveInstallFailed, primitive execution context: Interactive
2023-08-31 06:19:38, Info CBS The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2023-08-31 06:19:38, Info CBS Resolve time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2023-08-31 06:19:38, Info CBS Stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2023-08-31 06:19:38, Info CBS Execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2023-08-31 06:19:38, Info CBS FinalCommitPackagesState: Completed persisting state of packages
2023-08-31 06:19:38, Info CBS Enabling LKG boot option
2023-08-31 06:19:38, Info CBS Exec: Will not run corruption repair because no store corruption found.
2023-08-31 06:19:38, Info CBS Exec: Processing complete. Session: 31054861_3083983636, Package: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.20348.1, Identifier: Windows Foundation [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-08-31 06:19:38, Info CBS Reporting capability session finalize status: 0x80073701, client id: DISM Package Manager Provider, reboot count: 0, capabilities: NetFX3~, state: Installed, ID: 31054861_3083983636, RetryID: (null), retryStatus: 0, torn state reservicing: 0x80004001, download source: 10
2023-08-31 06:19:38, Info CBS Removing the pending hard reserve adjustment for Client: DISM Package Manager Provider, Session: 31054861_3083983636
2023-08-31 06:19:38, Error CBS Failed to perform operation. [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-08-31 06:19:38, Info CBS Session: 31054861_3083983636 finalized. Reboot required: no [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]
2023-08-31 06:19:38, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x80073701]
========================
Thanks!
Regards,
Sean
Per Microsoft Community's Suggestion. I forwarded the question here.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 89%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJL%3C/text%3E%3C/svg%3E)
Hi @SeanT ,
May I know if you have any update about this question?
When running the Add Feature wizard, on the bottom of the Confirmation screen should be an option to specify an alternate source path.
Insert your install media and select the \Sources\SxS folder there.
Hi Rafael,
As I've mentioned in my post for measure #5.
I've done that for many times without luck.
Thanks!
sorry, skipped over that step in your text
If I remember it right, there was some broken install media published a while back, not sure if this the same case all over again. Try getting a refreshed install ISO, or using the Offline installer:
https://learn.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
0x80073701 = ERROR_SXS_ASSEMBLY_MISSING which means there are some system files are missing, which caused the update installation failure. You can also try a repair install by running setup.exe from the root of the install.
I wouldn't hold much hope for this, time may be better spent standing up a new one, patch fully, migrate the roles or applications over and move on.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thanks Dave!
It's kind of frustrating. I just set up this brand new fresh DC from scratch for just like a week...
I wouldn't spend any time trying to fix a this especially on a domain controller. Simplest solution is to stand up a new one for replacement.
I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
--please don't forget to upvote and Accept as answer if the reply is helpful--
Thanks Dave! I'll check health for this old AD that exists for many decades prior to totally destroy this new DC.
Sounds good, please don't forget to close up the thread here by marking answer.
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Just checking if there's any progress or updates?
--please don't forget to close up the thread here by marking answer if the reply is helpful--