Forum Discussion
Solved
ctrl w not working after latest update
After updating to Windows 11 (update kb5034123, linked here), ctrl + w no longer did anything. It did not matter what application I was using; it simply would not do anything. The W and ctrl keys still worked individually. I uninstalled the update, and everything was working as it should again.
I woke up to this issue today as well after allowing my computer to install this update and reboot overnight. I tried uninstalling the update but that did not work initially. However, I noticed that it started happening right after Samsung Magician started. So, I killed that process, and ctrl+w started working again! Weird. The hotkey continues to work after starting Samsung Magician again too. I'll prevent it that app from starting and see if the hotkey stops functioning next time I reboot.
I woke up to this issue today as well after allowing my computer to install this update and reboot overnight. I tried uninstalling the update but that did not work initially. However, I noticed that it started happening right after Samsung Magician started. So, I killed that process, and ctrl+w started working again! Weird. The hotkey continues to work after starting Samsung Magician again too. I'll prevent it that app from starting and see if the hotkey stops functioning next time I reboot.
sangrapura, as soon as I saw your solution, I went to see if there was an update on Samsung Magician. As soon as I updated it, the ctrl w seemed working again. I don't know what blocks it when the new update comes, but just updating Samsung Magician seems to be fixing the problem.
- This worked for me. Thank you.
- Man you saved me, I was struggling from a week, after updating Magician all working well.
I noticed the same thing on a Windows 10 computer today. CTRL-W shortcut to close open taps/windows stopped working across all apps on Windows 10 (Edge, Firefox, Adobe apps, etc.)
- Thanks for this! I had the same issue, however, when I uninstalled kb5034123 it did not fix it. Then I reinstalled kb5034123, and it was fixed. I'm glad I found your post.
- that's very strange. i hope a hotfix comes out soon because not everyone who's experiencing this will know what to do
