Build 9879 hard drive disaster (read this)

The following comment I posted earlier as a reply because I was unaware of how to start a new question or discussion. Here it is with an update.



I updated to Build 9879 via the fast circle option in windows 10 stings, but I was never able to reboot my laptop. I’m still trying all kinds of ways (Acronis TI, Paragon disk recovery) to get back my Dell XPS Studio. I essentially have lost access to any Windows 8 or Dell recovery options because I’m getting a black screen that says:


“Intel UNDI, PXE-2.1(build 083)

Copyright (C) 1997-2000 Intel Corperation


This Product is covered by one or more of the following patents: US5, 307, 459, US5, 434, 872, US5, 732, 094, US6, 570, 884, US6, 115, 776 and US6, 327, 625”


Yes, it looks like it’s trying to boot via network, but I already put the hard drive as my first booting option in the BIOS. Build 9879 literary wiped out my MBR I imagine!


Don’t know what to do anymore, this is a 3 year old Dell XPS laptop i7 with 8GB ram and HD display with a high-end Radeon graphic card and Toshiba Hard drive.


I have been with you now for the 3rd update and giving you feed back all the while, this last one however, killed totally my computer. I have no access to any Dell support or outlet in my current geographical location. Any help from you would be highly appreciated.


Thank you


*Update: My hard drive eventually was unresponsive and corrupted. I took it down to a local computer repair store, they informed me that the disk is unsalvageable, and my only option is take it to a data recovery specialist if I need to recover data. So I bought a new drive and plug it back to my laptop.


Luckily, I had an Acronis disk image backup of my previous Windows 8.1 install, so I recovered it to my new hard drive. After 2 relatively stable release for Windows Technical Preview, build 9879 was a disaster for me. I know, going into this was not going to be all milk and honey, and this after all is a beta preview. But I’m experienced enough with Microsoft betas and have been doing this with many previous iterations of Windows, and to have this happen to me was beyond all my expectations.


Not touching any new builds until I’m assured.


Question Info

Last updated April 16, 2019 Views 36,860 Applies to:

Hi all,
I've pinpointed the issue which is related to this function of HDDs

Your motherboard doesn't support PM2 and neither does mine.
You should get your old HDD back as it is OK. Windows haven't broke the hardware.
Guys in your shop are lame, sorry.

That's the explanation of what's happening:
HDD gets power (electric current) but stays still instead of spinning (it waits for ATA signal).
If your BIOS doesn't support it (you 
probably get something like "SATA1 0MB") bootloader can't start so Windows won't work.
On the other hand, Linux supports direct communication with SATA drives so here comes our saviour.


a) One time

You can fix it for one time by booting Linux LiveCD/LiveUSB and rebooting - Linux communicates with SATA drives and spins them - after reboot BIOS will detect your WD drive and so will Windows.

b) Permanent

(that is until Windows 10 overwrites the setting again :D)

Follow the instruction and avoid Sleep on 9879.

After you boot your LiveUSB/CD:
1. Open Terminal (Ctrl+Alt+T or Ctrl+Alt+F1 or just click the icon)
2. Execute:

sudo hdparm -iI /dev/sd?

sudo hdparm -s0 /dev/sd?

hdparm is a Linux tool for configuring HDDs.

First command displays some info (look for Power-up in Standby on the list - Shift+PgUp to scroll the output).
Second commands sends disable command to that feature.
'?' in commands should work as a wildcard but if it doesn't use 'ls /dev/sd*' to find the letter of the HDD (it usually is either /dev/sda or /dev/sdb - but sometimes can even happen to be /dev/hda)

Credits go to T61T9300 - I couldn't find that command

Here comes the explanation of what happens in there from the author of HDAT2

I'm happy to make your 'bricked' HDDs working fine again.


5 people were helped by this reply


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.