So, this one is a bit old and I had started to post on it some time ago when things became overwhelming.
This Server 2016 server is an RDSS Connection Broker and Licensing Server. It may be more prudent just to migrate those roles to another server but I'd like to try and fix it if possible.
Servicing Stack updates are current and Malicious Software Removal Tool updates continue to install but Cumulative Updates fail continuously and it appears to be something related to a .NET component that is causing it. I've performed repairs on .NET, attempted manual installation of more recent updates.
SFC /scannow
DISM /Online /Cleanup-Image /RestoreHealth
SFCFix claims that there are no issues but I did find that there are some odd .NET errors in the CBS log related to SFC /scannow.
All files linked/attached.
CBS.zip
sfcscannow.txt
This Server 2016 server is an RDSS Connection Broker and Licensing Server. It may be more prudent just to migrate those roles to another server but I'd like to try and fix it if possible.
Servicing Stack updates are current and Malicious Software Removal Tool updates continue to install but Cumulative Updates fail continuously and it appears to be something related to a .NET component that is causing it. I've performed repairs on .NET, attempted manual installation of more recent updates.
SFC /scannow
Code:
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 66% complete.
Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log. Note that logging is currently not
supported in offline servicing scenarios.
DISM /Online /Cleanup-Image /RestoreHealth
Code:
Deployment Image Servicing and Management tool
Version: 10.0.14393.0
Image Version: 10.0.14393.0
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
SFCFix claims that there are no issues but I did find that there are some odd .NET errors in the CBS log related to SFC /scannow.
Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-09-29 08:22:16.556
Microsoft Windows Server 10 Build 14393 (Updates Deferred) - amd64
Not using a script file.
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2020-09-29 08:22:47.447
----------------------EOF-----------------------
All files linked/attached.
CBS.zip
sfcscannow.txt