It did not detect HDD obliviously as Legacy does not support GPT drives Some more duct tape and voila good as new just with other drive Popped that drive(Other WD BLUE drive not TOSHIBA) from USB and put it back in Laptop I used WINtoUSB by hasleo software to install Windows 10 GPT UEFI on that Dell Drive in USBĬonnected the USB WINDOWS 10 GPT UEFI drive to laptop So I popped that old drive out and put it in that SATA to USBĪnd because I cannot get the installation media to work I just wanted to check if system recognizes others drives too and it did Tried to boot on SafeMode/Without GPU drivers but none stopped BSOD on ati.sys(something) (I was a drive from an old Dell Laptop I had, Laptop mobo had gone bad so I salvaged the HDD ) So I switched to Legacy boot and it booted only to be crashed in ATI driver section It had windows 7 Ultimate MBR from a legacy bios system though So I removed all the duct tape and popped out that drive and Put in another WD BLUE HDD I had around So I booted into BIOS(Insyde) and cleared UEFI So now that I knew HDD was fine I popped it back in used some duct tape to put thinks together and tried to boot again (I felt more like a smart ass now about buying that SATA to USB3.0) (Am so sorry for calling you a bastard HDD Toshiba, I was wrong, I made the call to early) So I popped in that bastard Toshiba HDD in there and connected to the other laptopĪnd to my surprise everything is normal, it got detected and all data was safe and sound I had a STORITE SATA to USB3.0 for such situation(Smart eh, I felt so good on that useless purchase now) ( In the mean while thinking How can you do this to me Toshiba I trusted you and you betrayed me ) So I pried open the laptop with crowbar to get to my precious data in that failing bastard HDD Now I got worried that something might have gone wrong with the HDD(I had important data in there) Got my other laptop and created a USB windows 10 installation media and tried to boot from a USB 2.0 port(so not to face any issues of USB 3.0 drivers) I said to myself calm down it might be just windows corruption and tried to restart the system 3 times I have never been so happy to see that(worried and sad) Next time I booted up, I got greeted with the love of everyone's life i.e. I will try to give as much context as possible so you guys can give me some insight on the issueĮverything was working great until yesterday when I had and power outage and my laptop battery died on me Thanks again fujianabc for your work, even that this thread is now 4 years old is still valid.I have been having issue with booting windows 10 with UEFI, I used RMPREPUSB to format the USB sticks so they were listed as HardDrives in BIOS. I created two USB Sticks, one (32GB) booting with Windows 7 SP1 圆4 and the other USB stick (16GB) booting with Windows 7 32bit. LAST UPDATE: Finally I made it work using another PC that was running Windows 7 64bit as a host. Error occured when loading the registry Press any key to exit. Processing the registry and usb boot watcher. 16385 Applying progressSuccessfully applied image.Total elapsed time: 64 min 41 sec The Wim file applied O.K. Extracting the WIM file, it needs some time, please wait.ImageX Tool for WindowsCopyright (C) Microsoft Corp. If you want to use other drive letter, please directly input the letter (e.g. After the installation, the drive letter of the OS partition will be C. Windows Vista/20 R2 Fast Installer = 2010.02.19 = Path of your Wim file: "O:\sources\install.wim" The index number: 1 Drive letter for OS partition: E: Drive letter for boot partition: E: USB hard disk or not: YES All informatition is collected! Press Enter to start installation. So far so good, it's extracting the wim and applying it.īut there is an error after applying the wim to the usb: here is the details of the messages: The installer.cmd now runs even that after selecting the install.wim and clicking the open button there is a jumping window in Windows 8.1 Enterprise64bit saying: Windows Command Processor has stopped working. UPDATE: after creating manually the file setwimpath.cmd with the following command inside (for my setup): The host is Windows 8.1 Enterprise 64bit. I can not see this file and the script is calling for it otherwise it will terminate in failure. After 4 years that I did install windows 7 64bit to usb successfully ( ) I was trying again today to install windows 7 32bit to a usb and for some reason the installer.cmd script is failing and exiting with the error can not find SetWimPath.cmd or something similar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |