can't make a clean win 7 install on my new sata drive :(

LilWeasel · 12 Sep 2015

https://www.asus.com/Motherboards/CROSSBLADE_RANGER/

That's the mb I have.

I just tried one more time with the diskpart command prompt thing. And I can clean and turn it into a MBR drive just fine, but that's where it stops, I'm probably typing something wrong but, I can't format it, I can't assign it, and I can't activate it after that point.. it just says this: "There is no volume selected." I don't know what they mean by that. I just wrote the command select disk 0 beforehand. But maybe that's not what I'm supposed to type...

AddRAM · 12 Sep 2015

After you convert it and clean it, you should be able to install windows on it using the install disc, the drive should show up as unallocated space.

Clean Install Windows 7

But the reason you can`t do anything with it, is because you did not create a partition using diskpart yet, you have to use the command "select disk 0" then follow the instructions in the link I posted above in reply #4

If you`re already in Disk 0 then just create the partition, then you can format it, set it active etc.

Read the create a partition tutorial option 2

LilWeasel · 13 Sep 2015

I have created a partition, but it doesn't matter, it just gives me the same BS, can't install windows on the drive, and in diskpart command prompt it just keeps giving me that ""There is no volume selected." garbage no matter what. I don't know what to do at this point, I feel so disheartened from this I have like zero motivation to even try anymore.

If you could perhaps write the exact commands I should type in the right order maybe I can figure out what I'm doing wrong, because obviously there's some step I'm not doing right.... =(

EDIT: At this point I'm very tempted to do one of two rather radical things.
1. Treating it with the "viking solution" by dropping my sledgehammer on this HDD.
2. Buying a small, as cheap as possible SSD drive just for installing windows on. I could perhaps get this stupid 3TB up and running later with windows installed and me able to install drivers for it.

To be honest alternative number 1 is more attractive.

Edit #2:

I kinda reined in my wrath eventually and settled for option number 2 and just placed an order of a Samsung SSD 850 Evo 250gb, hopefully I will have it by tuesday and I can finally get a closure to this hellish ordeal. One thing is for sure tho, I will never again in my life buy a product by western digital. =)

I'm sure I can get that piece of junk up and running later on tho when I already have windows installed on a disk that isn't garbage.

Thank you tho AddRam for trying so hard to get this to work for me. I will come back here and let you now how things have turned out later when I get my SSD drive. =)

Andyrids · 13 Sep 2015

Maybe that is the problem you need to load drivers for it before you install Windows.

LilWeasel · 15 Sep 2015

Ok, I get my new SSD Samsung drive today, and of course, I put it in, fire
it up, and wouldn't you know, it's giving me the same BS as the other drive.

I don't know guys, I've never been so close to doing brutal violence to a
computer as I've been today. I have tried EVERYTHING, it just seems that
this motherboard or whatever is the cause of this BS behavior just hates
windows with a deep passion and for no reason at all wants a windows OS
on it's HDD.

It keeps yapping at the installation menu that windows can't be installed
because some BS controller that isn't enabled in Bios. The only problem
with that poor excuse is that I have looked up Bios 1000 times by now, and
tried every possible setting related to boot devices, etc that there is,
and NOTHING works. It just gives me the same crap over and over....

So, any final suggestion from you guys? Or should I go for my viking solution
I first thought about?

LilWeasel · 15 Sep 2015

I've been told to disable secure boot state in BIOS before, the problem with that suggestion though is that it's impossible to disable it in my BIOS because it's greyed out. Is there any workaround to disable it anyway?

jc836 · 15 Sep 2015

If this is a new motherboard you may well want to contact Asus and ask for their help. Failing that, it could well be that the controller has failed or the Bios is corrupted. If you can try running a Linux Live CD in Demo mode to make sure that the drives can be seen.
Good luck

LilWeasel · 15 Sep 2015

Thank you for your reply Jc836.

Yep, it's a brand new board, yeah I might have to contact ASUS about this, may very well be something wrong with this MB.