OneCore DeviceAssociationService 3503 (Windows 11 24H2)

Winback · Oct 19, 2024

Hello,
Since updating the 24H2 via Windows Update, I get two errors every time I shut down my PC.
Does one of you have the same symptom ?
On the other hand, Windows works perfectly well when it's turned on.
I just get these two errors at shutdown. I didn't have this on version 23H2.

Royce · Oct 21, 2024

I have noticed this for a while on my PC. My guess is that the NIC is getting terminated before the service that monitors it, as on mine the error occurs in the midst of DHCP events.

I have been on 24H2 since the pre-release. Those errors do not seem to indicate any true failure.

Winback · Oct 21, 2024

That's a good thing. It's reassuring if you get the same thing.
And indeed, despite these two PC shutdown errors, there doesn't seem to be any problem getting Windows to work properly. Perhaps a patch will be released soon.

Royce · Oct 21, 2024

I would speculate that it is the device driver not handling the shutdown gracefully, and the MS service just noticing. My NIC is the onboard Realtek 2.5Gb on AsRock with an AMD CPU

Winback · Oct 23, 2024

You're probably right.
I simply have an Asus H410M-A (Realtek RTL8111H)
Hoping for a fix soon.

Vrekman · Dec 9, 2024

Hi, I got 4 of those messages and yes Realtek 2.5Gb + Realtek 1Gb on AsRock with an AMD CPU user too.

Marcus Vinicus · Dec 14, 2024

I've had this same issue for a while now, like others only at shutdown. It is the actually the first one for me with 24H2. I have found what was causing the error messages in the Event Viewer.

The error message was probably the same as what others have been getting. "Device Association Service detected an endpoint discovery failure."
What I discovered was that the WiFi in the computer wasn't fully configured because I don't use it so didn't bother to set it up. There were drivers installed for it in the Device Manager. So, I disabled WiFi in Windows 11, and this caused the OS to uninstall the drivers.

After a reboot the error messages in the Event Viewer have stopped. It wasn't a fatal error because it wasn't causing any crashes or BSODs. The issue has been reported to MS via the Feedback Hub by numerous users.

Rick V · Jan 1, 2025

Not at all related to a device driver. It appears to be a service dependency/timing issue.

What did the trick for me was setting the "Device Association Service" service from "Automatic" to "Automatic (Delayed Start)"

Rick

Coolmistry · Jan 1, 2025

I have those problem few days ago and the issues is gone in my event viewer.

Let leave Device Association Service alone in your Windows Services.
I just found out what issues is my Wi-Fi printer svchost.exe and spool.exe.

So, I have try uninstalling printer driver and full clean and try again reinstalling latest driver.
It fixes my issue and no more error in my event Id.
Have a look your event id > detail see what your issues?

Rick V · Jan 1, 2025

Coolmistry said:
I have those problem few days ago and the issues is gone in my event viewer.
View attachment 120791

Let leave Device Association Service alone in your Windows Services.
I just found out what issues is my Wi-Fi printer svchost.exe and spool.exe.
View attachment 120792
View attachment 120793
So, I have try uninstalling printer driver and full clean and try again reinstalling latest driver.
It fixes my issue and no more error in my event Id.
Have a look your event id > detail see what your issues?

I get the same details for my Hyper-V VMs without any installed printers, scanners, or intrinsic WiFi configuration so if Coolmistry's solution doesn't work, give delaying the service start a try.

Coolmistry · Jan 1, 2025

Rick V said:
I get the same details for my Hyper-V VMs without any installed printers, scanners, or intrinsic WiFi configuration so if Coolmistry's solution doesn't work, give delaying the service start a try.

Yeah, I have tried to change delay in my service, but it issues still there.

Rick V · Jan 2, 2025

I stand corrected. I should have paid better attention to the original post and done a more thorough test sequence. These 3503 errors come at shutdown, NOT STARTUP.

Thus, delaying service startup does nothing. I started seeing the 3503's again even with "Automatic (Delayed Start)" so I did everything step-by-step with a several-minute pause between logoff, shutdown, startup, and logon. The event log showed the 3503's near the end of system shutdown meaning "Device Association Service" was reporting failures to connect to the spooler, etc. because they were already stopped and DAS was still up and polling.

Setting "Device Association Service" to "Manual" isn't easy as it sets itself back to "Automatic" on its way down. Best I can do is kill the PID running the service and set the service to "Disabled". Tried "Manual" after a "Disabled" reboot and something set it back to "Automatic" the next reboot. Keeping at "Disabled" for the moment and seeing what functionality I lose.

Will advise when I have more to share.

Rick

LM2007 · Jan 29, 2025

Rick V said:
I stand corrected. I should have paid better attention to the original post and done a more thorough test sequence. These 3503 errors come at shutdown, NOT STARTUP.

Thus, delaying service startup does nothing. I started seeing the 3503's again even with "Automatic (Delayed Start)" so I did everything step-by-step with a several-minute pause between logoff, shutdown, startup, and logon. The event log showed the 3503's near the end of system shutdown meaning "Device Association Service" was reporting failures to connect to the spooler, etc. because they were already stopped and DAS was still up and polling.

Setting "Device Association Service" to "Manual" isn't easy as it sets itself back to "Automatic" on its way down. Best I can do is kill the PID running the service and set the service to "Disabled". Tried "Manual" after a "Disabled" reboot and something set it back to "Automatic" the next reboot. Keeping at "Disabled" for the moment and seeing what functionality I lose.

Will advise when I have more to share.

Rick

I have the same message or problem. Have you encountered any problem after disabling?

Rick V · Jan 29, 2025

No issues with disabling EXCEPT you can't pair new Bluetooth devices. I added a headset a while back and I first had to enable/start the DeviceAssociationService service then find/pair my new Bluetooth headset then I Disabled the service and killed the service's PID (else it will set it back to Automatic at normal termination). Able to connect to the headset after all this. All DAS does, in my opinion, is do an open search for available devices.

thinker · Jan 30, 2025

Happen at shutdown or reboot

Last boot time:

Get-CimInstance -ClassName win32_operatingsystem | select csname, lastbootuptime

Alway happen from last shutdown, resart

OneCore DeviceAssociationService 3503 (Windows 11 24H2)

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

New member

My Computer

Semper paratus

My Computers

Member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computer

Member

My Computer

Member

My Computer

Member

My Computer

Well-known member

My Computer

Similar threads