Oh yes, I can get into the bios setup screen no problem by pressing delete. Although i don't see any screen telling me to do so because its all black. It also occurs when I don't go into the bios at all I get constant black screen until the Windows login.
While in the BIOS you will see the Boot Option Priorities screen. You can choose your next boot item from this list. MBR or UEFI system?
UEFI. So there is this bios selection but also another one that should pop up if I don't go into the bios. This is the one I'm concerned about that may not show on my screen, but usually there is a 30 sec timeout so I shouldn't be in limbo if I can't see it. im going to use this command to add my clone to my boot manager. "bcdboot G:\Windows /d /addlast", where G is where it is installed. From 3 days of reading that should work if the clone is bootable.
Well, I just did the above and when I rebooted the menu choice did appear and I tested the original installation first and it booted fine. I rebooted to try the new cloned drive and it failed. I got "inaccesable" error. I noticed that this ssd was plugged into my usb hub which looked like it didn't have power to the ports, they were not lit up. Next test was to connect the clone to the front usb ports which would always have power and reboot. This failed again. Error message was to use recovery tools, it then automatically shut the system off before I made a choice from the given options. Hmm...so now what to do? I used diskpart to look and see if the 100MB system hidden partition was there on the clone and it was. I used bcdedit to check the bootloader and everything looked ok. I could see both C: and my clone F: but something isn't right yet. A few days ago on their forum, Terabyte Support suggested "You may have to run the USBBOOT.TBS script against it." So I wonder what this script does. I want to do it manually to learn. It has to be using the commands I mentioned above but how I don't know yet. I have notes from the tenforums site about using diskpart and bcdboot to totally replace the system 100MB boot partition and I could do that but wasn't that all copied when the clone was made? I guess it's something to do with the physical location of the drive. If I pulled my C: and replaced it with the clone it may work but not when the C: is a M.2 drive and the clone is a ssd. I may have to do this once I give the system partition a drive letter - bcdboot c:\windows /s Z: /f UEFI assuming Z: is the drive letter I gave the system partition. Here is the bcdedit listing - Code: Windows Boot Manager -------------------- identifier {bootmgr} device partition=\Device\HarddiskVolume1 path \EFI\Microsoft\Boot\bootmgfw.efi description Windows Boot Manager locale en-us inherit {globalsettings} default {current} resumeobject {b8c2c3cb-c5de-11ee-a5ee-c20ddd518b51} displayorder {b8c2c3cc-c5de-11ee-a5ee-c20ddd518b51} {current} toolsdisplayorder {memdiag} timeout 30 Windows Boot Loader ------------------- identifier {b8c2c3cc-c5de-11ee-a5ee-c20ddd518b51} device partition=F: path \windows\system32\winload.efi description Windows 10 locale en-us inherit {bootloadersettings} isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=F: systemroot \windows resumeobject {b8c2c3cb-c5de-11ee-a5ee-c20ddd518b51} nx OptIn bootmenupolicy Standard Windows Boot Loader ------------------- identifier {current} device partition=C: path \Windows\system32\winload.efi description Windows 10 locale en-US inherit {bootloadersettings} recoverysequence {b8c2c3c9-c5de-11ee-a5ee-c20ddd518b51} displaymessageoverride Recovery recoveryenabled Yes isolatedcontext Yes allowedinmemorysettings 0x15000075 osdevice partition=C: systemroot \Windows resumeobject {b8c2c3c7-c5de-11ee-a5ee-c20ddd518b51} nx OptIn bootmenupolicy Standard
Can you again make a copied drive. After deleting all partitions on the USB drive. Don't try to boot the copy. Boot your M.2 Win10 and run the usbboot.tbs script. Just double click it and follow the instructions. Now try to boot the copied OS. Good luck.
OK, I'll try it. I couldn't find that script in the install I did. I must have skipped choosing it. I did find it on TB's site. I downloaded the file "tbosdts_pro_en.zip". Just confirm that's what I should install?
That looks ok. If you don't have the correct permissions to run the script, right click and run as admin.
OK, I just made a new clone and ran the script on it. Rebooted into the BIOS and set first boot device to the USB HDD. Rebooted and it looks like I'm booted into C: again. Here is the current Disk Management screen -Hmm...the image should display below, it does when I'm editing this post. https://i.imgur.com/CfJ5LgV.jpeg
Sure but something just crossed my mind. I still have the USB drive in the external hub. I forgot to plug it into the front panel of my desktop. I'll do that now. Here is the image - Update - No difference plugged in on the front panel. https://i.imgur.com/BDjmJR9.jpeg
Ok. The copy is in a 465 GB partition. One point. The booted OS assigns the drive letter C: so when the OS on the USB drive boots, it will be C: drive and the original OS will be something else. See what TeraByte Support thinks. I don't use the Windows boot menu for multi-booting so I'm not sure what you should do.
Yes, my C: is the 2TB drive and the clone is the 500GB drive. I'm working with TB also. I just noticed that I may still be having a disk signature collision. My event viewer says this - https://i.imgur.com/4HQdcXy.jpeg I couldn't wipe the drive like you said to do because in disk management there was only one right click option to delete the main partition, not the system or recovery partitions. I wonder if the old signature is hanging around in there.
I expected Simple Operations mode should have changed the Disk signature and GUIDs. Strange. Still, the copied OS is mounted with a drive letter so you would think the drive has a new Disk signature.
For the exercise I just did this with a MBR and a UEFI system. Easy and no problems. As I mentioned above, Windows on the USB HD boots with the C: drive letter. Don't expect the USB performance to be good. It's appalling compared with an OS on an internal drive.
Thanks for testing. Did you have to use the USBboot script on the usb drive to make it work? I'm a GPT drive on a UEFI system. I better start over and format the drive again, clone and go into BIOS to select it. Earlier today I spent an hour trying to reconnect to the internet. My network card (Intel I225V) seems to be known for intermittant connection issues. Had to reset the BIOS! Powered down for 10 minutes too. Luckily it came back.
No need to do anything to the USB drive. I had several partitions on mine before the copy. In Windows I used IFW Simple Mode to copy the OS drive to the USB drive. Remained in Windows and ran usbboot.tbs. Then restarted and used the F12 Boot Menu to select Windows Boot Manager on the USB drive. Windows loaded, slowly. Almost 10 minutes to get to a fully loaded desktop on the first occasion. 7 minutes the next time and 5 minutes the next time. Once in Windows it wasn't too bad. My internal drive was M.2 NVMe. My USB external drive was an old 2 TB WD HD. You should get better USB performance than me.
The drive I copied had 3 Windows OS and a few Linux OS. I was using BootIt to boot the various OS. It takes over from WBM to boot the various Windows OS. BootIt isn't involved in booting Windows on the USB drive.
It is really easy. Do the copy using Simple Mode. Run the script. Restart and use the F12 boot menu to boot the OS on the USB drive. Edit... WBM is in the ESP.
You asked about the script. If you don't run it, the OS on the USB drive will start to load but terminates in a BSOD. Inaccessible Boot Device. Running the script now won't fix it. You have to start again.
OK, thanks Brian. I have a newsletter to get out in the next 2 days. I'll be back to this then and try it again.
Update... I tried copying to a SSD using a USB to SATA cable. A very satisfactory result. Windows booted in 20 seconds and OS performance was quite acceptable. Almost as good as the original OS.
Thanks Brian. When you reboot into the bios to select the boot device do you see the name of the usb hard drive, like samsung, or like me I saw only "USB HDD", no actual brand name or model?
tyee, It sounds like there could be an issue with usbboot.tbs. When you run that script, is the final screen "Operation Successful". Here is my F12 Boot Menu... If "Windows Boot Manager" is not seen, the USB OS won't load.
