Reboot And Select Proper Boot Device Toshiba

[Jordan Tucker]

ThisUbuntu boot-repair tool can repair frequent boot issues you may encounter in Ubuntu like when you can't boot Ubuntu after installing Ubuntu. Or you can't boot Windows after installing a Linux distribution, or when you can't boot Ubuntu after installing Windows, or when GRUB is not displayed anymore, or some software update or hardware upgrade breaks GRUB, etc.

Four options. Either boot into the LiveCD and download the program and apply it to your boot loader, or create a Ubuntu OS install boot disk with boot-repair, or boot into a barebones boot-repair liveCD, or a boot repair USB stick.

So either pitch in and help the developers figure out why that version of Ubuntu isn't working with your hardware, or troubleshoot what is wrong by learning about how the boot process works, or try a different version of Ubuntu on a different hardware.

I had this issue today. For me the fix was to hit a different function key than the normal bios menu. This made a menu pop up that allowed me to select a device to boot from (this is also in BIOS, but this menu was a different thing that only allowed you to do that one thing). Then I selected the device "uefi: Ubuntu." This device was already selected as the first boot priority in my BIOS, but for some reason it didn't work until I used this second menu. I had used this menu before to boot from USB to install Ubuntu, so I'm thinking maybe this menu overrides what's in BIOS and it's persistent? I have no idea, but problem solved.

MiniTool OEM program enable partners like hardware / software vendors and relative technical service providers to embed MiniTool software with their own products to add value to their products or services and expand their market.

Recently, some users have reported to us that the computer asks them to insert proper boot media when starting Windows. An error message shows on the screen, saying Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key.

Since it refers to a BIOS error, this means you can get the error message on any computer running on Windows 10/8/7 and it always happens on ASUS, Toshiba, Acer, Gigabyte laptop. In most cases, you may find Windows startup is still blocked here even if you reboot the computer.

If the disk you want to start Windows 10/8/7 from is not the first boot device, please set it as the first boot device. If the Windows installation medium does not enjoy boot priority, please set CD-ROM or removable device as the first boot device.

However, if it is not UEFI but Legacy, you are using Legacy BIOS boot mode. In addition, sometimes it is CMS (compatibility Support Mode), which supports both UEFI and Legacy BIOS. In addition, sometimes it is CMS (compatibility Support Mode), which supports both UEFI and Legacy BIOS.

Generally, the partition storing Windows boot files should be set active, and it is always the system reserved partition. However, if you install Windows 10/8/7 to an appointed partition, there will be no system reserved partition, and your C drive should be set active.

Prepare a Windows repair disc and boot the ASUS, Acer, Toshiba or Gigabyte PC from the disc. Then, go to the following interface and click Repair your computer to enter the Windows Recovery Environment.

As we know, reinstalling Windows will erase all files saved on the boot partition (it is always the drive C). So, what if there are important files saved in this drive? We believe all of you would want to transfer them out at first, but how to do the transferring when Windows is unbootable?

Case 1: the user tried lots of methods found from the internet, including change boot order, rebuild MBR, set BIOS to defaults, and fix boot, but the error still exists. Then, he took out battery of COMS and then put it back. After that, the error is fixed magically.

A little background about my system. I am not totally sure what you would need, but if I am missing something, don't hesitate to ask.

I have set up Arch and encryption by following the Arch Wiki. The system itself runs fine.

Mhm, MSI are notorious for broken NVRAM implementations. Check whether you have an option to manually add an entry in the depths of its UEFI interface, if you don't rerun the grub install command with the --removable flag added. That will populate the /EFI/BOOT/BOOTx64.efi path, which should be bootable regardless. (And will potentially be overwritten on Windows updates should you run a dual boot)

Well that is nice to know... UEFI doesn't have an option to add an entry manually.

I do not really get what you mean with the "grub install --removable" command. Do I have to run this and see if that works?

Also, I am not dual booting, so not too big of a problem.

I've had this problem, I have a MSI Z170A PC MATE. I used the built in UEFI shell to load the more complete UEFI shell on the arch installer. There is a command that lets you add a boot device, that isn't available in the built in UEFI shell.

