Windows 7 troubleshooter will not work

Status
Not open for further replies.
R

Rob94hawk

2[H]4U
Joined
Jul 20, 2002
Messages
2,222
Update: Solved!!

I just got through cloning my dying 5400 HD to a larger SSD on a Windows 7 laptop.

I can't fix problems, check for performance issues, or even troubleshoot problems on my network card.

I used the system file checker to see if anything was corrupted on the SSD but it came up clean.

At a loss here. No idea how to fix this one.
 
Last edited:
Rob94hawk said:
I just got through cloning my dying 5400 HD to a larger SSD on a Windows 7 laptop.

I can't fix problems, check for performance issues, or even troubleshoot problems on my network card.

I used the system file checker to see if anything was corrupted on the SSD but it came up clean.

At a loss here. No idea how to fix this one.
Click to expand...

Does the computer boot? If it does, try to boot a linux live distribution to see if your hardware is really broken or if it's just a corrupted windows from the old hdd.
 
auntjemima said:
Are all of those three things listed related to your network card?

Try uninstalling it and reinstalling. Otherwise, you could try running the commands at this website. I have used it before and repaired networking issues.

https://kb.wisc.edu/helpdesk/page.php?id=6653
Click to expand...

Not sure. There is no problem at the moment. After the switch over to the SSD I just happened to notice after a reboot there was a delay in connecting with the internet so I just went to troubleshoot just as a precaution & just happened to notice that troubleshooting doesn't work. Was looking to boost performance in Windows 7 & noticed that troubleshooting doesn't work for that either.
 
vick1000 said:
SFC time...
Click to expand...

Did you miss the part where the OP said that was done? :D

Rob94hawk said:
I used the system file checker to see if anything was corrupted on the SSD but it came up clean.
Click to expand...

My personal advice: maybe consider doing a clean install of Windows 7 depending on how long that installation has been in operation. I typically recommend a clean install since it's easier and faster to start over in a great number of situations than wasting hours, or even days attempting to resolve such an issue and having no luck at all and eventually doing a clean install anyway.

Yeah, I know, it can be a complete bitch for some people to start over again, not saying it wouldn't be such a situation for the OP, just saying it's something to be considered.
 
Check if any of these services aren't running
 

Attachments

  • Services.png
    Services.png
    19.4 KB · Views: 0
One other unrelated thing, you need to check partition alignment when you clone a HDD to SDD. If it's not aligned, you should do a fresh install anyway.
 
What cloning software did you use? If it was pretty old cloning software, it might not have aligned the SSD properly, like ^^^ vick1000 mentioned. But at this point, I would be leaning on and prepping for backup/dump/reload.
 
you cloned a failing hdd so there are probably errors/corrupt files. like mazz said, try a reinstall of 7 over itself.
 
pendragon1 said:
you cloned a failing hdd so there are probably errors/corrupt files. like mazz said, try a reinstall of 7 over itself.
Click to expand...

Ok so I probably caused this problem. I used 2 different cloning software. I couldn't get Macromium to clone C: so I had it clone partitions H: & G:

Then I used AOMEI to clone C: last.

Everything works fine though. I'll try swapping back in the old HDD to see if I can get troubleshooting to work.
 
I'm gonna go ahead and be THAT guy. I have been doing this since around 1995 in the PC world. I have never successfully long term had a Windows repair install. \

They suck. I don't care what anybody says.

With that said, You need to back up the important data to another drive and do a fresh install. You have already taken more time chasing unicorns than it takes to do the correct thing.

I would explain in detail why you need to just do it the right way but my fingers are tired. Something like .dll's lost on bad clusters, you don't code for MS nor can see it...blah blah blah.
 
DrLobotomy said:
I'm gonna go ahead and be THAT guy. I have been doing this since around 1995 in the PC world. I have never successfully long term had a Windows repair install. \

They suck. I don't care what anybody says.

With that said, You need to back up the important data to another drive and do a fresh install. You have already taken more time chasing unicorns than it takes to do the correct thing.

I would explain in detail why you need to just do it the right way but my fingers are tired. Something like .dll's lost on bad clusters, you don't code for MS nor can see it...blah blah blah.
Click to expand...

Wow, really? I've used the repair install feature in the past to transfer a Windows Server 2003 install between servers without a single issue. I wish more than anything the feature was still available under Windows 10 as the Windows 10 repair tool is useless.

Now if you were to say that sfc /scannow is hopeless and never fixes a thing I'd agree. ;)
 
Mazzspeed said:
Wow, really? I've used the repair install feature in the past to transfer a Windows Server 2003 install between servers without a single issue. I wish more than anything the feature was still available under Windows 10 as the Windows 10 repair tool is useless.

Now if you were to say that sfc /scannow is hopeless and never fixes a thing I'd agree. ;)
Click to expand...
No one said anything about Windows Server ;)

I was speaking of strictly Desktop Versions.

And I have had sfc /scannow fix some things in the past. :p
 
Mazzspeed said:
There's not really any difference from a repair install perspective?
Click to expand...
Well most servers serve. They don't have dumbass users banging away on them all day browsing QVC and donkey porn. Which is of course followed up by installing stupid software and toolbars that make a repair install shit its pants.
 
DrLobotomy said:
Well most servers serve. They don't have dumbass users banging away on them all day browsing QVC and donkey porn. Which is of course followed up by installing stupid software and toolbars that make a repair install shit its pants.
Click to expand...

A repair install isn't going to rectify virus/malware related issues. ;)
 
Mazzspeed said:
A repair install isn't going to rectify virus/malware related issues. ;)
Click to expand...
That isn't what I am referring to.

And it isn't up for argument. I don't like repair installs and I think they are bullshit. That is the way I run things. I don't like get bitten in the ass and a repair install is just a rattle snake in wait.

Enjoy your eventual callbacks.
 
thats your opinion. my 20+ years says they work and sometimes dont. depends on how bad things are. this is a failing drive clone and needs files replaced so a repair install could fix it.
 
In other notes, shortly after this eureka moment I black screened the laptop's display updating the ATI drivers, but after reinstalling it I noticed that for some whacked out reason AMD hid their ACHI driver in this update!

Why the hell would they do that?!

Well that's enough for today. Going to bed before I break what I just fixed...
 
Status
Not open for further replies.
Back
Top