Ask a question

Greg M

Unable to Install Windows Migration Tool on Windows Server 2016

Hello - 

I'm unable to install the Windows Migration Tool on a Windows Server 2016 Standard server.  The 2016 would be the source server and one of the last steps, but receiving an error message when trying to install via the GUI or PowerShell.

Tried numerous things, but it also seems to fail when running sfc /scannow or DISM /ONLINE /CLEANUP-IMAGE /restorehealth.    

Output of that is below.  CBS log is attached.

C:\Windows\System32> Install-WindowsFeature -computername mgwserver –Name Migration
Install-WindowsFeature : The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed. Error: 0x800f0831
t line:1 char:1
 Install-WindowsFeature -computername server –Name Migration
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=mgwserver}:PSObject) [Install-WindowsFeature],
   Exception
   + FullyQualifiedErrorId : DISMAPI_Error__Failed_To_Enable_Updates,Microsoft.Windows.ServerManager.Commands.AddWind
  owsFeatureCommand

 

 

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% 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.

 

 

 

C:\Windows\system32>DISM /ONLINE /CLEANUP-IMAGE /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.14393.4169

Image Version: 10.0.14393.4169

[==========================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

C:\Windows\system32>gpudate /force
'gpudate' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>gpupdate /force
Updating policy...

Computer Policy update has completed successfully.
User Policy update has completed successfully.


asked06/28/2023 18:33
50 views
Add Comment
Greg M

I was able to get past this error.  Article below was helpful.  Summary needed to clear CBS logs, attempt to install feature, determine the KB that was causing the failure from the logs, download the KB from Microsoft catalog, and install it.  Afterwards feature was able to get installed.

https://community.spiceworks.com/how_to/173479-resolve-0x80073701-error_sxs_assembly_missing

Last Activity 07/06/2023 15:18

No answers found

Add an Answer