Device Disassociation (Unpairing) Failed. 3502 + Windows Search Indexer (Slow for the indexer to activate)

MysteriousBox said:

Issue 1
(KB5101650) (26200.8875)
Update (KB5121767) (26200.8894)

Since the above updates, my event viewer throws the following Error ;

Device Disassociation (Unpairing) Failed. 3502
[td]AepId[/td] [td]EsclUsb#{aea69b2f-e9ff-593a-aaa6-26b294dbe06c}[/td]
[td]ClientProcessName[/td] [td]C:\Windows\System32\spoolsv.exe[/td]
[td]ClientPid[/td] [td]4912[/td]
[td]AssociationError[/td] [td]0[/td]
[td]ProtocolError[/td] [td]2154037265[/td]

Does anyone know what this is?

Issue 2
Since the above update(s), the Windows Search Indexer (Service) takes significantly longer than normal to start. If I turn on the PC, it takes up to 2 full minutes for WSearch to go from Stopped to Running. This is abnormal as prior to these updates, the indexer would run almost immediately.

Click to expand...

HeavyHemi said:

It looks like your system is trying to pair or unpair with a printer, then failing with a time out. Do you have a printer or scanner connected? If so, try disconnecting them and seeing if that resolves the boot issue.

Click to expand...

• Open Settings → Bluetooth & Devices → Printers & Scanners
• Remove every printer/scanner entry, including ones marked “offline” or “driver unavailable.”
• Open Device Manager
  • View → Show hidden devices
  • Expand Printers, Print queues, Imaging devices, USB devices
  • Uninstall anything referencing any printer or scanner. Check the box to remove its driver.
• Open Services.msc. Stop Print Spooler
  1. Open Run:
  2. Type printui.exe /s /t2
  3. Remove any drivers associated with 3rd party printers/scanners. Restart.
     
     
  4. After fixing the printer subsystem, rebuild the indexer:
     1. Settings → Privacy & Security → Searching Windows
     2. Click Advanced Indexing Options
     3. Click Rebuild
     4. Is the indexer now faster?
  5. Reinstall printer to see if problem stays gone. Report back.

glasskuter said:

Note: you say the printer is old but do not give us a make/model. You need to make sure you have a good working Windows 11 driver for this printer because this procedure removes all old printer/scanner devices and drivers from your system.

If just uninstalling printer, restarting computer, and reinstalling printer does not fix it, and I don't think it will, Try this.

• Open Settings → Bluetooth & Devices → Printers & Scanners
• Remove every printer/scanner entry, including ones marked “offline” or “driver unavailable.”
• Open Device Manager
  • View → Show hidden devices
  • Expand Printers, Print queues, Imaging devices, USB devices
  • Uninstall anything referencing any printer or scanner. Check the box to remove its driver.
• Open Services.msc. Stop Print Spooler
  1. Open Run:
  2. Type printui.exe /s /t2
  3. Remove any drivers associated with 3rd party printers/scanners. Restart.
     
     
  4. After fixing the printer subsystem, rebuild the indexer:
     1. Settings → Privacy & Security → Searching Windows
     2. Click Advanced Indexing Options
     3. Click Rebuild
     4. Is the indexer now faster?
  5. Reinstall printer to see if problem stays gone. Report back.

Click to expand...

glasskuter said:

Here's the deal.
The Device Disassociation (Unpairing) Failed. 3502 error you’re seeing in Event Viewer is coming from the print subsystem, specifically spoolsv.exe, and it’s tied to a USB‑connected printer that Windows is trying—and failing—to fully enumerate or unpair. These updates did NOT cause this issue for most people.

Windows 11 25H2 updates (KB5101650 / KB5121767 July updates) changed parts of the print subsystem. Older USB printers—especially ones using legacy ESCL/USB scan protocols—may leave behind stale device entries or partially registered drivers. Windows then repeatedly tries to enumerate/unpair them, causing Event Viewer errors and sometimes delaying services like Search.

This is why a clean install of windows works as it should. You do not have any stale device entries or partially registered drivers installed at this point (if you installed your printer) The issue is not with the updates. The issue is with what shape your system was in when the updates were applied.

You do not say if it is your intention to go back to your old installation of windows or continue forward with the new install. Applying those updates to a clean system should not affect performance of this clean install. But if you want to go back to you old installation, you will have to attempt to manually clean up all the old drivers and registry entries in the print sub-system that is causing the problem in that old installation.
The reason a repair install of the old installation would not fix it is because a repair install does not clean out these erroneous entries.

Click to expand...

MysteriousBox said:

I have posted multiple times in other threads that these issues are in fact happening on a clean install. Like literally I install a fresh 25H2 after running Secure Erase on the NVMe and allow the updates to install via Windows Updates without even installing anything else except the basic motherboard drivers like Chipset and Ethernet Adapters. I never allow Windows Update to install drivers, those are always disabled via Group Policy.

Click to expand...

glasskuter said:

You said in post #5 and I quote "I have for the time being, installed a fresh ISO 25H2 26200.8037 build with no weird errors in Event Viewer."
Sorry, but you statements are contradictary.

Click to expand...

glasskuter said:

Can you tell me what version print driver you are using and whether you installed it in compatibility mode or not.

Click to expand...

MP490 series MP Driver Ver. 1.05 (Windows 10/10 x64/8.1/8.1 x64/8/8 x64/7/7 x64/Vista/Vista64/XP)​

glasskuter said:

I know you say the driver you are using works, but it has not been updated since 2015. I believe there is some disconnect between the old driver and the new changes in the print subsystem. As a long shot wild guess, completely uninstall you printer and all software that came with it (if you installed the software
ie My Imagegarden, Easy Photoprint, My Printer, MP Navigator)
Restart.

Then go through the steps I gave in my post #4 to remove all traces of the printer drivers. Restart again. You may also have to rebuild search indexing again.

Reinstall only the driver version 1.05, no software. But this time install it in compatibility mode for Windows 10 to see if it makes any difference. (Yeah I know windows 10 drivers work in 11, but I said it was a long shot guess to make the printer subsysteem see the driver differently) If you don't see windows 10 as an option try Windows 8.1)

To Install in Compatibility mode:
• Right-click the installer file (usually an .exe file) and choose Properties.
• Click on the Compatibility tab.
• Check the box for "Run this program in compatibility mode for".
• Pick the older version of Windows (Windows 8.1 64 bit or windows 10 64 bit) from the drop-down menu.
• Click Apply and then OK.
• Right-click the file again and select Run as administrator to begin the installation

Fingers crossed as this is all I got to suggest.

Click to expand...

MysteriousBox said:

but I cannot confidently say those errors are not somehow triggering the Indexer problems

Click to expand...