Windows 10 Home does not boot anymore - block with EOL?

Other Distributions
1

Hello Friends

Just today in one laptop with Windows 10 Home installed

I started the machine as usual but for a first time in its all life it loads the BIOS directly instead. Therefore is not possible boot Windows 10.

What to do? I am assuming it is about EOF but is possible load the OS in peace? Of course no updates are expected anymore

Thanks in advance

2

I suspect its nothing to do with the end of support for windows 10 just that time to die.

Can you check the date and time in the bios is correct if not that would suggest a cmos battery problem

Do you have a usb with linux on that you could boot to and then see if you can mount and then disk check the hard disk. That will check the disk is ok

It would also allows you to copy important data off to an external media to then décide what path to take next

3

Had this once with my old computer (Acer Aspire XC-780). One of its disks would all of a sudden not be noticed anymore. Then, after a couple of reboots, it was all of a sudden there again.

I have thrown the computer away (malfunctioned), but I thought it was a cable issue. Perhaps this is a cable issue as well?

4

Thanks for the replies

Paul

Can you check the date and time in the bios is correct if not that would suggest a cmos battery problem

If my memory does not fail me the date and time is ok

Do you have a usb with linux on that you could boot to and then see if you can mount and then disk check the hard disk. That will check the disk is ok

Yes, I thought that: I am going to boot with Ubuntu through a pendrive and try to mount the SSD and recovery data

It would also allows you to copy important data off to an external media to then décide what path to take next

Correct 
 I have other SSD to replace this one and install Ubuntu. Funny, it is in my TODO list since months ago

Xander

Had this once with my old computer (Acer Aspire XC-780). One of its disks would all of a sudden not be noticed anymore. Then, after a couple of reboots, it was all of a sudden there again.

Agree, I assumed perhaps some key is dirty and is doing a false contact and loading the BIOS. It happened in other old laptop in a similar way. Tomorrow in the morning with the brain refreshed I will take a set of actions

I have thrown the computer away (malfunctioned), but I thought it was a cable issue. Perhaps this is a cable issue as well?

It is a laptop 
 normally the first thing to fail in a laptop is the SSD

To all

  • Should the BIOS be reset to initial manufacturer?

I’ve never entered to the BIOS for this laptop

Thanks to all

5

Generally no, its not often they are updated and should not make a difference will not solve your issue which i suspect is hard drive related and the Master boot record

6

Thanks Paul

Understood. In other network I have practically the same indication but is suggested to disable the enable fast boot option. I remember it is enabled. I am going to research about that feature

7

With an ssd that may help, but if it was working before with the switch set unlikely to be that

I am not a fan of ssd feel failure it built in ! Ready for comments on that point

8

If you disable fast boot option , it may look at more devices (eg hotplug disks) during boot, and therefore boot slower.
See here

I do not think it would be involved in your problem, but no harm in trying.

9

As usual thanks for the replies

The disable fast boot didn’t work but

I have the following advance

At the BIOS for the “Boot” Menu exists the following:

Boot
Boot Configuration
Fast Boot                      [Enabled]
Launch CSM                     [Disabled]
Boot option Priorities
	<Empty here should appear the SSD>
Add New Boot option
Delete Boot option

About “Empty here should appear the SSD” even when the USB is plugged, the boot event does not happen, always the BIOS is loaded instead. But later is possible detect both devices, the USB and SSD

For the “Add New Boot option” item appears:

Add New Boot Option

Add boot option       
Path for boot option
Boot option File Path (generated according with "Path for boot option", otherwise empty)
Create                (is mandatory have defined "Add boot option" and "Path for boot option", 
                       otherwise appears the following Warning message as: 
                       "Please set Boot Option Name and File Path")

Therefore working with the 2 first options

  • For the “Add boot option” must be written a custom name such as either “USB” or “Windows10” according the case
  • For the “Path for boot option” appears detected the SSD and USB respectively with the following set of options according the navigation

Note: The “*” is only used to improve the hierarchy

