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

I see no Fast Start or any other setting discussed in the lengthy threads tracking this issue:
build 9879 bricking drives - Microsoft Community
Build 9879 hard drive disaster - Microsoft Community

The Power Plan is Balanced at defaults.

 

Deja vu
Yes a update build reset fast start and hibernation and pretty much bricked mine
http://answers.microsoft.com/en-us/i...1-3bcf93b1ae4c

They put out a fix for some but seem to effected some other drives in the process
No updates on my question there.
I'm done with 10.

 

After using it solidly since October I started having mice problems, went back to 7 and feel like I'm home. Now if I can only get the two hard drives 9879 bricked fixed I'll try to forget the whole thing.

 

I wonder if using "High performance" plan and setting the HDD to Never sleep could help. *Confused
(Power Options > High performance > Turn off hard disk after > Never)

 

Hi there

You could download W8.1 enterprise trial and make a WINDOWS TO GO - so this would allow you to boot a Windows system to attempt to repair your HDD's. You can make a Windows to Go system on any external HDD --doesn't have to be a "Certified" device. Methods are in the tutorials.


Otherwise you could install VMware vmplayer on any bootable Linux system and a Windows VM and use the Windows VM to repair your drives.


Note here also for people reading this who use Storage spaces.

Note also that if you CREATE storage spaces on W10 and then revert back to W8 the storage spaces will show configuration error -- DO NOT RESET the drives as you will lose data. You need to install W10 again - then the storage spaces will be OK --save the data and THEN revert.


If you create storage spaces in W8 and then go to W10 - they should work.


Cheers

jimbo

 

Since you can boot the drive up, can you wipe and format that partition? And install either Ubuntu or Linuxmint there instead.
Mind you Win10 is only a TP. It works for a few months only.

Daniel

 

You were lucky to be able to access the drives at all,
I have yet to get anything to access mine,
Tried many things Linux live disk tried to install Linux...
Need a mobo capable to wake it and enter the command to disable what ever feature I believe to be fast start/ Instant Go feature,

The issue might or might not effect ssd's :/
I'm not willing to test on one to see
I've just chalked it up to 10tp as undependable and not worth the potential future problems free upgrade or not lost data/ drives is a deal breaker or jumping through a bunch of hoops to wake a drive just is not worth it for an os,
Linux is free too and I'm getting used to it
Start button has everything not just a few things *Wink

If you find out how to un-brick make a tutorial *Tongue
Attachment 14882

 

After reading carefully what gregrocker said, I think my hd issue was different from his.
After mid January, I only fool around via virtual player.
I was very careful already. I detached all other harddrives while installing win 10. Still after reattachment , win 10 still bricked my harddrive.
I was lucky by correcting my problem by reinstalling win 10 again.
I was very impressed with the Beta of win 7. But this is another beast.

Daniel

 

I believe the new terms of use are very clear,
Your losses are restricted to what you paid for the os "0.00$"
Either way both of you or anyone that can access the drive or get anything to read the drive at all have done well your luckier than I

Nothing but 10tp 9926 we're on the 6y.o. Hitachi hdd
But what if there were :/
Sorry but the win-10 juice is not worth the squeeze besides it's going in the wrong direction to my preferences anyway
I did buy a 25$ generic hdd to test with but I'll hold off until way down the line to test June.. to see what happens with it,
I'm happy with 7 and mint 17.1 *Wink

 

If you kept track of your error codes post them,
http://answers.microsoft.com/en-us/i...1-3bcf93b1ae4c
My picture of it was so blurred I couldn't read it *Sad

 

Is there any data on the dirve that you need?

If not, try doing a clean all on the HDD. I don't know what was on the drive before, but if there was a Linux boot, sometimes, grub4dos writes beyond the 100MB threshold (I used to know the exact boundary .... sorry 'bout that)

 

Hi Bill are you talking to me :/
Nothing but build 9879 and 9926 were on mine and some walls,
I personally tried everything to access or get anything to acknowledge the drive failed including installing mint 17.1 failed.
dpart fail via live dish...

 

Sorry Mike, that was, or should have been, directed to Greg. I'll correct my post.

 

Thanks Bill, I'll try that tomorrow.

 

Hope it helps.

Your avatar would make a great letter T after removing the side white water. I almost took the liberty of making a TenForums image for you using it (... but I've been busy with other fun stuff.

Good luck.