Windows 10: Interesting question here about bricking older hdd's :/

Just keep a drive for it alone when installing Windows and while updating, both, 9860 and 9879 screwed up (temporally) my dual boot so I had to fix it. Next time I'll disconnect other dives while doing that.

 

That's no myth, urban or otherwise lol. But it takes a lot of effort to trash HDD by using OS alone, it takes a lot of specialized SW to change firmware in a HDD and apart from electronic or mechanical breakdowns it's very unlikely it could be done by accident. I remember trying to salvage data from some half dead HDDs by changing controller boards on them and flashing same FW on it to match serial numbers so it would work and I can tel you, it was a lot of work. I would say continual BSODs and freezing etc can put a bit of strain on an SSD and do quite a bit of damage.

I had a few spare hours this afternoon and tried repairs with TP and Windows 8.1, didn't work. Tried installing Windows 8.1 straight over the top as a new install, didn't work, formatted one partition and tried again, didn't work. Formatted all 3 partitions and installing, didn't work.

Fully removed all partitions and installed again, this time it worked, Windows 8.1 and fully updated. Have rebooted a few times and run some apps, no BSODs.

No matter what anyone thinks, this was caused by 9879 and nothing else, end of story. File system yes, physically bricking, trashing HDD not likely. I've never said it was bricked, I said it was very close, trashed absolutely, close to being bricked absolutely, was it 9879, absolutely.
What SSD brand and model are we talking about here? I have no problem with Samsung Evo 120GB.

 

Pretty weird new feature of sleep mode in win-10 *Shock
From the last few posts look like Hitachi hdd are effected,
That's what I was using for the first few builds for dual boot
I guess I bailed in time although I still had to re-install win-7 after to straighten out the boot mess :/
build 9879 bricking drives!!!! - Microsoft Community

 

That's no myth, urban or otherwise lol. But it takes a lot of effort to trash HDD by using OS alone, it takes a lot of specialized SW to change firmware in a HDD and apart from electronic or mechanical breakdowns it's very unlikely it could be done by accident. I remember trying to salvage data from some half dead HDDs by changing controller boards on them and flashing same FW on it to match serial numbers so it would work and I can tel you, it was a lot of work. I would say continual BSODs and freezing etc can put a bit of strain on an SSD and do quite a bit of damage.

I had a few spare hours this afternoon and tried repairs with TP and Windows 8.1, didn't work. Tried installing Windows 8.1 straight over the top as a new install, didn't work, formatted one partition and tried again, didn't work. Formatted all 3 partitions and installing, didn't work.

Fully removed all partitions and installed again, this time it worked, Windows 8.1 and fully updated. Have rebooted a few times and run some apps, no BSODs.

No matter what anyone thinks, this was caused by 9879 and nothing else, end of story. File system yes, physically bricking, trashing HDD not likely. I've never said it was bricked, I said it was very close, trashed absolutely, close to being bricked absolutely, was it 9879, absolutely.
What SSD brand and model are we talking about here? I have no problem with Samsung Evo 120GB. It's a Kingston HyperX 120GB, I've got two of these, the reason I bought the 2nd one was because the 1st never gave me any problems.
The 2nd never gave me problems until 9879 and so far since completely repartitioning and installing Windows 8.1 no problems. I didn't do anything wrong, just did what Microsoft said to do, upgrade to 9879, that's when the problems started.
I suppose people could say why didn't you do a clean install with 9879, that's not what Microsoft wanted, it's an in place upgrade.
I know I'm not the only one there are quite a few people who have had similar problems, and I suppose in a way that's what Microsft wants, problems being reported.

 

I never read anything about installing 10TP as a upgrade from any existing os :/
On the contrary Microsoft had stern warnings to not use 10 on a primary computer *Wink

 

Looks like you haven't been following the thread, when you've read what I've been saying, comment again.*sarc

By the way people, I'm now commenting from Windows 8.1 on the SSD which was giving me all those problems, and guess what, no problems so far, so it wasn't hardware.

 

Most people have done a clean install on another partition or it's own drive,
Actually the majority of smart people are using hyper-v or VMware player *Tongue
But I doubt clean would make any difference the issue is with sleep or hibernation mode in windows 10TP newest build and some hdd's and ssd's
The newest to the list is Hitachi which I was using before the newest build so I may have bailed out just in time as far as I can see which did require another clean install of win-7 for me personally,

I just want to see the documentation that says Microsoft recommended people to cover or upgrade to win-10TP instead of a clean install of win-10TP on it's own drive,
Which I'm sure you can't produce :/

 

With the win -10TP the upgrade files were made available before the ISO were released.
Link to M$ stuff. detailing what you can keep and not keep when upgrading.

 

I don't need to produce any documentation, 9879 was An update to 9860 which was an update to 9842 or whatever the 1st one was, Microsoft wanted people to update, not do a clean install, which is what I did, besides there was no ISO, unless you wanted to make one yourself.
I've got a funny feeling you haven't read anything I've said, not that that matters, nobody listens to me anyway, not even my budgerigar.

Oh and just so there's no confusion, I made a living out of building selling and repairing computers for quite a number of years, back in the DOS days when you had to know a hell off a lot more about computers than you do now.

 

Oh, like it's first time MS screwed up an update ???? Actually it happens so often that I always (well almost) make a full system backup before applying any large update. For Win 10TP I didn't bother that much, it's a tryout thingy and I can replace it any time, nothing important is on it anyway. Everything else is on primary OS, W8.1 and Linux because there are some SW I can't replace easy, like MS Office and other precious stuff.

 

I don't need to produce any documentation, 9879 was An update to 9860 which was an update to 9842 or whatever the 1st one was, Microsoft wanted people to update, not do a clean install, which is what I did, besides there was no ISO, unless you wanted to make one yourself.
I've got a funny feeling you haven't read anything I've said Well I get an equal feeling you haven't read the links in the original question,
I've never said I know anything about computers
Originally in the first build I did install 10TP on top of 8.1 only because I didn't care what happen to it and as you stated it was much easier to do,
Other builds were clean installs,
Next will be on it's own ssd instead using VMware or hot swap so I am shifting my install preferences learning via hard knocks *Smile
Cheers.

 

I also installed 10 TP build 9879 on a Kingston HyperX 128 GB ssd, but I've had none of the same problems as you. So far anyway. But it's good to know about potential problems.

 

Billybob,

Even though I don't test W10 any more. I still read about it. I came across a post that said 9879 overlaps a partition that causing it to be bricked. It sounds to me it causing the drive to have more than 4 primary partitions unless your drive is GPT. This might fix, if you can boot to 9879, shrink windows 10 partition, reboot install MiniTool Partition Wizard Home Edition free version don't know if work in this build. You can use MiniTool partition wizard to resize it back to without it overlapping. Now, if you can't boot, I would recommend trying Linux gparted. I am unclear if resizing a windows 10 partition using gparted keeps the data.

LittleJay
Is your drive Gpt or MBR partition?

All,
Even if you have GPT partition, your partition could be overlapping as well.

 

I use MBR partitions for my W10TP installation. As I mentioned before, I haven't had any trouble with my Kingston SSD bricking, but it is good to be forewarned that it might be possible.

 

I also installed 10 TP build 9879 on a Kingston HyperX 128 GB ssd, but I've had none of the same problems as you. So far anyway. But it's good to know about potential problems. Who knows what causes these things but Microsoft has admitted to BSODs etc in 9879 and has released a patch. Different computer configurations with different hardware and drivers are bound to cause problems.