Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You Cannot Decrypt Files After You Reset Your Password with a Password-Reset Disk
Article ID: 308273 - View products that this article applies to.
This article was previously published under Q308273
After you reset your local computer account password by using a password-reset disk, you may be unable to decrypt encrypted files or folders.
NOTE: If you later remember the original password, you can decrypt the encrypted data.
This behavior can occur if the following scenario is true:
To resolve this problem, obtain the latest service pack for Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
322389This update is available on the Microsoft Windows Update Web site.
(http://support.microsoft.com/kb/322389/EN-US/ )How to Obtain the Latest Windows XP Service Pack
Release Date: October 25, 2001
Download the "Windows XP Update Package, October 25, 2001" now
Collapse this imageExpand this image
For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file. The English-language version of this fix should have the following (or more recent) file attributes:
(http://support.microsoft.com/kb/119591/EN-US/ )How to Obtain Microsoft Support Files from Online Services
Date Time Version Size File name Platform ---------------------------------------------------------------------- 21-Sep-2001 21:40 5.1.2600.14 653,824 Lsasrv.dll i386 21-Sep-2001 21:40 5.1.2600.14 2,081,280 Lsasrv.dll Itanium 64-bit
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows XP Service Pack 1.