New
#11
Hi, You don't need to burn the ISO to a DVD to make a clean install, if you have downloaded the ISO on to the computer that you are going to install it on.
What I do is this
1, I download the ISO,
2, I open up Winrar,
3, I drag the ISO straight into Winrar,
4, When it is in Winrar, I double Click on the ISO, and let Winrar do the biz.
5, It then gives you a Setup.Exe, and I click on that and install it on to a partition
1. jfar: i'm booting for a DVD because that is how i'm installing this fresh system. I'm not using virtualization software.
2. quertiy: i read the link you posted about the HD being the issue. I don't think that applies to me since i have a 500W power supply and a dedicated power connection to the HD that is not sharing with anything else.
Do I need to uses HD drivers to install the OS do you think? Is there a way to build them into my USB load?
i'll try safe mode too.
Last edited by Brink; 19 Jun 2009 at 22:28.
I've read all the replies to your post, and while some of them hold merit, I'm amazed that nobody pointed out the obvious - just look at the filename of the ISO you downloaded:
The last bit, "SoLoR-custom" should have gotten the alarm bells ringing for you. As it is, this implies that the internals of this ISO have been customized (for unknown reasons), and could therefore be the root cause of you troubles.7260.0.x86fre.win7_rtm.090612-2110.client_en-us.ultimate.SoLoR-custom.iso
My advice to you would be to go to the official Microsoft Windows 7 site, and download it from there. Sure, it is the older build 7100, but it is an official Microsoft-endorsed release. Chances are your problems will all go away if you try using that instead of a suspect download...
for me SoLoR,s 7260 build works 1000000000000000% great iam happy
Suspect download???
Theres nothing suspect about SoLoRs ISO, we all know its modified. As mentioned that's a hdd error, not an issue with the ISO.
there's nothing wrong with the iso. SoLoR is a trusted member who created the iso from the original vhd image.
That error message is caused by the registry attempting to rename a file and is unable to.
re running setup and choosing repair should fix it. otherwise, reformat and reinstall.
I hope your right, as a trusted member here on the site gave me the link to the very same and I have no reason not to trust him.
It's damn hard to know what your getting if you don't have/know the exact name of the original ISO made by some one, in this case, SoLoR.
Is that how SoLoR named it?