The preliminary analysis of the cause of Vista's crash caused by QQ

  
Since the author used VISTA, it has been tortured by Tencent QQ (hereinafter referred to as QQ)! How do you say this? In the author's memory, from the earliest Windows Vista Beta1 to Windows Vista Beta2, and even Windows Vista 5472 can not run the latest version of QQ, namely Tencent QQ 2006. For a student, most of my classmates and friends only use QQ to communicate, but I can imagine how important QQ is in my online life. But in my favorite Windows Vista, I can't use QQ to share with friends. The infinite happiness and sorrow that Windows Vista brings to me is very depressed. Although the luma qq of the java platform can simulate some of the functions of QQ, but it is not as good as Tencent QQ...

Finally, I got some inspiration in Windows Vista Pre-RC1 5536, and then I found out that QQ crashed on Windows Vista. Several reasons are shared with everyone here. At the same time, it also increased its confidence in the security of Windows Vista.

strange crashes through the front

since I landed like Windows Vista with the Administrator account has been the impact of various factors of insecurity, resulting in system crash several times to install several times, which a lot of emotion ! When I got the latest beta version of Windows Vista Pre-RC1 5536, I decided to "hear" Microsoft's security advice: log in with a normal user account and open UAC... In this latest version, I feel a more user-friendly UAC design, so It is no longer "fearful" about the troubles caused by UAC. In fact, this is no longer a problem, because the improvement of UAC has made users feel that it is not there, but the security has not diminished.

also said a bunch of nonsense, to say the following for himself encountered this strange problem: a lot of listening in on vistafans forum Friends of the altar say Windows Vista Pre-RC1 5536 running QQ, often to the fourth input Bit password, the system is blue screen... Just the latest version of QQ 2006B3 is launched, the author also installed and run with a try, but the magic happened, not only did not crash when entering the fourth password, and QQ Running in good condition, no crash symptoms! It was very gratifying at the time, I don’t know if it’s a good character. But there are also several problems: 1. Keyboard encryption can not be started; 2. Can not find the folder of user information named by their own number in the QQ directory. I intuitively feel that I should use QQ as the Administrator to solve the problem (because I am used to the ordinary user account at this time, and the user-friendly UAC design does not bring much inconvenience to myself, so I no longer use the Administrator. The account is used to log in to the system). So through the Windows Vista a convenient program to run the rights management options for QQ (Figure).
Haha, the method works, keyboard encryption can be started. Filled in the number with excitement and lost the password. However, there is no response after "Enter". If you look at the password and enter the fourth place, you can't continue to type it. Try it again... The unfortunate thing happened. Windows Vista blue screen, DUMP restarted. ......

Keyboard encryption is working? !

After restarting, try again, still using the Administrator privileges to run, the result is still blue screen, crash... After the second reboot, decided not to use the Administrator privileges to run, restore normal permissions try, this time finally He successfully broke through the fourth blockade of passwords and successfully landed in QQ. The problem is really strange. In everyone's mind, generally using the Administrator permission to run the program can achieve the "perfect" effect, but this time it can be blame, using the Administrator privileges to run the program will crash. At this point, the author suddenly noticed the problem of keyboard encryption. As shown in the figure, the keyboard encryption is not activated.

Since you suspect it is, you can't let it go! Then the author went to the forum to check some cases of crashes, and some netizens summed up the law of not crashing. From this, we can find that most users are still used to log in to the computer with the Administrator account, which can start the keyboard encryption and lead to the blue screen; and some bold users. Also suspected to be a problem with keyboard encryption, thus deleting the SYS file of the two keyboard encryption programs under the QQ directory (as shown below), so there is no crash!

keyboard encryption it really in trouble?




The theoretical analysis of the hypothesis
We all know that if you log in with the Administrator account, you can get the highest authority of the computer (this account turns off UAC by default), so it is safe. Sex is also quite high, so Microsoft does not recommend enabling this account. Suppose we log in as the Administrator account and run the QQ program. At this time, the QQ program can get the highest running permission to execute other services or programs it needs. Of course, keyboard encryption is such a program that it needs, so this is keyboard encryption. Can start smoothly. In contrast to the ordinary account, when we run QQ, Windows Vista only allows itself to allow, and no other permissions to execute other required programs, so the keyboard encryption is locked out of the authority door, which can not be allowed normally, thus appearing Error message. Of course, if we select the "Run as Administrator" option of QQ at this time, the QQ process has the highest authority, so that keyboard encryption can be run. It is worth noting that Windows Vista prevents an unsafe program from gaining the highest privilege in order to prevent the malicious selection of the "Run as Administrator" option. When we allow it to be UAC with the Administrator privilege, it will start, prompting us whether to allow this unknown. The program that may pose a security risk is allowed to obtain the highest authority, which is the perfect embodiment of UAC humanization and security.

From the above analysis, we can easily find the answer to the second question (the folder that cannot find the user information named by its own number in the QQ directory). Because we are running with a normal user account at this time, we only allow it to write data to the specified location (the specified location of the QQ user information folder is set to X:Users[username]AppDataLocalVirtualStoreProgram FilesTencentQQ X refers to the Windows Vista system disk). Of course, the problem of not being able to write data to the regular folder (X:Program FilesTencentQQ X refers to the drive letter of QQ) can be explained.
Virtual redirection is mainly used in UAC-compatible scenarios. When an old software is running in a standard user environment, UAC will automatically redirect it to another location if it needs to access a system directory and is rejected. The program thought that it had permission to access the directory. In this way, the author's strange experience is not difficult to explain: QQ under standard users can not be written to its installation directory, so other QQ number directories will be redirected, so that QQ can run normally in UAC environment. The power of virtual redirection is reflected here, so the security of Windows Vista can be further improved.


ingenious solutions presented here are two general solutions:
first very simple, normal user account login, then QQ can not get enough privileges can not run encryption keyboard program so as not to cause a system crash

second method is more thorough, that is, delete X: npkcrypt.sys and npkcusb.sys these two files in the program FilesTencentQQ (X refers to the drive letter where QQ).

Questions to date

Why is Windows Vista system not compatible with QQ keyboard encryption program?
Copyright © Windows knowledge All Rights Reserved