Summary:


Windows Server Migration failed in prepare Stage due to dism driver  injection failure  with  Error Code: 0x800703F1



Problem:


Customer reported issue https://rackware.freshdesk.com/a/tickets/11361 with the below Details 



Job is getting failed at preparation steps on one of the windows servers. Log is attached .kindly look into it and advise.

 

RSP_SYNC_ERROR  SYNC_ERROR_PREPARE  STATUS_ERROR

Details: dism injection of Y:\windows\Temp\RackWare-driverstore\vmware\mouse\vmmouse.inf failed:  Deployment Image Servicing and Management tool Version: 10.0.15063.0  Image Version: 10.0.17763.1697  There was a problem opening the INF file. Y:\windows\Temp\RackWare-driverstore\vmware\mouse\vmmouse.inf Error: 0x800703F1.  Error: 2  No driver packages were found on the specified path.  Verify that the driver .INF files are in the specified location and try the command again. An error occurred closing a servicing component in the image.  Wait a few minutes and try running the command again.  The DISM log file can be found at Y:\windows\Temp\RackWare-winutil\var\log\dism.log (2)

The following file systems were synced:

    C:

    EFI system partition

    Recovery

    F:

    E:

jobid file: /var/log/rackware/by-jobid/000000000001473d.log

 





Environment:


Source : Hyper V

Target  : Vmware 

RMM   : 7.4.0.583

Sync Type : Direct sync 

Windows version : 2019



Root Cause Analysis :



Here is a summary of the Root cause  analysis of this failure by RackWare's engineering team:

Windows uses a component called "dism" to inject drivers for hardware. When dism attempts to install the drivers for the hardware for the target machine into this copy of Windows, dism fails and reports the error code 0x800703f1.

Searches for this specific error code indicate that this is usually due to a problem with Windows Update, in some cases due to partially installed, but failed, updates.

We also observed on the source machine that Windows Updates have not been installed since a failed update in March of this year.




Possible/Recommended  Solutions:



Rackware Recommended that it is likely that if the issue with Windows Update can be resolved on the source machine, then the dism component will likewise also be fixed so that it no longer reports that error when attempting to install hardware drivers for the VMware target machine.