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!
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.
Thankyou BillyBob and gregrocker for you comments.
I tried all that with the Hitachi on USB and separate power on my other PC to no avail. I will not try 9879 and wait for the next release and install when it is considerate to be stable.
As a Win 8.1 user, Windows 10 looks great - just needs the bugs sorting.
I had the same issue, however, I lost 2 drives on two different machines.
I have 2 machines that I use for "play with/experiment", a Gigabyte GA-Z68MA-D2H-B3 w i7-2600 cpu & 16 GB memory, and a Gigabyte GA-X58A-UD3R with i7-930 cpu & 12 GB of memory. Both machines have Kingwin 3.5 Internal Tray-less Hot Swap Racks.
Both machines had (for C:\ drive) brand new Seagate ST1000DM003 1 TB hard drives.
Everything was fine for some days, however, after updating to Build 9879, I lost both C: Drives.
Neither would boot after shutting down overnight and nothing I could do helped:
Boot the machine up with Win 8.1 Pro or Win 7 Pro and the drive(s) would not be recognized until after an excessive amount of time.
I tested both drives on my main computer (Win 7 Pro) that I don't experiment with and I finally got SeaTools for DOS V2.23 to recognize one of the drives, however, ALL tests would fail.
One drive was only 2 Weeks old and I took it back to the store and exchanged it.
The other was 2 Months old, so I got a RMA from Seagate to replace the drive.
Has anybody else seen this?
Anybody have any ideas what is causing this and what the fix might be??
Yes faced same issue and finally after much of R&D and wasting 2 days came up with solution : -
1) DL hiren CD.
2) Boot up mini XP.
3) Disk manager > Format it (For me primary didn't work so i formatted it to extended NTFS).
4) Get WINXP CD and install it.
And all done.. After installation u can reinstall any OS u want ...
Though i tried installing 9879 build again and faced same issue now will again format HDD once i reach home..
Guy I need help, My HDD (Main one) disappeared after that stupid auto update of new TP build at night. TP is on separate SSD and other HDD is my main HDD with windows 8.1 on partition 1 and my data on partition 2. How do i get back my HDD.
It is a laptop i bought recently, i dont even know what brand HDD it was. Now I am pissed and don't know what to do, the HDD don't appear in Disk management.
Thanks for the info o0k00l and I will download and inspect those files, however, since none of the Seagate tools (SeaTools for Windows or SeaTools for DOS) was able to handle the issue, I've already exchanged one at the store and the replacement from Seagate will arrive today.
Note that Seatools for Windows (latest version) would not recognize either of the drives. Seatools for DOS (V2.23) did recognize one drive, however, all repair/reformat operations failed with seagate failure codes.
If I have the same issue happen in the future, I'll give these utilities a try, however, if I do lose another drive(s), that will be it the last time for the Tech Preview until it becomes more stable and no more of these issues show up.
Also note that when I experiment with new systems, I do so with a dedicated hard drive(s) and NEVER attempt to install as dual boot with my daily machine!