Path for boot option
	PCI(1D|0)\PCI(0|0)\DevicePath(Type 3, SubType 17)HD(Part1, Sig<possible-uuid>) <--- It is the SSD
	* <EFI>
		* <..> (to return)
		* <Microsoft>
			* <..> (to return)
			* <Boot>
				* <..> (to return)
				* ... more options ...
				* <en-GB>
				* <en-US>
				* <es-ES>
				* <es-MX>
				* ... more options ...
				* <Fonts>
				* ... more options ...
				* <qps-ploc>
					* <..> (to return)
				* <Resources>
					* <..> (to return)
					* <en-US>
					* <es-ES>
					* <fr-FR>
				... more options ... 
				* SecureBootRecovery.efi
				* memtest.efi
				* bootmgr.efi
				* bootmgfw.efi
			* <Recovery>
				* <..> (to return)
		* <Boot>
			* <..> (to return)
			* bootx64.efi
	* <System Volume Information>
		<..> (to return)
	PCI(14|0)\USB(15,0)\HD(Part2,Sig23919B4D) <--- It is the USB
	* <grub>
	  * <arm64-efi>
		  * <..> (to return)
		* <distro>
		  * <..> (to return)
		* <fonts>
		  * <..> (to return)
		* <i386-efi>
		  * <..> (to return)
		* <i386-pc>
		  * <..> (to return)
		* <mips64el-efi>
		  * <..> (to return)
		* <themes>
		  * <..> (to return)
			* <ventoy>
			  * <..> (to return)
		* <x86_64-efi>
	* <ventoy>
	  * <..> (to return)
		* <7z>
		  * <..> (to return)
			* <64>
			  * <..> (to return)
			* <32>
			  * <..> (to return)
		* <imdisk>
		  * <..> (to return)
			* <64>
			  * <..> (to return)
			* <32>
			  * <..> (to return)		
		* iso9660_ia32.efi
		* ventoy_ia32.efi
		* ventoy_x64.efi
		* iso9660_x64.efi
		* vtoyutil_aa64.efi
		* udf_aa64.efi
		* udf_x64.efi
		* vtoyutil_x64.efi
		* ventoy_aa64.efi
		* vtoyutil_ia32.efi
		* iso9660_aa64.efi
		*	udf_ia32.efi											
	* <EFI>
	  * <..> (to return)
		* <BOOT>
		  * grubia32_real.efi
			* MokManager.efi
			* grubx64_real.efi
			* grub.efi
			* BOOTIA32.EFI
			* mmia32.efi
			* BOOTMIPS.EFI
			* BOOTAA64.EFI
			* BOOTX64.EFI
			* grubia32.efi
	* <tool>
	  * <..> (to return)
	* <System Volume Information>
    * <..> (to return)

Therefore for each device

  • What is the correct .efi file?

It is for a ASUS UX501VW-DS71T (2016) in perfect conditions about hardware (500gb SSD, 16gb RAM)

Note:

  • 1 or 2 days ago before of the problem an update of Windows 10 Home was accomplished in the same way done throughout the years

Perhaps it was a coincidence or not

Goal(s)

  • Boot Windows 10 from the SSD
  • Boot from Ventoy to load the iso file of Ubuntu and mount in peace the SSD

Thank You

10

Without making any changes does it boot from an inserted usb key ?

Do. You have a usb without ventoy and just a standard linux version on to try, i experiance occasionally ventoy will not boot but other direct versions will

11

Thanks for the reply Paul

Without making any changes does it boot from an inserted usb key ?

No, it does not boot

Do. You have a usb without ventoy and just a standard linux version on to try, i experiance occasionally ventoy will not boot but other direct versions will

Yes, I have other pendrives (of course without ventoy)

So: Do you mean put in that pendrive directly the .iso file of Ubuntu?

Thank You

12

Solved

Just in case to all.

In other network (credits to “_D_D”) was indicated the following:

bootmgfw.efi for windows
BOOTX64.EFI for Ventoy

My reply was:

Thank you in worked in other way

It only was tested for the SSD 


  1. chosen the “bootmgfw.efi” and created
  2. save and exit

But it did not work, the BIOS was shown again

Again was done 1 and 2 but there is a section in the BIOS where is indicated/shown something like “Boot Overridden” where the new custom “boot option” appears, thus:

  • Was selected and pressed “enter”

Therefore the unique difference is that “Boot Overridden” was chosen instead of “save and exit” and as a consequence:

  • The BIOS closed and Windows 10 Home was loaded

Do you have idea about what happened?

I am not sure if the battery of the mobo is almost “die” to be replaced and the BIOS as a mechanism of defense is doing all this situation. Of course it is a simple theory because the date and time shown in the BIOS is correct so far

Huge Thanks for the support!

Therefore to all:

  • Do you have idea about what happened?

Thanks to all!

13

Congratulations on your repair

Just for info you cannot boot to a usb that only contains an iso file you need to create a boot médium (ventoy does this different)

For windows systems you need to do the following

But for linux mint you normally have usb création tools and you use that to unpack a iso onto the usb

It may be worth you creating a usb using one of these tool in case of future issues. I personally have a collection, including windows for such difficulties

14

It depends on the type of iso file.

  • you can copy any iso file to a CD and it will boot
 because CD readers have a built in bootloader, but
  • only a bootable iso file ( also called a hybrid iso file) can be copied to a USB stick and be bootable. Most linux distro isos are hybrid iso files, Windows iso files are not ( at least when I last checked). There is a Linux command called isohybrid that will convert a nonhybrid iso file to a hybrid iso file
 it actually adds a bootloader to the iso. Do not use it on an iso that is already hybrid.

I think this is what @callpaul.eu meant by ‘create a boot medium’

15

Thanks Neville I did not know that I always thought I must do more. I learn so much from this site