This is a test, at the grub menu highlight the windows entry and press e for edit
Change the
set root='hd1,msdos2'
To
set root=‘hd1,msdos1’
Delete all the lines from if to fi
Press ctrl-x to boot

Thank you C Savvy

Yes i will try to have a go and get to grips with this code/"text tags. I did wonder that but when EFI first came I disabled secure boot in the bios and have had no problems. This original started when I first installed Ubuntu 20.04LTS everything went ok. I updated grub D/L google and sorted my dual screens and added various Ubuntu apps. Then the key board stopped working. Tried 3 other keyboards no joy. no solutions after 3 days then by luck I opened ubuntu apps and saw a keyboard app named "input method". clicked on it and keyboard immediately started working. That icon in the apps has now gone. I had concerns about 20.04 so put 18.04 back. That installation ended up with windows on 2 disks sdb1 and sdb2 and ubuntu started by entering bios and clicking CD drive. during those 3 days I could not install anything as I could not input the personal details required to proceed.Intermittently the keyboard worked but only on the live disk. as soon as I tried to install keyboard stopped working again Thats why I thought there was a connection to this problem. Thank you for your help.

Hi did as requested trebled checked and definitely set as instructed. would not boot up grub menu still saying windows on sdb2

no did not boot up. grub saying windows sdb2 tried a restart but no joy clicked windows in bios boot up but goes to a black screen saying grub rescue

That doesn't change what the grub menu says, what happenes after hitting ctrl-x while in edit mode after making changes. after changes should look something like this

Did this system come with windows 10 installed originally? If so why is windows drive not /dev/sda and not a gpt type disk label?

the screen just flickered a bit and remained in edit mode

sorry for the wait checking now

try it with deleting these two lines
in additon to the other lines

Post 6 output clearly shows that both the windows hard drive and the Ubuntu hard drive are msdos. In the original post, the output from updating grub clearly shows windows was detected. There is no reason why windows boot files could not be on the second partition (sdb2). Time for boot repair. Go to the site below while you are booted into Ubuntu and download boot repair using the 2nd option explained on the page. After downloading and running it by selecting the Create Boot INfo Summary option, you will get a link which you can post here for help as it will show a lot of details about your system. Do NOT try to make any repairs.

https://help.ubuntu.com/community/Boot-Repair

Tried the boor repair disk. waited 14 minutes for it to go into working mode but it did not. I will try again. Thank you You are correct as when I first discovered that clicking the disks in the bios boot order would start the OS. At that time windows in grub showed on both sdb1 and sdb2 Both booted into windows, no problem

CP Im so sincerely sorry for leaving you hanging. I wanted to keep the edit window open to compare. tried to start my old PC to open LQ but my password had changed so it was not on google password list, plus other stuff all at the same time. I do apologise and thank you for your patience.

went back into Edit menu ctrl and X and it booted into ubuntu but still black screen after restart.

My PC is custom built. I had windows 7 so downloaded the free windows 10 disk from microsoft and installed it myself. I think that was just over 5 years ago.

I will try Boot Repair Disk again and if no joy I will input the last code you sent (partool)

I have made condensed notes of the edit menu. unfortunately there does not appear to be any methods of copying the data so I typed it out. Not ideal but I think enough to give you a good idea of the changing data. Some different if and fi have appeared.

sincere thanks for your time and patience

post the ouput of

It's a pretty simple tool. Did you read the section on Using Boot-Repair? Do you have an internet connection? You won't get the link info if you do not.

I have used Boot repair disk with good success in the past.This time I went to Sourceforge and updated the version I intended to use. However after a very long time. it did not boot into front page, instead a notice appeared saying it needed updating. updated and it continued No graphical image so could not get the paste address.
if did not work. no change. Yancek I would not have been able to even get on Linux Questions without the internet.

CP input parttool ${root} hidden as you requested response "setting partition" to 0x93
drivemap -s (hd0) ${root} drivemap to -s (hd0) $ {root} hit Ctrl & X booted up into Ubuntu. Now will shut down to see if it boots up.

Thanks for everything will let you know in a few minutes

Hi CP output from lsblk as requested


sda
├─sda1
│ ext4 879c701a-e87f-4086-bcb6-4773682b3aed 70G 10% /
├─sda2
│
├─sda5
│ swap e05efded-36c7-4c80-8be0-b704f2b10ad0 [SWAP]
└─sda6
ext4 a500aeed-c850-4c49-9bfb-e83070b64ef2 15.2G 11% /home
sdb
├─sdb1
│ ntfs System Reserved
│ 0AAA3702AA36EA39
├─sdb2
│ ntfs EEF03A41F03A0FF7 130.4G 24% /media/mar
├─sdb3
│ ntfs 2CDE9DABDE9D6E38
├─sdb4
│
└─sdb5
vfat 066B-7457
sr0


Did this too hoping to give you a better picture UUID still fragmented but we are getting there thanks to you

sudo blkid | grep UUID=

dev/sda5: UUID="e05efded-36c7-4c80-8be0-b704f2b10ad0" TYPE="swap" PARTUUID="03f23f0e-05"
/dev/sda1: UUID="879c701a-e87f-4086-bcb6-4773682b3aed" TYPE="ext4" PARTUUID="03f23f0e-01"
/dev/sda6: UUID="a500aeed-c850-4c49-9bfb-e83070b64ef2" TYPE="ext4" PARTUUID="03f23f0e-06"
/dev/sdb1: LABEL="System Reserved" UUID="0AAA3702AA36EA39" TYPE="ntfs" PARTUUID="3767dd0a-01"
/dev/sdb2: UUID="EEF03A41F03A0FF7" TYPE="ntfs" PARTUUID="3767dd0a-02"
/dev/sdb3: UUID="2CDE9DABDE9D6E38" TYPE="ntfs" PARTUUID="3767dd0a-03"
/dev/sdb5: UUID="066B-7457" TYPE="vfat" PARTUUID="3767dd0a-05"