A short question: When downloading the cited windows install discs at:
Windows 7 Direct Download Links, Official Disk Images from Digital River
About half way down the page near the top of the english section there is a selection:
That is the same as my system... just wanted to make double sure I downloaded the right one.Windows 7 Home Premium x64 SP1 U (media refresh) X17-58997.iso
Follow the advice of the others that have already posted etc. and then if you still have issues; post back and we can go from there.
Yes, and I do so gladly, but perhaps I am a little thicker than the average bear. I'm still not sure how to get to some of the things being suggested.
Going into the full install disc to the point of having my OS discovered and running the repair thing for fixing startup problems, well it came back with a clean report.... not much to go on there.
One fellow has suggested getting to a command line with the Install disc. I think I'm getting there wrong or something because the one I see offered puts me at X:\ on the disk... not on the actual OS. The suggestion offered was to get to the command line with the Install disc and run the command 'bcdedit /enum all >c:\bcd.txt'
At X:\ command line, nothing is known about that command. I'm guessing he is referring to a command line in the old OS but has not mentioned how to get there.... I have reported that none of the boot option are available starting with no boot disc. Including the one about the command line.
So unless there is some as yet unknown way to get to that command line, its looking like I should go ahead and reinstall from scratch.
Is that your consensus?
I specifically said you can do the repairs with the install disk, which contains System Recovery Options. So why are you saying you went ahead to buy the Repair CD from EasyBCD since you want to try to do repairs first?
I also said that what EasyBCD has to offer for sale is the Repair CD - System Repair Disk, so why do I need to look again?
The title of the "Boot" partition being "System" has nothing to do with the listings I was discussing. On PW "Boot" means it is the partition actively booting the OS, while "System" means the presently booted OS partition, which you have none. These two labels mean the opposite in Disk Mgmt. Active flag always is meant to point to the partition booting the OS.
Did you run Startup Repair 3 separate times no matter what it reports? If it won't start then you'lll need to start at the top of Troubleshooting Windows 7 Failure to Boot since it might be infected and won't repair until disinfected. Everything that can be done to repair Win7 is in those steps, leading up to if necessary rescuiing your files to Clean Reinstall - Factory OEM Windows 7.
The payoff of doing the reinstall is that if you'll stick only with the tools and methods in the tutorial, you will get and keep a perfect Win7 install better than all others. Just keep asking back questions until you are clear on everything. I am traveling now so may take a day to get back to you.
To GregRocker:
I guess I can understand a bit of testiness from you. But I did say I am somewhat thick skulled. Still when a person like you who is seriously well versed in the area under discussion.... it must be a bit hard when presented with all the makings of a down home knucklehead!
I am a little overwhelmed by all the info that came out in this thread... What seems to you, to be obvious, simple and hard to messup, may look a bit different to me.
I chickened out and went for a full reinstall, deleted all partition and it turned out to be pretty much a breeze to get the install done.... My license plugged in and off we go.
So thank you ALL who had the patience to last it out.... It has improved my tiny windows skill set immeasurably.
Now the real work of getting the new install up to speed and a graphics editing work station... and personal desktop can continue.
Thank you Thank you Thank you Thank you Thank you ALL
Glad to hear it Harry. Let us know how it performs.
Good work!
Thanks.... I can say so far what I've observed... and I've already made numerous changes installs etc, is that that pause that happens between when the signin at the User signin screen and the when the desktop becomes usable has shrunk down to probably 2 seconds or less.
Whereas before the crash and burn... it had gotten to be a really hefty pause.... while all the baloney looking for god knows what did there thing... then finally the desktop would appear but it would still be another 30 seconds or so before the mouse quit turning into an hourglass while daemon timed out or what ever it is they do that takes up a lot of time.
So that has become much much faster.
It seems more agile all around.
Quote