- Dec 31, 2005
- 120
- 0
- 0
After three years of reliable performance -- always with updated Windows XP, Norton AV and Webroot Spy Sweeper active -- my Sony Viao suddenly started exhibiting the lsass.exe problem.
The following error message appears for a few seconds as Windows tries to load: "When trying to update password, this return status indicates that the value provided as current password is not correct." (I have never put in a system password. And who writes these error messages? Borat?) Then my system automatically reboots and the whole process repeats.
Symptoms like this have been broadly discussed in Windows user forums for the past few years. Could be a form of the "Sasser" virus, or simply corrupt system files. Microsoft has a fix described in their Knowledge Base that involves going into the Recovery Console from the Windows XP start-up disk.
Since my computer came with XP pre-loaded (as did most others!), I have no Windows Xp start-up disk -- only the "system-recovery" disks which would wipe out my files. Further, Microsoft specifically warns against using this recovery procedure for OEM-installed Windows.
Any suggestions, short of re-formatting the C-drive??
The following error message appears for a few seconds as Windows tries to load: "When trying to update password, this return status indicates that the value provided as current password is not correct." (I have never put in a system password. And who writes these error messages? Borat?) Then my system automatically reboots and the whole process repeats.
Symptoms like this have been broadly discussed in Windows user forums for the past few years. Could be a form of the "Sasser" virus, or simply corrupt system files. Microsoft has a fix described in their Knowledge Base that involves going into the Recovery Console from the Windows XP start-up disk.
Since my computer came with XP pre-loaded (as did most others!), I have no Windows Xp start-up disk -- only the "system-recovery" disks which would wipe out my files. Further, Microsoft specifically warns against using this recovery procedure for OEM-installed Windows.
Any suggestions, short of re-formatting the C-drive??