Not Behaving

[leachim]

Win 7 64 bit Sp1

 

 

Got called in to fix a printer issue

 

Turned out that things had gone wrong 2 weeks before when the theme had changed - tried a system restore - no good.

 

 

Services.msc won't open - nor will Default Programs

 

 

Ran Malwarebytes - found some malware - removed

 

 

sfc /scannow - found stuff but couldn't fix it

 

 

Tried a Repair Reinstall - came back with an error

 

 

Used Tweaking.com Windows repair to reset permissions etc etc

 

 

No good

 

 

Is there something I missed ?

 

 

Thanks

[Mako]

My rule of thumb is that as soon as anything goes wrong with the system it's easier to reimage the machine. You spend less time waiting for windows to install than the hours trying to correct the problem of corrupt system files.

 

Is that possible for you?

[southhamster]

My rule of thumb is that as soon as anything goes wrong with the system it's easier to reimage the machine. You spend less time waiting for windows to install than the hours trying to correct the problem of corrupt system files.

 

Is that possible for you?

Yes. Whilst I enjoy fixing an obscure problem it's not cost effective for me to spend more than an hour or two finding the fault, or even worse not finding it!

Plus Reinstalling does clear out an awful lot of rubbish too!

[leachim]

When you say Reimage - do you mean a Fresh Install

 

I have cloned the drive onto another to "mess" around with it, so I don't cause any possible non reversible issues with the setup they already had....

[Mako]

When you say Reimage - do you mean a Fresh Install

 

I have cloned the drive onto another to "mess" around with it, so I don't cause any possible non reversible issues with the setup they already had....

 

It's common practice to have a standard "image" of a computer, a customised configuration that you can always go back to (and apply to new computers) for a consistent environment (not technically a clone, there are differences between a clone and an image). If windows imaging deployment is not something done where you work, then a fresh Windows install would be recommended if that is an option. As @southhamster said it's not really cost efficient to spend hours fixing a corrupt system, especially if it's been a victim of malware. You also never really know what damage it's caused and something may rear its head further down the line.

 

Wiping it clean, through whatever method applies to your scenario, is the best course of action.