User user keys should be accessible only after the user logs in and cannot be accessed simply by resetting the user password and then logging in using the reset password (indeed, there are warnings before the user password is reset that the user will lose access to encrypted data, etc. .d.) See: http://support.microsoft.com/kb/290260
However, as soon as a user logs on to the system, it is possible for processes of other users on one computer with sufficient rights (usually granted only to administrative / system accounts) to access stored keys, for example. by entering the code into the process of the user that will be launched, I am the context of the user and, therefore, I can do everything that the user can do with the key (use it to decrypt, sign or export the key, etc.).
Enabling strong secret key protection can reduce some of these problems by requiring the user to enter a password for the key whenever it is used. Even so, it is probably still possible that the malicious code will intercept the key password.
Iridium
source share