OneCore-DeviceAssociationService - Error ID 3503

Question

Hello,

Last night updated my Windows 11 to 24H2 - 26100.2454. Since then everytime when I turn off my pc or do a reboot in Event Viewer I got this error:

OneCore-DeviceAssociationService ID 3503

The Device Association Service dedected an error discovering endpoints.

Event Data

AbortingProtocolProvider Internal DAS error

ClientProcessName c:/Windows/System32/svchost.exe

ClientPid 9664

InternalError 3

Never had this error before. I've seen few other reports from people that they got that too. Wondering is this something serious? Should I worry? Does Microsoft know about it? Is this going to be fixed?

Answer 1

very bad experience today 365 chat support

Answer 2

Ran into the same issue, but I was a dummy and installed the Hyper-V platform myself, which I didn't need. So for the service problem, run the below in an admin CMD or PowerShell.

sc delete l1vhlwf

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/sc-delete

I'm going through cleaning up my mess now. I've been trying to pinpoint what has been causing weird delays and keyboard/mouse lockups, but never crashed the computer. It usually would come back.

Update: That service cleaned up fine, but the other fail persists.

Answer 3

Reporting here that I'm having the same issue. In my case I need Hyper-V

Answer 4

Hi.

I have been suffering from the same error after I updated to Windows 11 24H2.

The error seems to have something to do with "Device Association Service", so I navigated to "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\DeviceAssociationService" in regedit.exe, and found some keys(looking similar to a folder) with an uuid.

I searched the uuid entering "pairtool /enum-endpoints" in cmd.exe and got that the uuid is associated with my printer.

I guess the error occurs when I turn on or restart my computer with printer turned off.

I have reported this error through Feedback Hub.

I hope Microsoft developers could solve this bug.

Answer 5

I solve "l1vhlwf" error by turning off Windows Sandbox.