WaaSMedicService problem -- Issue found by :WinRETargetingPlugin

Anonymous
2024-10-11T21:01:47+00:00

Hello,

My PC crashed frequently due to a faulty memory stick. When I used a new memory stick, the problem didn't occurred anymore. Unfortunately, the crash also occurred during the windows update after the in-place upgrade. Until now, I have been unable to download and install two important updates -- the latest cumulative update and the update from August. (Two error codes (0x80070643 and 0x800f0805) appeared alternately)

I just tried Windows update troubleshooter and get a diagnosis --

WaaSMedicService

Issue found by :WinRETargetingPlugin

Problem with BITS service : The requested service has already been started. More help is available by typing NET HELPMSG 2182

Also, I've tried to perform the second in-place upgrade but ended in failure, an error occurred during the process(More details at https://answers.microsoft.com/en-us/windows/forum/windows_10-update/error-in-downloading-windows-10-cumulative/6ec330e1-c849-4b83-97db-286974f4290a?messageId=84f7d351-326d-49d5-8c7a-d154d5a69c89)

I hope all problems can be fixed without losing any data, please help me with a targeted solution as much as possible! Thanks!

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

57 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-10-15T12:35:12+00:00

    I just got the idea from a reply on a reddit post that all the problems are most likely caused by oem1.inf(heci.inf) --

    "One thing we've had in going W10 22H2 to W11 22H2 is driver issues. If you have a device that tried and failed, you look in c:$windows.~bt\sources\panther for CompatData*.xml files. There would show if any inf files have BlockMigration="True". It's an old problem that happened with W10 build upgrades in the past with XPS and PDF writer printers. Find the inf file in c:\windows\inf and open with notepad to see what printer the file is associated with. I remove the driver as we don't use those printers anyway. The following will remove, substitute the inf file name you want to remove.

    pnputil /delete-driver oem1.inf /force"(from Windows Upgrade problems)

    Unfortunately, I was unable to uninstall it with Driver Store Explorer, and I don't know whether uninstalling using the above command will have any impact on the system. Do you have any suggestions on this?

    Could you help me check BlockMigration status?

    Was this answer helpful?

    0 comments
  2. Ramesh 181.8K Reputation points Volunteer Moderator
    2024-10-15T13:09:07+00:00

    I just got the idea from a reply on a reddit post that all the problems are most likely caused by oem1.inf(heci.inf) --

    "One thing we've had in going W10 22H2 to W11 22H2 is driver issues. If you have a device that tried and failed, you look in c:$windows.~bt\sources\panther for CompatData*.xml files. There would show if any inf files have BlockMigration="True". It's an old problem that happened with W10 build upgrades in the past with XPS and PDF writer printers. Find the inf file in c:\windows\inf and open with notepad to see what printer the file is associated with. I remove the driver as we don't use those printers anyway. The following will remove, substitute the inf file name you want to remove.

    pnputil /delete-driver oem1.inf /force"(from Windows Upgrade problems)

    Unfortunately, I was unable to uninstall it with Driver Store Explorer, and I don't know whether uninstalling using the above command will have any impact on the system. Do you have any suggestions on this?

    Could you help me check BlockMigration status?

    The Microsoft Print to PDF and XPS drivers show up as "BlockMigration" drivers on every setup log. They're false positives. They definitely don't block the setup. The OEM numbers for the two drivers vary from system to system.

    Here's the log from a Windows 11 system where the setup completed successfully.

    Image

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-10-15T13:42:52+00:00

    I was unable to uninstall oem1.inf(heci.inf) with Driver Store Explorer, and I don't know whether uninstalling using the above command will have any impact on the system. Do you have any suggestions on this?

    Was this answer helpful?

    0 comments
  4. Ramesh 181.8K Reputation points Volunteer Moderator
    2024-10-15T14:07:53+00:00

    It's oem0.inf.

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Description: Intel(R) Management Engine Interface

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Parent Device: ACPI\PNP0A08\0

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Problem Code: CM_PROB_REGISTRY (19)

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Problem Status: 0xC0000034

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Driver INF Name: oem0.inf

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Driver Package Id: heci.inf_x86_b21f869920c8c3fa

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Class Name: System

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Provider Name: Intel

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Driver Date: 10/19/2010

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Driver Version: 7.0.0.1144

    2024-10-13 19:05:38, Info [0x0808fe] MIG Plugin {ff9c714f-b864-4f43-ae39-ec07d7385abe}: Matching Device Id: PCI\VEN_8086&DEV_1C3A

    The error code 0xC0000034 denotes, "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)" ~ CM_PROB_REGISTRY - Windows drivers | Microsoft Learn. I think the DRIVERS registry hive is corrupt and that's probably why you're unable to uninstall it.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-10-15T14:20:59+00:00

    For the situation, how should I uninstall it?

    Was this answer helpful?

    0 comments