You can try re-downloading the ISO from Step 1 of Clean Reinstall - Factory OEM Windows 7
and write it to stick using UltraISO Software To Create Bootable USB Flash Drive which always works for me when for some reason the other methods don't.
It's writing the image now in UltraIso. Currently at 209 kb/s which will take 5 hours. That can't mean good things. I'm assuming that's not normal for UltraIso. The quickformat it did also took forever. I'll try changing the policy for the drive back to normal. I had moved it to safely remove status as a test using the previous software.
Well 209k/sec was a gift cuz now its 195. But it's working so i will let it finish. It is slowly ramping up speed now 196k. I wonder what's Spooked the Microsoft tool into a boarding the copy. I got no such resistance from Ultra I so. I will report back in later this afternoon. Thanks all.
The write speed is likely due to the flash drive's ability. Some are able to write very fast.
Did you press the Format button first per the tutorial.
If you abort it for any reason I'd try running Diskpart Clean Command on the stick.
Thanks I think it needs it after 6 years. Ya it formatted the stick successfully every time then aborted as soon as soon as it switched to copy. This drive is a super cheapy RAM stick free from Best Buy with the Geek Squad label. Definitely not built for speed. For many tasks I use my galaxy S3 which always has around 50 gigs to spare on a class 10 microSD card. Android has been tweaked to present to Windows as a USB mass storage device which moves a 10 GB file in 30 seconds. That would be nice right about now
Last edited by TrunkMonkey; 20 May 2013 at 17:27. Reason: edit
I was able to use ultraiso along with disk management console to create a bootable primary partition on my mini USB hard drive (How to Install Windows 7 or Vista from Bootable Portable USB Flash Memory Key or Hard Disk Drive). I also added another simple volume for all the software I want and need to have on hand when Windows first boots. Literally 30 seconds before I'm going to reboot into the installer, I'm making the last minute adjustments in Disk Management Console, and Kaspersky anti-virus launches is an auto scan of one of the two volumes just as Disk Management Console has created it and disk management starts throwing errors. long story short is I went from almost over the hill to falling back down the cliff in a blink of an eye thanks to Kaspersky anti-virus. I have recovered boot manager with a start up repair via the install disk. I have downloaded the ISO file for AVG recovery disk which contains utilities namely TestDisk and am currently running that. Great news is it has found both partitions however I have to change one of them back from fat32 to NTFS and the geometry of the partitions overlaps so I'm trying to figure out how to get them to line up because they are perfect copies of the partitions all the files are there its pristine I just need them to line up and and to fit on the disk. another good sign is it found doubles of each of the two partitions but with corrupt file system. so one copy has a perfect filesystem the other copy has the exact location of this partition but a corrupt file system. I hope that makes sense as I'm extremely frazzled and I'm having to do this on my phone. Luckily the s3 takes dictation pretty darn well. Does anyone know how to do this please answer quickly as I am remaining in TestDisk obviously until I figure it out. Thank you very much and I will be glad when this is over.
screenshots of what TestDisk found and the menu at the bottom of the screen.
Wasn't this self-inflicted because you didn't want to buy or borrow a $5 flash stick or $2 pack of DVD's?
What's worked regularly here to rescue lost partitions is free Partition Wizard Partition Recovery Wizard. This is an undelete process where partitions are deleted or disappear. If after scanning any appear to overlap it is not likely unless you formatted over them. Just choose them by size and have them restored.
If something else happened with "Disk Management throwing errors" then its likely not recoverable.
AHA but not so fast Greg. for those that haven't looked at the screenshots there is a pattern to discern there and I'm just about done patching things up. I will report in one things are solid. I came across quite a few of the examples of overlap because remember these numbers are somewhat inferred by whatever software is being used. There was only one actual partition able to be recovered intact so I'm pleased with test disk as it contains some deeper logic then others I've seen described. It took more than just an undelete. Thanks for the software tool as I will also be adding that to my arsenal. More soon!
Quote
