Solved Cannot click on tray notifications

Is this some known bug with some of the recent updates or the problem is just on my end(I know it was working before)

For example a run the clock app and set a timer for 5 seconds and run in
When the popup appear,I cannot click on the dismiss button nor close the popup

When I get a message from WhatsApp or a call,clicking on either of the buttons does nothing
To be able to stop the clock alarm, I have to click on the clock at the bottom right to bring the notification bar

I am using the latest win11 home version

What's else,when I check for updates and if there is some updates,I was able to select the text before to copy the KBNumber but now I cannot

I am assuming you have restarted your machine and that you have made sure you do not have an issue with your mouse.

Are you running ANY 3rd party app that alters the GUI. If so delete it, restart, and test. If that fixes the issue see if there is an update to the app.

Otherwise here are other things to try.

1. Perform a clean boot to eliminate software conflict causing the issue. If it doesn't happen in a clean boot, you have some software conflicting with Windows. Brink's procedure will help you weed out which one. Perform a Clean Boot in Windows 11 to Troubleshoot Software Conflicts Tutorial

2. Make sure you have no corrupt system files that is causing this problem. Open a command prompt as administrator and type dism /online /cleanup-image /restorehealth then restart.
When complete Open a command prompt as administrator and type sfc /scannow
Pay attention to the scan results to see if SFC found anything it could not repair

3. If neither of the above fix it See if the issue happens using another user account. If it does not, then you have corruption in YOUR user account.

4. If it DOES happen using another user account, do a Repair install Windows 11 with an inplace upgrade Repair Install Windows 11 with an In-place Upgrade

The explorer decide to crash on me and after that happen,the problem was magically fixed
Thanks anyway @glasskuter

A good indication that a restart would have fixed it.