Remember to develop a lock keyboard and Task Manager applet experience

Recently, there is a new demand, the customer computer boot needs to display a full screen interface, and force the user to click on the consent before exiting, to lock the keyboard, lock Ctrl+atl+del to prevent the task Manager to start. Lock the keyboard with low-level keyboard hooks, but Ctrl+atl+del can not lock, in the Internet to find a way to modify the registry, the debug version runs well, the hearts of joy. However, when you are ready to package the program only to find that release version does not work, and then debug under release, found running to write the registry to prohibit task Manager, the program automatically shuts down. At first thought is a procedural problem, hurriedly from the procedure to find the problem, the result is not obtained, finally suddenly think of 360 security guards shut down, after the program is running normally. Did 360 intercept it? But why is the debug version okay? The reason has not been found. But later thought will 360 shut down and then compile release version of the program, at this time the release version of the compilation is normal, and restart 360 security guard, release version can also run normally. The problem is solved! But the release version of the write registry to prohibit the operation of the task Manager is why the behavior is captured by 360 security guards and banned is still a mystery!

The Disable Task Manager method is for Software\\microsoft\\windows\\currentversion\\policies\\system under registry HKEY_CURRENT_USER Writes the DWORD value of DisableTaskMgr to 1. Delete the disabletaskmgr when it is enabled.

Remember to develop a lock keyboard and Task Manager applet experience