Edited by JCastaldi, 11 March 2006 - 10:57 AM.
Isass.exe System Error
Started by
JCastaldi
, Mar 11 2006 10:53 AM
#1
Posted 11 March 2006 - 10:53 AM
#2
Posted 11 March 2006 - 11:00 AM
Hi JCastaldi,
I'm curious to know why you posted this in the Malware forums?
Do you suspect a virus to be the cause?
Also you wrote: Isass.exe
Is that correct or could it have been lsass.exe ?
I would suggest you follow this procedure:
http://www.geekstogo...p?showtopic=138
to get XP up and running again.
After that we can see if anything needs to be cleaned out.
Regards,
I'm curious to know why you posted this in the Malware forums?
Do you suspect a virus to be the cause?
Also you wrote: Isass.exe
Is that correct or could it have been lsass.exe ?
I would suggest you follow this procedure:
http://www.geekstogo...p?showtopic=138
to get XP up and running again.
After that we can see if anything needs to be cleaned out.
Regards,
#3
Posted 11 March 2006 - 11:12 AM
Thanks for your quick response. On other forums, some have described this problem related to the Sasser worm/virus. However, I posted this not realizing what forum I was posting on--so I claim "mistake." You are right--now that I look at the message, it is lower case "l" not upper case "I".
#4
Posted 11 March 2006 - 11:21 AM
In that case I'd certainly suggest you follow the procedure to Repair the XP install.
Regards,
Regards,
#5
Posted 11 March 2006 - 11:33 AM
Install does not work. As soon as the process reaches "Installing Windows" I get the same error message, etc.
#6
Posted 11 March 2006 - 12:36 PM
Did you install or uninstall any new drivers before this started happening?
Or do you know of any reason why an important system file could have been removed? (Maybe by Antivirus or other scanner)
Regards,
Or do you know of any reason why an important system file could have been removed? (Maybe by Antivirus or other scanner)
Regards,
#7
Posted 11 March 2006 - 12:42 PM
My answer to your 2 question is No and no clue. Also, I do not know the administrator password for this computer, and thus cannot get into recovery console (which I have tried).
Edited by JCastaldi, 11 March 2006 - 12:43 PM.
#8
Posted 11 March 2006 - 12:57 PM
If you have not set a password then it will be blank (just hit Enter)
I think it's better if I hand you over to the experts on your OS.
They are much better at solving this kind of problems then I am.
Regards,
I think it's better if I hand you over to the experts on your OS.
They are much better at solving this kind of problems then I am.
Regards,
#9
Posted 11 March 2006 - 01:01 PM
Thanks for trying.
#10
Posted 11 March 2006 - 01:39 PM
Hello JCastaldi...
lsass.exe rerrors can be difficult to resolve without at least doing an in-place upgrade (Repair). We need to get you to a command prompt. Start your machine and tap the F8 key during the boot sequence to get to the Safe Mode options screen. Select the option "Safe Mode with Command Prompt" and press "Enter".
Once at command prompt, type %systemroot%\system32\restore\rstrui.exe, and press "Enter". This will start the System Restore feature. Choose a date before the problem began and Restore to that date. This may or may not resolve the problem. If not, move to the next instructions...
At the command prompt, type sfc /scannow (Note the space between sfc and /) and press "Enter". You will be asked for your installation cd, so have it handy. Wait for the scan to finish (this might take up to an hour). When it's finished, (If the machine starts) click Start then Run...type chkdsk /r (Again...note the space), and click "Ok". (If the machine still won't start, type the chkdsk /r command at command prompt and press "Enter"). Reboot when prompted (type Y and press Enter). This will run on boot-up so restart will take a while...be patient.
Let me know if you are able to complete these procedures.
wannabe1
lsass.exe rerrors can be difficult to resolve without at least doing an in-place upgrade (Repair). We need to get you to a command prompt. Start your machine and tap the F8 key during the boot sequence to get to the Safe Mode options screen. Select the option "Safe Mode with Command Prompt" and press "Enter".
Once at command prompt, type %systemroot%\system32\restore\rstrui.exe, and press "Enter". This will start the System Restore feature. Choose a date before the problem began and Restore to that date. This may or may not resolve the problem. If not, move to the next instructions...
At the command prompt, type sfc /scannow (Note the space between sfc and /) and press "Enter". You will be asked for your installation cd, so have it handy. Wait for the scan to finish (this might take up to an hour). When it's finished, (If the machine starts) click Start then Run...type chkdsk /r (Again...note the space), and click "Ok". (If the machine still won't start, type the chkdsk /r command at command prompt and press "Enter"). Reboot when prompted (type Y and press Enter). This will run on boot-up so restart will take a while...be patient.
Let me know if you are able to complete these procedures.
wannabe1
#11
Posted 11 March 2006 - 02:42 PM
First, I tried booting as you suggested but I was unable to do so, as the computer took me back to Windows Setup process I had started with the Operating System CD, which is where it hung up into a cycle where it kept repeating the lsass.exe message when I was supposed to be at the Installing Windows point. Then, in order to get out of that cycle, I canceled the Windows Setup which looks like now that caused another problem. I now get 2 messages. (1) same lsass.exe error message and (2) "Windows XP Setup--Windows cannot run under Safemode. Setup will restart now." (and then has the OK button) Also, when I put the OS CD back in, I get the same lsass.exe message, and "Insert Disk--Please insert the CD labeled Windows XP Home Edition Serice Pack 1 into your CD-ROM drive and then click OK." All I have is the SP2 disk, but I await your instructions before I do anything else.
Edited by JCastaldi, 11 March 2006 - 02:57 PM.
#12
Posted 11 March 2006 - 03:08 PM
If I understand correctly, you have started a repair installation that did not complete...correct?
If this is the case, let setup continue and see if it will complete with the disk you have. If this is not the disk that came with your machine, be sure to use the product key from your machine if asked for the key. Don't use the one for the disk unless it is the disk for your machine.
Should the repair fail again, try to access Recovery Console again. If you are able to enter the Recovery Console, let me know...either way.
Did I mention this can be a tough one to resolve?
wannabe1
If this is the case, let setup continue and see if it will complete with the disk you have. If this is not the disk that came with your machine, be sure to use the product key from your machine if asked for the key. Don't use the one for the disk unless it is the disk for your machine.
Should the repair fail again, try to access Recovery Console again. If you are able to enter the Recovery Console, let me know...either way.
Did I mention this can be a tough one to resolve?
wannabe1
#13
Posted 11 March 2006 - 03:28 PM
Somehow I got into F8 list of options, hit Safemode with Command Prompt, and got 2 messages: (1) same lsass.exe message (2) "Windows XP Setup cannot run under Safemode. Setup will restart now." (then gives me an ok button to click) which when I click it takes me back to "setup is restarting" then I get (1) lsass.exe message (2) "insert the SP1 disk", both on top of another frame which is the Windows XP installation wizard (?) which shows the re-installation hung up at "Installing Windows." Hopefully, I made this clear. Should I try installing the SP2 disk at this prompt now (since I do not have SP1 disk)?
#14
Posted 11 March 2006 - 03:30 PM
Yes, but use your product key if you are asked for one.
#15
Posted 11 March 2006 - 03:35 PM
I do not understand "product key" and where to find it.--Never mind I found it on the back of the notebook. I will proceed and let you know.
Edited by JCastaldi, 11 March 2006 - 03:42 PM.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users