How to fix
OneCore-DeviceAssociationService error ID 3503
on Windows

Hello I think there is something wrong with my PC after I updated it to version 24H2. I was looking into something on the Event Viewer and noticed that there are tons of errors like OneCore-DeviceAssociationService - ID 3503. They were not present yesterday (before I updated) and now they are coming up non-stop. Is this something I should be worried about?

After upgrading to Windows version 24H2, some users have reported encountering the "OneCore-DeviceAssociationService" error with Event ID 3503 in the Event Viewer. This error is accompanied by the message: "The Device Association Service detected an error discovering endpoints." 

Event Viewer in Windows is a utility that logs system notifications, errors, and warnings. Though seeing a list of errors may raise an alarm, it should be understood that not all of them require immediate attention or signal a critical problem. Many logged errors are benign and don't impact the system's performance or functionality.

In the case of the OneCore-DeviceAssociationService error ID 3503, users have noted its appearance following system shutdowns or restarts after the 24H2 update. Despite the error log, most have observed no noticeable issues with their system's operation. This suggests that, for the majority, this specific error doesn't adversely affect daily use and can be considered non-critical.

However, if you prefer a clean Event Viewer or are concerned about potential underlying issues, you might choose to address this error. Optional instructions that could help resolve it are provided below.

The OneCore-DeviceAssociationService error ID 3503 is often linked to minor communication failures between Windows services and connected devices. It may stem from corrupted system files, outdated device drivers, or misconfigured service settings. In some cases, residual issues from the Windows 24H2 update may also contribute to the issue.

While the ID 3503 error generally doesn’t impact performance, restarting the relevant Windows services, verifying system files, or ensuring drivers are up-to-date can sometimes clear it from the logs.

For a more effective way of finding and eliminating such system errors, one can employ an automated tool like [d1] PC repair. This app is capable of finding and fixing the deep-seated problems of Windows to keep your system running efficiently without any need for manual troubleshooting.

Fix 1. Restart or set Device Association Service to Manual

The Device Association Service is responsible for managing and discovering connected devices. Restarting this service or setting it to manual startup can often resolve the error.

• Type Services in Windows search and then press Enter.
• Locate Device Association Service in the list.
• Right-click on it and select Restart - check if the problem persists.
• If it does, go to Services and double-click the Device Association Service to open Properties.
• Set Startup type to Manual.
• Click Apply and then OK.
• Restart your computer and check if the error persists.

Fix 2. Update system drivers

Outdated or corrupted device drivers can cause communication failures with Windows services. Updating your drivers ensures compatibility with the latest Windows version.

• Right-click on Start and pick Device Manager.
• Expand categories related to hardware devices (e.g., Network adapters, System devices).
• Right-click on each driver and select Update driver.
• Choose Search automatically for drivers.
• Wait till all the updates are installed.
• Once the process is finished, restart your computer to implement the changes.

Fix 3. Run SFC and DISM

Corrupted or missing system files can trigger service-related errors. Running SFC and DISM scans can repair these files.

• Type cmd in Windows search.
• Right-click on Command Prompt and select Run as administrator.
• When User Account Control window shows up, click Yes.
• Paste the following command into the new window:
  sfc /scannow
• Press Enter and wait till the scan is executed.
• Once done, run this set of commands, pressing Enter after each:
  DISM /Online /Cleanup-Image /CheckHealth
  DISM /Online /Cleanup-Image /ScanHealth
  DISM /Online /Cleanup-Image /RestoreHealth
  (Note: if you get an error executing this last command, add /Source:C:\RepairSource\Windows /LimitAccess to it and try again).
  
• Restart your computer.

Fix 4. Check for Windows updates

Microsoft usually addresses widespread issues in the next update patch, so make sure you have it installed:

• Type Updates in the Windows search bar and press Enter.
• The new window will open and you should be notified about available updates - click Install all.
• If none are available, click Check for updates, and they should be installed automatically.
• Don't forget to install all the available optional updates.
• Restart your computer to apply the updates.

Fix 5. Perform a Clean Boot

Third-party applications or services might conflict with Windows services. Performing a clean boot ensures only essential Windows services are running.

• Type msconfig in Windows search and press Enter.
• Go to the Services tab.
• Mark Hide all Microsoft services and select Disable all.
• Go to the Startup tab and click Open Task Manager.
• In the Task Manager, right-click on each of the items and select Disable, then close the Task Manager.
• Go to the Boot tab, and tick Safe Boot.
• Click Apply and OK, and restart your PC.
• To find out which app(s) is causing conflicts, enable each of the processes (or you can do it in groups), restart, and see if the problem persists. Repeat until you find the faulty app, then either update or uninstall it.

Fix 6. Reset Windows Components

Resetting key Windows components like Windows Update and Windows services can resolve persistent issues.

• Open Command Prompt as an administrator.
• Stop the BITS, Windows Update, and Cryptographic services by typing the following commands, and pressing Enter after each:
  • net stop bits
  • net stop wuauserv
  • net stop appidsvc
  • net stop cryptsvc
• To rename the SoftwareDistribution and Catroot2 folders (where Windows stores update files), type the following commands:
  • ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
  • ren %systemroot%\system32\catroot2 catroot2.old
  • regsvr32.exe /s atl.dll
  • regsvr32.exe /s urlmon.dll
  • regsvr32.exe /s mshtml.dll
  • netsh winsock reset
  • netsh winsock reset proxy
• Restart the services stopped earlier by typing the following commands:
  • net start bits
  • net start wuauserv
  • net start appidsvc
  • net start cryptsvc
• Close the Command Prompt and restart your computer, then try updating Windows again.