Forum Home
Press F1
 
Thread ID: 140047 2015-08-11 07:33:00 Bootmgr image is corrupt. The system cannot boot. EFFIGY (12530) Press F1
Post ID Timestamp Content User
1406347 2015-08-12 23:16:00 Yup the zip file where you put the X or get the one that says new if you want to use a flash drive. The ISO is only small, so it'll be a waste to use a cd for a 59k iso
well that has opened a can of worms.
Its hard to explain whats going on, basically I think files are being stored in wrong places. The computer boots from the usb and runs fine. BUT when I started to work with the memtest usb I got a message telling me to reconnect my drive because it has been disconnected too long. I couldnt safely eject the usb as it complained that it was still in use, even though all the programmes were closed. So I shut down - removed the usb with memtest on it and powered up, guess what...
Bootmgr message again.
So
I switched everything off at the wall and started again with the W10 usb, which worked fine, differently to last time, but it worked and I am up and running again.
Here is where it gets interesting. I have just realised that the Seagate external hard drive which is normally permanently attached, was NOT attached when I did the upgrade from W8 to 10 the first time. I have 2 internal and 2 external hard drives.
The computer is supposed to boot from the SSD 'C' drive, but I *think* something is wrong with the way it is storing temporary files, ie NOT on the other internal 'D' I wanted it to, but somewhere else - like possibly the Seagate.
I am out of my depth here.
EFFIGY (12530)
1406348 2015-08-12 23:41:00 It may have been trying to boot from one of the externals if they were still connected. So which hdd has windows on it the SSD or the external??

If the SSD, it should install / upgrade on that not on the external.

If the SSD is the bootdisk / has windows on it remove the external hdds. Then try the upgrade again

Also if you havent used this for a while open the case and see if its full of dust
Speedy Gonzales (78)
1406349 2015-08-12 23:49:00 Are you sure if you did a clean install after you first upgraded you did not get the drives mixed up as it gives you a choice usually with the correct one highlighted Blue

I always look at this twice
Lawrence (2987)
1406350 2015-08-12 23:56:00 I'm going to start a new thread about this one... EFFIGY (12530)
1406351 2015-08-13 00:08:00 That'll only confuse people and they'll probably come back to this thread. Speedy Gonzales (78)
1406352 2015-08-13 01:24:00 I have disconnected everything, vacuumed thoroughly (I wanted an excuse to use the minitools that came with my new vacuum) I booted from usb and all looked good so I thought - lets try re-boot from ssd. So I shut down, removed usb, restarted into bios and told it to boot from ssd (which is how I set it up) The ssd is 'C' drive. So as far as I know it is now booting from the ssd. Now I just have to wait and see if I get the 'reconnect your file history drive' message again, my file history is on 'D' which is the old original hard drive (one of the few bits I kept) when I rebuilt.
At what point will it be safe to reconnect the external hard drives?
EFFIGY (12530)
1406353 2015-08-13 01:30:00 Thats a good question. I have no idea when its safe to connect external hdd's. I've never had any Speedy Gonzales (78)
1406354 2015-08-13 01:45:00 Grrr, this looks intermittent. Sometimes it will boot and sometimes it won't. I shut it down to test and when I hit the power it just sat there powering and stopping, powering and stopping, so I unplugged everything wiggled the usb wires and sata connections and it started. (with usb) But why has this happened since W10? Or is it perhaps just co-incidence? EFFIGY (12530)
1406355 2015-08-13 02:38:00 I think this is a connection issue, I had the machine running and restarting for the past half hour no problem, so I thought great let's put it's cover back and set it where it belongs. Now it's doing the power on whirr click, off on over and over again. I'm at my wits end, I suppose I just have to open it up again.:crying EFFIGY (12530)
1406356 2015-08-13 02:52:00 Self induced faults are always the hardest to find. Driftwood (5551)
1 2 3 4 5 6