There are legitimate reasons this can happen.įor example, if the program you’re using is doing some very long, CPU-intensive calculation - say a video-editing program performing some operation on a large video or a spreadsheet performing a lengthy calculation - it might not respond in a timely fashion. If the program never comes out of that state, we also call it hung, as in hung up on something. When Windows asks a program to do something like take a keystroke or close itself, and the program fails to acknowledge the request within a certain amount of time, the program is classified as not responding, and Windows indicates that in the title bar of the program. If you click on the Close Program “X” on a program’s window and the program doesn’t acknowledge it, it’s not responding. If you type a key and the program you’re using doesn’t take it because it’s too busy doing something else, that’s not responding. Windows expects programs to respond to its requests in a timely fashion. Programs are expected to respond to Windows ![]() ![]() This can be due to legitimate delays, if the program is busy working, or to errors like a programming bug, design error, hardware problem, malware, and more. “Not responding” happens when a program stops interacting with Windows properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |