LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   General (https://www.linuxquestions.org/questions/general-10/)
-   -   Windows 10 disappeared after updating Ubuntu (https://www.linuxquestions.org/questions/general-10/windows-10-disappeared-after-updating-ubuntu-4175642585/)

lfs1121 11-18-2018 04:10 AM

Windows 10 disappeared after updating Ubuntu
 
1 Attachment(s)
Hello All,

I was on a dual boot using Windows 10 and Ubuntu. I installed Ubuntu alongside my Windows OS. Recently, I upgraded my Ubuntu OS to its new version Version 18.04. Below is the Ubuntu OS version running on my machine. After this upgrade my Windows disappeared from the boot menu. When I start my machine it only displays the login option for Ubuntu and Advanced option for Ubuntu. Windows is no longer there, however, when I check the disk partitions I see that my Windows 10 partition is still there. When I open the GParted menu on Ubuntu it displays the Windows 10 partition.
Code:

$ lsb_release -a
No LSB modules are available.
Distributor ID:        Ubuntu
Description:        Ubuntu 18.04.1 LTS
Release:        18.04
Codename:        bionic

I am a newbie on Ubuntu. I started using Ubuntu for most of the course requirement in my school.

Any help would be highly appreciated to recover my Windows and data on it.

P.S I have also attached a screenshot of GParted showing my Windows partition.

Best,

enorbet 11-18-2018 08:18 AM

Did you label the two ntfs partitions "boot" and "diag"? It is my guess that the second ntfs partition, currently labelled "diag", is Windows' hidden boot partition and needs to be flagged to "boot". GParted will handle that easily and proper though you might have to run "update-grub" to let the change be recognized but I'm not certain since I use LILO.

If you'd prefer checking this out, besides being able to see what's on there and determine if such files as "ntldr" are present there and not on the partition you have labelled as "boot", you can download and install any number of live operating systems on a CD, DVD, or USB thumbdrive (affecting nothing on your hard drives) boot any of those to either Linux or what is often called MiniXP these days, and run all manner of diagnostic apps OR you could simply select one of the Boot Managers, like PLOP, which will allow you to engage any and every partition to see what boots and what doesn't.

One great example of such tool-heavy Live Distros is Hirens Boot CD which boots a scaled down version of Windows, a scaled up version of DOS, and a full Linux Desktop, each just laden with superb tools. BTW, these tools are also "sharp" so don't just explore and "try stuff" without a bit of research but diagnostic apps and boot loaders are entirely benign and safe. No worries.

lfs1121 11-18-2018 10:27 AM

Quote:

Originally Posted by enorbet (Post 5927303)
Did you label the two ntfs partitions "boot" and "diag"? It is my guess that the second ntfs partition, currently labelled "diag", is Windows' hidden boot partition and needs to be flagged to "boot". GParted will handle that easily and proper though you might have to run "update-grub" to let the change be recognized but I'm not certain since I use LILO.

If you'd prefer checking this out, besides being able to see what's on there and determine if such files as "ntldr" are present there and not on the partition you have labelled as "boot", you can download and install any number of live operating systems on a CD, DVD, or USB thumbdrive (affecting nothing on your hard drives) boot any of those to either Linux or what is often called MiniXP these days, and run all manner of diagnostic apps OR you could simply select one of the Boot Managers, like PLOP, which will allow you to engage any and every partition to see what boots and what doesn't.

One great example of such tool-heavy Live Distros is Hirens Boot CD which boots a scaled down version of Windows, a scaled up version of DOS, and a full Linux Desktop, each just laden with superb tools. BTW, these tools are also "sharp" so don't just explore and "try stuff" without a bit of research but diagnostic apps and boot loaders are entirely benign and safe. No worries.

I ran update-grub several times but it did not fetch. I also ran some boot repair mentioned here https://help.ubuntu.com/community/Boot-Repair
I followed option 2 with the following instructions
Code:


sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair

At the end of the process, it generated a note and I saved it. It mentioned that if the problem did not fix, I email the link it generated to boot.repair@gmail.com Here is the link http://paste.ubuntu.com/p/HhMdNJkYbs/

I am waiting to receive from their end.

enorbet 11-18-2018 11:33 AM

Quote:

Originally Posted by lfs1121 (Post 5927353)
I ran update-grub several times but it did not fetch. I also ran some boot repair mentioned here https://help.ubuntu.com/community/Boot-Repair
I followed option 2 with the following instructions
Code:


sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get install -y boot-repair && boot-repair

At the end of the process, it generated a note and I saved it. It mentioned that if the problem did not fix, I email the link it generated to boot.repair@gmail.com Here is the link http://paste.ubuntu.com/p/HhMdNJkYbs/

I am waiting to receive from their end.

OK but did you change the flags on the ntfs partitions before you ran update-grub? or do you know for a fact that you overrode the default of creating a hidden boot partition making your current flags accurate? I suspect not.

syg00 11-18-2018 10:22 PM

There are several inconsistencies here.
- I find it hard to comprehend Win10 on a nvme disk that is not gpt. Was this a Win10 machine or Win7/8 that was upgraded to Win10 ?.
- No boot info summary
- os-prober can't find Windows loader code.

It looks like a "legacy mode" install (or update) has been done over the top of a UEFI (gpt) install. So that's screwed the partition table and wiped out what was the EFI partition /dev/nvme0n1p1. There is no way that should be ext4 if this was originally a Win10 machine.

You might be able to get to recover your data, annd you might be able to boot the recovery partition i you don't have any other Win10 media to recover from - I always create a recovery USB for myself.

lfs1121 12-04-2018 06:50 AM

Quote:

Originally Posted by syg00 (Post 5927535)
There are several inconsistencies here.
- I find it hard to comprehend Win10 on a nvme disk that is not gpt. Was this a Win10 machine or Win7/8 that was upgraded to Win10 ?.
- No boot info summary
- os-prober can't find Windows loader code.

It looks like a "legacy mode" install (or update) has been done over the top of a UEFI (gpt) install. So that's screwed the partition table and wiped out what was the EFI partition /dev/nvme0n1p1. There is no way that should be ext4 if this was originally a Win10 machine.

You might be able to get to recover your data, annd you might be able to boot the recovery partition i you don't have any other Win10 media to recover from - I always create a recovery USB for myself.

Hello,

Yes, this was originally a Windows 10 machine and I installed Ubuntu later. I have a backup of all the data on my Win10 but not a backup of the OS itself. Even if I have to reinstall a new Win10, I am willing to do that.

enorbet 12-04-2018 10:57 AM

You should be able to view the data on each partition from Ubuntu. This might require checking to see if the Windows Boot Partition is flagged "Hidden" but toggling that will have no consequence just for temporary reading file names to check. There are admittedly other inconsistencies that should be addressed but first I strongly suspect the Win 10 OpSys is still intact. Linux does not by default delete other systems. If as I suspect, this is the case all you need do is repair the boot partition. Without changing anything you should be able to verify from Ubuntu (File Manager) that the main Win10 structure is intact.

There is The Windows Way of doing this https://www.howtogeek.com/howto/3252...ader-problems/ (same for Win10 only slightly different for both 7 and 10 on UEFI systems) and also numerous live CD/Thumbdrive repair disks/Utilities as well as some that will run right from Ubuntu. There should be no need for any expense other than a little time. I have yet to see a laptop come from the factory without some repair option. Once Windows Bootloader is repaired/restored you can add or delete Ubuntu as desired, or if UEFI, just leave that as is, though you might do well to research UEFI boot configuration for precise instruction.


All times are GMT -5. The time now is 09:20 AM.