Windows 10: I lost 2 Hard Disks after updated from Build 9860 to 9879

Updated to build 9879 with no problems from build 9860. However, I powered down and restarted the next morning to find "Disk Boot Failure - Insert system disk". Whatever I tried to see inside the disk failed because it wasn't recognised in the BIOS, so that disk is a goner. Also I found that my second disk for data was lost, so that's a second disk down the tubes. I transfered both to a chipset 1155 PC and recognised both. Return on my Dell Optiplex 780 (chipset 775) not recognised both. Even connecting external as USB failed. Anyone else had similar problems?

:)

 

How to: 10 Tips before installing the latest Windows 10

Successfully updated from 9860 to 9879 on 12/01/14. Don't know why it worked this time, since Win10 has not been booted since the failure on 11/25/14.

BTW, after the failure, it automatically reverted back to 9860.

 

How to: 10 Tips before installing the latest Windows 10

Good to see the Build Number on the download page. That, in itself, is an improvement.

Now to see if 9879 will install over updated 9860. It failed on 11/25/14.

 

This won't help you directly with your issue but I always unplug all but the OS drive while installing Windows as it can often install parts of itself on other drives complicating the issue should you wish to replace one of those drives in the future.

I'm sure someone here will be able to help with your problem.

 

Me too unplug other OS HDD's when installing new. But the second drive was for data only. Sorry for my bad English.

In TechNet Forum there is another post with similar problem

Thanks

 

Did they suggest a fix?

 

Finally I got a solution

The drive one with OS and the second one with data found in the bios of an Intel 1155 chipset PC. On my old Dell Optiplex 780 (chipset 775) I used for evaluating build 9860 after updating (fail) to 9879 they do not appeared at all.

Both were in "Frozen state" allthough there were HDD's and not ssd.

Following this guide
How to: Secure Erase your Solid State Drive (SSD) with Parted Magic

I examined them in the old PC and bios recognised them. Everything OK.

What happened during update in place from 9860 to 9879 to cause such problem?

 

Windows 10T, like it's predecessor Windows 8, is designed to close & reopen faster by booting - Hybrid Boot.

It has left your system in a hibernated state, with the drives mounted, open and ready to take off as soon as Windows 8/10 restarts. When a drive is mounted, a little piece of data is written to a standard place on the disk to show it is in use - it is called the "dirty bit".

Now this may be completely unrelated to your problem, but because I'm still using Windows 7 whist evaluating Windows 10T, I've changed things so that Windows 7 doesn't go through a complete chkdsk on every disk on my system.

For those who are interested:

1. Control Panel -> Power Plan
2. Select "Choose what the power button does" on left hand side.
3. Click on "Change settings that are currently unavailable".
4. Uncheck "Turn on fast startup" under shutdown settings.

 

Thought it was my bad luck but read people having the same problem, my story as follows. Started with first build released 9841 on my 5 year old 1 terabyte Samsung HD then updated to 9860 all with no problems then noticed it was stating drive errors so did repair as Windows wanted and it rebooted but no repair done.Then along came 8979 after over 40 minutes back to desktop all OK rebooted and found drive had failed not visiblele in my ssd Windows 8 but visible in Linux boot disk and managed to recover pics and with partition tool the drive as well.Then being a glutton for punishment downloaded a Pro build 8979 and installed on a ssd but after a few seconds on desktop it powered down as if I hit the shutdown button no bsod tried,tried again exactly the same.Put Windows 7 back on this drive with no problems,all the years from Xp on installed loads of beta's but never problems like this ,weird or just one of those things?

 

This is not real, I bought a new 128gb SSD for the Preview when it came out, everything seemed okay except for a couple of minor glitches. Upgraded to 8979 had a few problems with that and also boot problems and BSODs, so I put Wiindows 8.1 on it as well for a dual boot to see if it would work okay on the drive, it did for a couple of days.

Two days ago I tried to boot up nothing, tried a few times nothing, checked the BIOS, no drive. I've got an exact same drive with Windows 8.1, so I put that in, booted up straight away.

I put the SSD in a USB caddy and I can read it. So I put it back in the other computer to see if it would boot, nothing, and nothing in the BIOS.

Is 8979 a HDD killer, it certainly seems like it, I've never had these problems with a brand new drive before. I'll keep the drive around for another couple of days to see if it will come back from the dead, but it doesn't look good at this stage.

Ive got another computer with 9841 on it, so I'll send Microsoft a message to see what's going on, this is definitely a bit weird.

Now it's getting crazier, after writing the above it prompted me to try again. So I booted up and it actually booted and I could see it in the BIOS, but all of a sudden the dreaded BSOD and reboot into an automatic repair, then reboot, straight back into another BSOD.

 

Looks like I might have to wipe both partitions and forget the Preview until the next major update

 

Parted Magic caused problems in Win7. I wonder if it could have caused you problems in TP.

I would run the maker's drive diagnostics, under their supervision if still within a year of purchase so you are already in the pipeline for RMA.

 

Same problem here
dual booted my old HP DV2000 laptop with Windows 7 to test Windows 10 on older hardware.
First Windows 10 build fine. So was the 2nd. Tried to upgrade to 9879 which went fine until I ran down the laptop and rebooted - nothing , no disc in the bios. Took out the Hitachi disc and connected to my other PC but it would not even spin up so after 6 years I thought it was bricked so into the bin it went in pieces after removing the platter inside.
This was last week before I read of these other problems so put in a new Western Digital disc and restored the laptop from backups. Now have build 9860 running fine. Do I risk the upgrade to 9879 again with my new disc?
Sounds like there may have been nothing actually wrong with the old Hitachi disk!

 

I think you were a bit hasty throwing out the Hitachi, HDDs have a habit of coming back from the dead, I've had them come back after a couple of years.
If I were you I wouldn't chance 9879 again, I had similar problems to you, couldn't read my new drive in the BIOS and had all kinds of problems with 9879.
In future if you have a drive that wont read in the BIOS stick it in a USB caddy on another computer, or even the same one if you have another boot HDD, if it doesn't read at first, turn the power to the caddy on and off a few times, also plug and unplug the USB cord and try different ports.

I've bought a few drives back from the dead that way, sometimes even just try again in a few days, it's amazing how these bricks can come back.

 

The exact condition of the drive (if it can spin) is determined with certainty by booting the maker's HD Diagnostic extended CD scan, followed by Disk Check - Windows 7 Help Forums run from the run from the booted installer's Command Line.