System Restore won't proceed past the "next" after selecting date

[Bob O]

I've recently encountered an issue with my computer, I think it may have been
due to some sort of virius attack. Windows now won't start in normal mode.

Anyway I am in "safe mode with networking" trying to utilize system restore
prior to getting medievil on the computer and using the HP recovery system.
For something that is obviously screwed up I've still got a lot of
functionality.

So I start system restore, id and select a "system restore point" (I've
tried several dates) and click the "next" button to proceed with the process,
and nothing, "click, click, click"; nothing happens.

Any ideas? I hate to lobotomize the computer with the HP restore, as I'm
assuming it's fixable given that the computer functions pretty normally but
for that whole can only open windows in safe mode. i've obtained a external
usb drive and moved my important data, but there are still some software
items that I'd like not to have to reinstall.

Thanks for you input
Bob

 

[Mick Murphy]

Do it in Safe Mode; and disable your Anti-virus before doing it.

 

[Ray Parrish]

Reading comprehension isn't your strong suit is it Murphy? The OP stated
that they could *only* get into Safe Mode, and that's where they are
trying to do the restore from.

Later, Ray Parrish

 

[Mick Murphy]

You have become an IDIOT, Ray.
YOU should learn to READ.

Still giving WRONG advice about Malwarebytes??????

"Anyway I am in "safe mode with networking", the OP's words!

I said to do it in Safe Mode, NOT safe mode with Networking, IDIOT

 

[Ray Parrish]

OH, that's what you meant... sorry, I've been duly whacked and accept my
punishment...

Later, Ray Parrish

 

[Mick Murphy]

Fair enough, Ray.
Thr list of startup options contains a lot of things:
Safe Mode
Safe Mode with Networking
etc
And Safe Mode with Networking gives you access to the Internet; which I
thought may be causing a problem with SR.

 

[Ray Parrish]

Thanks, I shouldn't have made that post in the first place. I read a lot
of posts and there are a lot of clueless people that don't read before
answering and it gets to me sometimes. I should have kept my fat fingers
off the keyboard that time.

Later, Ray Parrish

 

[Daave]

Thanks, I shouldn't have made that post in the first place. I read a
lot of posts and there are a lot of clueless people that don't read
before answering and it gets to me sometimes.

It looks like you just joined their (our -- I've done it once or twice)
ranks!

 

[Scubatropin]

I have the same problem; I receive a stop: 0x0000007E
(0xc0000006,0x806849EA,0xF79776E8,0xF79773E4) blue screen error upon trying
to boot normally. I've been booting to safe mode and trying to run system
restore to ANY time availible. As you know, on certain dates there are more
than one restore availible, nothing works, it just clicks and sits there. I
lent my XP pro CD to someone who LOST it, so that's not an option. The
computer is NOT proprietary and built it myself so alternate system restore
via different partition is not an option. I would rather just use the System
restore included with XP. Any ideas or suggestions to get back a previous
restore would be great. (Yes anti-virus is disabled in Services)

 

[Bob O]

Tried it in plain safe mode, same results.

Is there a troubleshooting mode where you can load a driver at a time till
it stops working? I'm assuming that something got FUBAR with windows or a
driver when the virus was cleaned by McAffee, or the virus actively deleted
something. How does one troubleshoot when windows only comes up in safe
mode? Obviously something is missing or corrupt or misconfigured and that
won't let it open in full windows, I just need to find out what.

Can I reinstall windows over the existing install without a lobotomy to the
computer? I don't have the windows disks as they are on the "HP recovery"
section of the drive. I don't beleive I can simply access them, without
running the "HP lobotomy" program.

Scubatron, I read about your issue someplace on the microsoft site while
searching for something on my issue; it has something to do with a
configuration in service pack 3 setting something funky in the
intelpowersomething. Bascially it configures some power function for an
intel processor but if you've an AMD processor, it screws it up. Your
supposed to rename a file that starts with "intel" to "xxxintel---".

Bob