Are you installing windows to it`s own dedicated hard drive ? Did you delete the partitions down to unallocated space ?
Once you do that you simply click next and the install will begin.
You have to boot from the dvd, put the dvd in the tray and restart the pc, when you see the words "Press any key to boot from dvd" press any key and the install will begin, it sounds like you`re already in windows when you try to start the install.
Clean Install Windows 7
Thanks for your quick reply. :)
To answer your question: Yes, I'm installing Windows to a dedicated SSD.
Also, I have tried deleting the partitions of that SSD down to unallocated space, but sadly that didn't work either and the installer showed the same message I described in my previous post.
Yes, this can happen to a new ssd, happened to me with my 1st ssd, boy that was fun.
SSD Alignment
WHS is our expert on installing to an ssd. I will PM him to see if he can help.
Meanwhile, read the Tutorial please :)
If your current windows 7 is on the hard drive, you need to set up your ssd 1st as explained in the tutorial. It needs to be aligned.
It`s real easy to do.
Thanks for the help. :)
The wierd thing is that when i first built this PC, Windows installed without any problems. After a while I installed Ubuntu and when I wanted to revert back to Windows 7, this issue arised. I have no idea why it's happening. When I first tried to make a bootable USB drive via Ubuntu, the installer started showing a "Missing CD/DVD driver" error, even though I don't have a CD/DVD device. Then once I made the USB drive via the Windows 7 USB - DVD tool, it didn't give this error, but it started showing the current one.
What's even stranger is that it won't even install on my HDD, no matter how much I format it.
EDIT: Tried the alignment tutorial and that didn't work either.
Ugh, why didn`t you mention you had Ubuntu involved ? That brings up a whole nother set of issues
Disk - Clean and Clean All with Diskpart Command
Whoops. Sorry about that.
As I said, I tried both clean and clean all to no avail. Other things that I have tried are: switching SATA mode from AHCI to IDE, disconnecting unneeded hard drives, switching USB ports, when (if) asked for CD/DVD drivers installing SATA drivers for the motherboard, resetting BIOS settings to default, using other ISO's. All of the above lead to the same problem.
If the install asks for sata drivers it`s usually a bad burn job.
I have never, ever once had windows ask me to install sata drivers during an install, not even with xp on new hardware.
Hopefully Greg will join in with some ideas. :)
The 1 thing you can`t do is start making a bunch of changes to the bios, once you`ve installed windows in the past (in this instance) it worked fine, so don`t start changing things, the problem is with the hard drive or the dvd`s your using, have these dvd`s worked fine before ?
Thanks for the help. :)
The wierd thing is that when i first built this PC, Windows installed without any problems. After a while I installed Ubuntu and when I wanted to revert back to Windows 7, this issue arised. I have no idea why it's happening. When I first tried to make a bootable USB drive via Ubuntu, the installer started showing a "Missing CD/DVD driver" error, even though I don't have a CD/DVD device. Then once I made the USB drive via the Windows 7 USB - DVD tool, it didn't give this error, but it started showing the current one.
What's even stranger is that it won't even install on my HDD, no matter how much I format it.
EDIT: Tried the alignment tutorial and that didn't work either.Ugh, why didn`t you mention you had Ubuntu involved ? That brings up a whole nother set of issues
Disk - Clean and Clean All with Diskpart Command
Never use CLEAN ALL on a SSD.
1) Boot CD or DVD & open a command prompt.
Command Prompt at Startup
Try one
2) type> fixmbr
Try two
3)type> bootsect /nt60 SYS /mbr
fixmbr returns: 'fixmbr' is not recognized as an internal or external command, operable program or batch file.
bootsect /nt60 SYS /mbr says that the requested system device can't be found. Disconnecting all other hard drives and running the command with ALL instead of SYS is successful, although doesn't make any difference when it comes to fixing the error.
Quote
