Device Not Migrated From Previous Installation Due to Partial or Ambiguous Match [Fix]
Explore effective solutions made by professionals for you
3 min. read
Updated on
Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more
The device was not migrated due to partial or ambiguous match is a common error that usually occurs after an update. The error message tells you the exact device causing the problem. For example:
Device PCIVEN_10EC&DEV_8168&SUBSYS_84321043&REV_064&100198e&0&00E4 was not migrated due to partial or ambiguous match.
Let’s see how we can fix it:
How do you fix not migrated due to partial or ambiguous match?
1. Update the driver
1. Press Windows + R to open a Run console, type devmgmt.msc, and press OK to open the Device Manager.
2. In the Device Manager, find the device mentioned in the migration error, then double-click it to open its Properties window.
3. Go to the Events tab and check whether there is a Device not migrated event.
4. Go to the Driver tab and select Update driver.
5. Select the Browse my computer for driver software option and wait for the process to finish, then reboot your PC to fix the device that was not migrated due to partial or ambiguous match issue.
In the next guided example, you can learn the easiest method to update your drivers manually or automatically using secured tools.
Automatically install drivers
As you’ve seen, uninstalling the correct drivers is not very easy, and most likely, you will have to go to the manufacturer’s website for their newest version.
However, a way more straightforward solution is to employ a dedicated driver updating app that will automatically update all your drivers with just a few clicks.
2. Install the latest Windows updates
- Press Windows + I to open the Settings app, then choose Update & Security.
- Click the Check for updates button and let Windows install any new ones.
- Wait for the updates to be installed and restart your PC if requested. The Device was not migrated due to partial or ambiguous match issues will be fixed.
3. Run the SFC scan
- Click on the Windows Start button, type cmd, and select Run as administrator to start Command Prompt with full privileges.
- Type the following command and press Enter to start a System File Checker scan process:
sfc/scannow
- Wait until the process is over, then restart your PC if any changes are made.
4. Use the System Restore option
- Type restore point in the Search bar and click the Create a restore point option.
- Go to the System Protection tab, select System Restore and click Next.
- Select one of the restore points and click Next. Make sure you select one that was created before the update was installed.
- Click on the Finish button. Please wait for the process to finish and restore your PC to the state where it was working without any issues.
5. Update the audio driver
- Press Windows + X and select Device Manager.
- Expand the Sound category, right-click on Realtek(R) Audio, and select Update driver.
- Select Browse my computer for drivers.
- Select Let me pick from a list of available drivers on my computer.
- Pick any option that has no Realtek in the name and press Next.
6. Update the BIOS
Flashing your BIOS is complex, and you risk causing significant harm to your computer if you do not carry it out correctly.
There is no requirement for you to keep your BIOS up to date if you are not an expert user; however, if you are experiencing a hardware issue and the only way to solve it is to upgrade your BIOS, then you may be required to do so.
Thus, we recommend you check out our comprehensive guide on updating the BIOS in Windows 10 or 11 to avoid any issues.
Wrapping up
The Were not migrated from previous os installation due to partial or ambiguous device match error is usually linked to driver problems. Compatibility issues, corrupt or outdated drivers to be precise. That said, corrupt system files can also be at fault.
This problem affects various external hard drives; many reported this issue when using USB 3.0 devices. All brands can be affected by this issue, but many Seagate users reported this issue.
We hope that you managed to fix it by using one of our solutions. For any questions or suggestions, we will wait for your notes in the comments section below and get back to you as soon as possible.
User forum
3 messages