HP Pavilion+XP Update+blaster=totally crashed

  • Thread starter Thread starter ericswan
  • Start date Start date
E

ericswan

Long story short: Firewall installed. XP Service Pack 1a
downloaded and installed 8/10. 8/11 RPC/blaster worm
symptoms appear. By 8/12 machine will no longer boot XP at
all.

Machine currently boots XP load screen, message appears
saying:
"isass.exe System Error
When trying to update a password, this return
indicates that the value provided as the current password
is not correct."

Machine will then shutdown and reboot constantly.

I am unable to start Windows, unable to start in Safe mode
and have been unable to access the Recovery Console
because the system asks for an administrative password,
which I don't know because I never entered one. Merely
pressing return doesn't work either.

Running the HP System recovery program for a non
destructive recovery works until the machine reboots
Windows and then the same scenario described above takes
place.

I have read other HP Pavilion owners having similar
problems after installing the Service pack/Security
Patch.HP had a bulletin on their website noting problems,
but issues were not spelled out.

Calls to Microsoft tech support got me connected to
someone with admittedly no knowledge of Windows and the
promise of a call back, 3 days ago.

Calls to HP Tech support yielded a $30 charge for advice
that I already knew and did't help.

Anyone have any clue how I can get into Windows XP and
save my data or do I just give up and go buy a Mac G4??!!

Any advice appreciated as well as any tips on how to do a
search on this forum.
 
Hi Eric,

if you feel this is blaster related you might try calling the free virus
support line at 866-PC-SAFETY.

If your data is backed up another option is to just run your HP recovery
disk and it should put you back to factory condition.
 
You should be able to get at the files after installing a new drive,
depending on where they were located. XP security *may* try to prevent you
from accessing certain folders without actually logging into the account on
the now-slaved drive. Make sure you log in as Admin when the new drive is
setup... hopefully that will do the trick.

Randall Arnold
 
Back
Top