Sorry that I don't have an exact solution, it's been a while since I did that, I don't remember the commands, and it broke at some point (motherboard battery went dead). I just boot from the UEFI shell, as I don't reboot very often. I hope this points you in the right direction.

Edit: here is some more information:

The path to the UEFI shell is EFI/shellx64_v2.efi (on the second partition of the installer). There is also a v1 of the shell, but I think v2 is what I used.

The command is bcfg, here is an example from the wiki:

The 3 is the priority, starting at 0, but it probably doesn't matter too much because you can change this later in the "BIOS" (is "system setup" more correct for UEFI?). You should change the name and path to match your setup.

Hmm I'd suspect that if bcfg works then efibootmgr (which is implicitly called when using the grub-install command without the --removable flag) would work as well? Maybe you do have an entry and it's simply not default? Maybe post

Huh, maybe that would have been easier. I believe the removable flag will change the name of grubx64.efi to bootx64.efi. bootx64.efi is what windows uses (well, at least sorta), and is what the Arch installer uses. It is meant for removable devices, a place the motherboard will always check (so that if you have an installer, it will just boot).

Since I (coincidentally) switched to an SSD yesterday, I decided to make it boot correctly again. I used bcfg, and it worked for me (I needed to make it boot entry 0). What it does is it tells the motherboard where the file is... and that's exactly what efibootmgr does. I have no idea why efibootmgr doesn't work, but bcfg does.

A boot device contains the information that a computer needs before it can launch an OS. It is an actual device, meaning that it is hardware rather than software. Because of it and the boot files installed on it, your PC can launch the Windows OS for your use. With the distinct operational characteristics of this piece of hardware and the software associated with it, boot devices are special. There is no alternative for them on Windows or Mac or any other existing OS.

Faulty drives and damaged or corrupted boot files are the reasons Windows prompts you to reboot and select proper boot device or insert boot media in selected boot device and press a key. Sometimes, you really need just to perform these actions, and the problem would be fixed. Other times, you need to be a bit more technical. Other times, you need to be a bit more technical.

It could also be that you are booting from an external drive. In this case, you have either connected your PC to the drive via a cable or through an online connection. In either case, you can get rid of the reboot and select proper boot device or insert boot media in selected boot device and press a key error by repairing the connections.

The last thing you can do to fix the reboot and select proper boot device errors and others like it is to reinstall your Windows OS. You should only do this when repairing or refreshing the OS does not work. On Windows 10 or 11, you can refresh your OS by doing the following:

Whichever option you choose, you would not have to deal with Windows reboot and select proper boot device errors. But Windows would uninstall your apps, so you would also need to reinstall them after the refresh or reset process.

Fixing booting errors in Windows is not difficult. Boot devices and files are important. Common boot device errors only occur when there is a problem with these devices and files. To prevent these problems from cropping up, make sure to run hardware and software diagnostic tests frequently. You can also use Auslogics Essential Tools software pack to keep your Windows computer(s) healthy.

@pontoark, I assume yours is a toshiba satellite in which case all I can say is that I have noticed there are a lot of people struggling to install ubuntu. I recommend you search for your precise model and see what you get. It might have certain options to be set from the BIOS/UEFI firmware screen for example. Good luck!

Hola Nestor, en mi caso, en la laptop debo instalar windows 8.1, pero no deja de salir el mensaje "Reboot and select proper boot device...". No se como solucionar esto, por favor podras ayudarme? Gracias

Saludos

Nestor Urquiza is a hands-on technologist, security-first thinker and results-oriented business executive. An Electronics Engineer dealing with hardware, embedded/web software development, security, compliance and full business funnel process engineering. Keeping things simple and innovating top-down, from Marketing to Accounting.

Since so many factors could result in such an error in Windows 10/8/7, it will be challenging for most users to find the exact cause and take the corresponding measure. Luckily, in the next part, we offer different solutions for every possible cause, so you can try them one by one until the error is removed in Windows.

If the disk that loads the operating system is not set as the first boot device, then you will encounter the boot failure issue. If so, please change the boot order and set the disk as the bootable device.

3a8082e126