[BUG] - Stuck on "please wait for the system event notification service" when shutting down

[Muzosh]

Before continuing...

• I agree to follow Atlas' Code of Conduct
• I have searched our issue tracker to verify that the issue hasn't been reported already
• I have searched the Atlas documentation beforehand for a solution
• I am on the latest version of Atlas, and didn't do an unsupported upgrade

Description

The issue started after I installed AtlasOS. During every shutdown, I get a black screen with white text in the middle: "Please wait for the System Event Notification service".

Googling led me only to solutions that happen on Windows servers via RDP.

The screen eventually dissapears and system shutdowns, but it can take even couple of hours.

I'm at AtlasOS v0.4.0 (Windows 23H2), Windows udate and myASUS updates are up-to-date.

Steps to reproduce

Don't know how

Expected behavior

Shutdown in a matter of seconds

Actual behavior

Shutdown takes hours.

Atlas Version

Atlas v0.4.1 for Windows 10 22H2

Desktop information

• AMD Ryzen Z1 Extrem
• 16GB RAM
• AMD Radeon Graphics, automatic VRAM

Additional content

No response

[respberryx]

You said in Atlas Version that you are on v0.4.1 on Windows 22H2 but over it you said v0.4.0 on Windows 23H2? Can you specify? Regardless, the delay suggests an issue with SENS shutting down. Check the Event Viewer (Windows Logs > System) for errors related to SENS service around shutdown times. Upload the logs here.

[Muzosh]

You said in Atlas Version that you are on v0.4.1 on Windows 22H2 but over it you said v0.4.0 on Windows 23H2

The github bug maker doesn't allow me to select v0.4.0. It only redirects to some common issues which didn't include my problem.

Regardless, the delay suggests an issue with SENS shutting down. Check the Event Viewer (Windows Logs > System) for errors related to SENS service around shutdown times. Upload the logs here.

I will, thanks.

[Muzosh]

Seems like it is not as consistent as I thought. I can't replicate it right now. I will post logs if it happens again.

[Muzosh]

Okay, I checked the events during the problem occuring and I found an error with a DistributedCOM as a source:
The server {some-uuid} did not register with DCOM within the required timeout.

Could it be related to SENS?