Windows 10 nightmare please help

GemmyJ

Can anybody help me please? I recently upgraded from Windows 8.1 to 10 and at first it seemed to work ok, but over about the last 3 days, I have been getting an error message when the computer has been switched on and idle, saying 'Automatic Repair. Your PCR did not start correctly. Press restart to restart your PC which can sometimes fix the problem. You can also press 'Advanced options' to try other options to repair your PC'. When I click restart it just supposedly repairs, diagnoses my PC and goes back to the same screen without resolving anything. This happens about 3 times a day and I've always been able to get it back up and running, until today when it just goes from blue screen to blue screen. My computer is now unusable, which is irritating to say the least. Does anyone know a solution to this please, preferably without going through a factory reset... or how to downgrade back to the dreaded, but working, Windows 8.1, which they said was simple to do when I upgraded? Any help or advice gratefully received.

esuhl

Did you do an in-place upgrade from within Windows 8.1? If so, I'd wipe the hard disk and try a clean installation of Windows 10. Obviously you'll need to check first that you personal file backups are up-to-date.

prosaver

thats what happened to my lap top ..the mouse touch pad has gone nuts and i cant get back into windows 8 as 30 days data, wontallow to change back .. urgh

[Deleted User]

Did you make a restore/repair DVD?

If so, you should be able to use that to boot to Windows, and carry out a repair.

pogofish

I had this recently and it turned out to be caused by an expiring Seagate Momentus hard drive.

Thankfully I had a recent disc image to fall back on because after a few days of intermittent operation, the drive became unreadable by any means.

buglawton

Beware those with SSDs and with data on separate drive from system:
http://www.theregister.co.uk/2016/08/16/windows_10_anniversary_update_ssd_freeze/

jshm2

This can be easily fixed 90% of the time using a linux liveCD and doing a scandisk check on the drive. The other times it can be the drive is nearing it's end of life or you've got yourself some malware causing havok with system files.