Record a window stuck processing idea

Because I used the IE Tab plug-in in the Edge browser to open some old and stubbornly developed IE-based web pages, I really don’t know how to keep pace with the times and I’m drunk. Then for some inexplicable reason, the window got stuck, couldn't be closed, couldn't be minimized, and nothing worked. . . As shown below:

b1ca9be30ba0eacde2b3643857d8cea3.png

The key point is that the window that is so dead is maximized. After minimizing with WIN+D, activate other windows casually, this broken window will be restored again. It is really disgusting, and the process cannot be found in the task manager.

8849bbc9589acd0fd88f77f40c887eb0.png

It really affects the normal operation too much, but it is not convenient to restart or log out when I am working now. It suddenly occurred to me that since it can be minimized and activated, it should still respond to system window messages.

So I took out the programming assistant and gave it a try:

5cdc9b186dd76f8a964be5fa41a8ad4a.png

Sure enough, it has a window handle, so it can be killed if it has a handle, and a window closing message is sent to it:

f13a9683279ab7e77f24a0ea2d9e8830.png

Click "Send", and sure enough, the eyes are clean.

Generally speaking, when a window is stuck, the first thing that comes to mind is to close the window, followed by the task manager to close the process, and finally restart to solve it. This time I use a little experience in programming to solve it. Although it is simple, it is the first time to do this. It is worth recording e1bb9f07e5030996954a1cd7b1c589a3.png.

Guess you like

Origin blog.csdn.net/a18065597272/article/details/130178104