[Ste]

Hi, I followed the instructions and the file appeared on the desktop. As previously, the message that the computer needs to restart appeared and so I rebooted; or at least I tried to. The same problem occurred as with the AVG fix, i.e. the drive became unbootable. So now I am on the clone which I made before the attempt.

 

I am now wondering if it would be easier to leave it as it is for now as the OS works fine apart from those redundant files. I might even consider reinstalling Windows on a spare sata drive to transfer to SSD later. (Do you think it would be feasible to do this in parts? In other words, returning to the new install several times until it is up to date, or can you foresee problems with that procedure?).

 

I am suspicious that the initial transference of the OS drive to the replaced mainboard and processor, even though they were supposed to be the same, may be at the heart of the matter. Of course, I am just guessing.

 

Another alternative I have is to try another older clone from last year which I have on an SSD but I suspect it may have the same inherent problem.

 

Do you think it is worth carrying on? I will be re-cloning this drive again shortly.

[Advertisements]

Since your system has crashed now on two different operations which only have a reboot in common, it would appear that there is some system instability present that only manifests itself during the boot process.

 

Since service drivers can only be removed on reboot, prior to your OS loading, it is unlikely that we'll be able to successfully perform a full removal of either Malwarebytes or AVG, since both have drivers present on your drive.

 

Since none of these orphans are causing problems (other than when we try to remove them), then although it's not ideal, then if you can live with them, then I'm inclined to leave them alone, since the only other alternative I can think of off hand, is to wipe the drive and perform a clean install of Windows.

[Gary R]

Since your system has crashed now on two different operations which only have a reboot in common, it would appear that there is some system instability present that only manifests itself during the boot process.

 

Since service drivers can only be removed on reboot, prior to your OS loading, it is unlikely that we'll be able to successfully perform a full removal of either Malwarebytes or AVG, since both have drivers present on your drive.

 

Since none of these orphans are causing problems (other than when we try to remove them), then although it's not ideal, then if you can live with them, then I'm inclined to leave them alone, since the only other alternative I can think of off hand, is to wipe the drive and perform a clean install of Windows.

[Ste]

Hi, yes I think we are in agreement on that. There's me thinking it was a simple task. I will probably leave it for a while and begin a clean install on another drive, but as I said that will have to be in increments. 

 

I'm very great full for the effort you have made trying to help, thank you.

 

Regards,

Steve 

[Gary R]

You're welcome.

 

Sorry things didn't quite go as planned.

 

Gary