Corrupted efi partition/formatted/lost windows 10

I installed Leap 15.4 onto an HP laptop that has Windows 10 preinstalled. I do not have windows media.

During the process the efi partition was formatted and now Windows 10 is not being found as a foreign OS by Grub2. The ask is for help to get it back as an option.

The Windows partitions are still in tact and were not touched.
They are:
UUID=8A465F18465F03FB /windows10
UUID=543259BF3259A730 /windowsRE

fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000LM035-1RK1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 187623D5-C0E3-434C-A0A4-3E91D4ACA96B

Device Start End Sectors Size Type
/dev/sda1 2048 534527 532480 260M Microsoft basic data
/dev/sda2 534528 796671 262144 128M Microsoft reserved
/dev/sda3 796672 1611409407 1610612736 768G Microsoft basic data
/dev/sda4 1951516672 1953523711 2007040 980M Windows recovery environment
/dev/sda5 1790033920 1951516671 161482752 77G Linux LVM
/dev/sda6 1611409408 1790033919 178624512 85.2G Microsoft basic data

Partition table entries are not in disk order.

Disk /dev/mapper/system-root: 35 GiB, 37580963840 bytes, 73400320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/system-swap: 2 GiB, 2147483648 bytes, 4194304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/system-home: 40 GiB, 42949672960 bytes, 83886080 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Then boot Windows installation medium and repair startup.

Windows 10 came preinstalled. I do not have windows media. I am trying to locate a Windows recovery usb, but so far all of the files found are windows exe, and require windows to make the recovery tool. I just installed wine to see if that will let me run the exe and created a bootable “media creation tool”

No success in getting Wine to run the installer to create a the tool. Anything possible via the Linux route?

Are you sure that your ESP was re-formatted or are you just missing MS Windows as an option in your GRUB2 boot menu?

If the latter is the case you probably only have to enable os-prober and re-create your GRUB2 boot menu.

I am pretty sure the efi partition was reformatted. But I will try anything. What is the prompt for the os-prober? I have it set in Yast Boot manager, but it’s worth a try.

There are dozens of hits searching for “create Windows installation usb on Linux”. As long as ISO image does not have files over 4GB, simply copying content of ISO image to USB FAT32 partition should be enough for UEFI boot. Or you can use USB DVD and simply burn installation image to DVD.

Well, then os-prober will not help. If you want to you can execute (as “root” in a terminal)

os-prober

and check the output.

If you really lost your MS Windows bootloader just visit the Microsoft website and download MS Windows 10 installation .iso, put it on an USB storage device, boot from that device and use the repair option.

Show output of

lsblk -f
ls -lR /boot/efi

No need to use wine. Use woeusb instead: How to Install Windows 10 for Free - Update

Thank you Karl. I had been looking for that answer but not found it yet.

As a note to anyone else, after inserting the usb stick, unmount it.
WoeUSB from the OpenSuse software search installs it in the /usr/sbin/

The repair functions in the Win installer did not find the issue, but they did provide a command prompt. Doing some digging in Windows articles I did find the command prompts to repair the boot records. bcdboot D:\Windows /s C:

The current output from lsblk -f and ls -lR /boot/efi are below. Is there any need to reduce the number of MS entries?

lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT16 SYSTEM E8FA-DA69 229.1M 12% /boot/efi
├─sda2
├─sda3 ntfs Windows 8A465F18465F03FB 719.4G 6% /windows10
├─sda4 ntfs Windows RE
│ 543259BF3259A730
├─sda5 LVM2_m LVM2 0Bn0DQ-fqjv-iIQT-uag3-82BG-rpYo-T2xfuT
│ ├─system-root
│ │ btrfs 3f9dd369-5e51-48c8-a25b-9183cda7f9e7 29.7G 15% /var
│ │ /tmp
│ │ /usr/local
│ │ /srv
│ │ /opt
│ │ /root
│ │ /boot/grub2/x86_64-efi
│ │ /boot/grub2/i386-pc
│ │ /
│ ├─system-swap
│ │ swap 1 e81d9c42-1a6f-4158-ac9c-b6b58628198c
│ └─system-home
│ ext4 1.0 f966c8f8-6dc4-47a3-b253-471c1a8a7306 36.5G 1% /home
└─sda6 ntfs shared-data
20243B8D243B64C6 79.5G 7% /shared

ls -lR /boot/efi
/boot/efi:
total 32
drwxr-xr-x 2 root root 8192 Feb 17 16:47 $RECYCLE.BIN
drwxr-xr-x 5 root root 8192 Feb 13 14:01 EFI
drwxr-xr-x 3 root root 8192 Feb 17 15:09 Recovery
-rwxr-xr-x 1 root root    0 Feb 17 16:44 Recovery.txt
drwxr-xr-x 3 root root 8192 Feb 17 16:46 System Volume Information

/boot/efi/$RECYCLE.BIN:
total 8
-rwxr-xr-x 1 root root 129 Feb 17 16:47 desktop.ini

/boot/efi/EFI:
total 24
drwxr-xr-x 2 root root 8192 Feb 13 14:01 boot
drwxr-xr-x 4 root root 8192 Feb 17 16:43 Microsoft
drwxr-xr-x 2 root root 8192 Feb 13 14:02 opensuse

/boot/efi/EFI/boot:
total 1840
-rwxr-xr-x 1 root root 934680 Feb 13 14:01 bootx64.efi
-rwxr-xr-x 1 root root  86352 Feb 13 14:01 fallback.efi
-rwxr-xr-x 1 root root 846240 Feb 13 14:01 MokManager.efi

/boot/efi/EFI/Microsoft:
total 16
drwxr-xr-x 40 root root 8192 Feb 17 16:43 Boot
drwxr-xr-x  2 root root 8192 Feb 17 16:43 Recovery

/boot/efi/EFI/Microsoft/Boot:
total 6064
-rwxr-xr-x 1 root root   20480 Feb 17 16:44 BCD
-rwxr-xr-x 1 root root   32768 Feb 17 16:44 BCD.LOG
-rwxr-xr-x 1 root root       0 Feb 17 16:44 BCD.LOG1
-rwxr-xr-x 1 root root       0 Feb 17 16:44 BCD.LOG2
drwxr-xr-x 2 root root    8192 Feb 17 16:43 bg-BG
-rwxr-xr-x 1 root root 1561952 Jul 27  2022 bootmgfw.efi
-rwxr-xr-x 1 root root 1545560 Jul 27  2022 bootmgr.efi
-rwxr-xr-x 1 root root   65536 Feb 17 16:43 BOOTSTAT.DAT
-rwxr-xr-x 1 root root    4933 Apr 21  2022 boot.stl
drwxr-xr-x 2 root root    8192 Feb 17 16:43 cs-CZ
drwxr-xr-x 2 root root    8192 Feb 17 16:43 da-DK
drwxr-xr-x 2 root root    8192 Feb 17 16:43 de-DE
drwxr-xr-x 2 root root    8192 Feb 17 16:43 el-GR
drwxr-xr-x 2 root root    8192 Feb 17 16:43 en-GB
drwxr-xr-x 2 root root    8192 Feb 17 16:43 en-US
drwxr-xr-x 2 root root    8192 Feb 17 16:43 es-ES
drwxr-xr-x 2 root root    8192 Feb 17 16:43 es-MX
drwxr-xr-x 2 root root    8192 Feb 17 16:43 et-EE
drwxr-xr-x 2 root root    8192 Feb 17 16:43 fi-FI
drwxr-xr-x 2 root root    8192 Feb 17 16:43 Fonts
drwxr-xr-x 2 root root    8192 Feb 17 16:43 fr-CA
drwxr-xr-x 2 root root    8192 Feb 17 16:43 fr-FR
drwxr-xr-x 2 root root    8192 Feb 17 16:43 hr-HR
drwxr-xr-x 2 root root    8192 Feb 17 16:43 hu-HU
drwxr-xr-x 2 root root    8192 Feb 17 16:43 it-IT
drwxr-xr-x 2 root root    8192 Feb 17 16:43 ja-JP
-rwxr-xr-x 1 root root   31544 Dec  7  2019 kd_02_10df.dll
-rwxr-xr-x 1 root root  379192 Dec  7  2019 kd_02_10ec.dll
-rwxr-xr-x 1 root root   26424 Dec  7  2019 kd_02_1137.dll
-rwxr-xr-x 1 root root  239928 Dec  7  2019 kd_02_14e4.dll
-rwxr-xr-x 1 root root   44344 Dec  7  2019 kd_02_15b3.dll
-rwxr-xr-x 1 root root   44344 Dec  7  2019 kd_02_1969.dll
-rwxr-xr-x 1 root root   31544 Dec  7  2019 kd_02_19a2.dll
-rwxr-xr-x 1 root root   20280 Dec  7  2019 kd_02_1af4.dll
-rwxr-xr-x 1 root root  298296 Dec  7  2019 kd_02_8086.dll
-rwxr-xr-x 1 root root   18960 Dec  7  2019 kd_07_1415.dll
-rwxr-xr-x 1 root root   48952 Dec  7  2019 kd_0C_8086.dll
-rwxr-xr-x 1 root root   17720 Dec  7  2019 kdnet_uart16550.dll
-rwxr-xr-x 1 root root   27464 Jun 23  2021 kdstub.dll
drwxr-xr-x 2 root root    8192 Feb 17 16:43 ko-KR
drwxr-xr-x 2 root root    8192 Feb 17 16:43 lt-LT
drwxr-xr-x 2 root root    8192 Feb 17 16:43 lv-LV
-rwxr-xr-x 1 root root 1351520 Jul 27  2022 memtest.efi
drwxr-xr-x 2 root root    8192 Feb 17 16:43 nb-NO
drwxr-xr-x 2 root root    8192 Feb 17 16:43 nl-NL
drwxr-xr-x 2 root root    8192 Feb 17 16:43 pl-PL
drwxr-xr-x 2 root root    8192 Feb 17 16:43 pt-BR
drwxr-xr-x 2 root root    8192 Feb 17 16:43 pt-PT
drwxr-xr-x 2 root root    8192 Feb 17 16:43 qps-ploc
drwxr-xr-x 3 root root    8192 Feb 17 16:43 Resources
drwxr-xr-x 2 root root    8192 Feb 17 16:43 ro-RO
drwxr-xr-x 2 root root    8192 Feb 17 16:43 ru-RU
drwxr-xr-x 2 root root    8192 Feb 17 16:43 sk-SK
drwxr-xr-x 2 root root    8192 Feb 17 16:43 sl-SI
drwxr-xr-x 2 root root    8192 Feb 17 16:43 sr-Latn-RS
drwxr-xr-x 2 root root    8192 Feb 17 16:43 sv-SE
drwxr-xr-x 2 root root    8192 Feb 17 16:43 tr-TR
drwxr-xr-x 2 root root    8192 Feb 17 16:43 uk-UA
-rwxr-xr-x 1 root root    9796 Dec  7  2019 winsipolicy.p7b
drwxr-xr-x 2 root root    8192 Feb 17 16:43 zh-CN
drwxr-xr-x 2 root root    8192 Feb 17 16:43 zh-TW

/boot/efi/EFI/Microsoft/Boot/bg-BG:
total 160
-rwxr-xr-x 1 root root 81448 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/cs-CZ:
total 208
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80400 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45576 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/da-DK:
total 208
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/de-DE:
total 224
-rwxr-xr-x 1 root root 83256 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 83472 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46120 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/el-GR:
total 224
-rwxr-xr-x 1 root root 84280 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 84496 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46600 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/en-GB:
total 160
-rwxr-xr-x 1 root root 77112 Apr 21  2022 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 77112 Apr 21  2022 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/en-US:
total 208
-rwxr-xr-x 1 root root 77112 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 77112 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45072 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/es-ES:
total 208
-rwxr-xr-x 1 root root 81208 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45880 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/es-MX:
total 160
-rwxr-xr-x 1 root root 81208 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/et-EE:
total 160
-rwxr-xr-x 1 root root 78136 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 78136 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/fi-FI:
total 208
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80424 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/Fonts:
total 13224
-rwxr-xr-x 1 root root 3695830 Dec  7  2019 chs_boot.ttf
-rwxr-xr-x 1 root root 3878309 Dec  7  2019 cht_boot.ttf
-rwxr-xr-x 1 root root 1985767 Dec  7  2019 jpn_boot.ttf
-rwxr-xr-x 1 root root 2372900 Dec  7  2019 kor_boot.ttf
-rwxr-xr-x 1 root root  177888 Dec  7  2019 malgun_boot.ttf
-rwxr-xr-x 1 root root  175429 Dec  7  2019 malgunn_boot.ttf
-rwxr-xr-x 1 root root  145684 Dec  7  2019 meiryo_boot.ttf
-rwxr-xr-x 1 root root  144017 Dec  7  2019 meiryon_boot.ttf
-rwxr-xr-x 1 root root  165524 Dec  7  2019 msjh_boot.ttf
-rwxr-xr-x 1 root root  163496 Dec  7  2019 msjhn_boot.ttf
-rwxr-xr-x 1 root root  157064 Dec  7  2019 msyh_boot.ttf
-rwxr-xr-x 1 root root  155438 Dec  7  2019 msyhn_boot.ttf
-rwxr-xr-x 1 root root   44760 Dec  7  2019 segmono_boot.ttf
-rwxr-xr-x 1 root root   85764 Dec  7  2019 segoen_slboot.ttf
-rwxr-xr-x 1 root root   86077 Dec  7  2019 segoe_slboot.ttf
-rwxr-xr-x 1 root root   48992 Dec  7  2019 wgl4_boot.ttf

/boot/efi/EFI/Microsoft/Boot/fr-CA:
total 176
-rwxr-xr-x 1 root root 82744 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 82960 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/fr-FR:
total 224
-rwxr-xr-x 1 root root 83256 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 83472 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/hr-HR:
total 160
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80400 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/hu-HU:
total 224
-rwxr-xr-x 1 root root 83256 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 83472 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/it-IT:
total 208
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80936 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ja-JP:
total 192
-rwxr-xr-x 1 root root 69432 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 69664 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 43016 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/ko-KR:
total 192
-rwxr-xr-x 1 root root 68920 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 69136 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 43024 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/lt-LT:
total 160
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79400 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/lv-LV:
total 160
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79376 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/nb-NO:
total 208
-rwxr-xr-x 1 root root 78648 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 78864 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/nl-NL:
total 208
-rwxr-xr-x 1 root root 81208 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81424 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45368 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pl-PL:
total 208
-rwxr-xr-x 1 root root 81720 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 81720 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pt-BR:
total 208
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/pt-PT:
total 208
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80400 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 46096 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/qps-ploc:
total 56
-rwxr-xr-x 1 root root 54072 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/Resources:
total 104
-rwxr-xr-x 1 root root 92472 Dec  7  2019 bootres.dll
drwxr-xr-x 2 root root  8192 Feb 17 16:43 en-US

/boot/efi/EFI/Microsoft/Boot/Resources/en-US:
total 16
-rwxr-xr-x 1 root root 12816 Dec  7  2019 bootres.dll.mui

/boot/efi/EFI/Microsoft/Boot/ro-RO:
total 160
-rwxr-xr-x 1 root root 79672 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79880 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/ru-RU:
total 208
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80912 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 44856 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/sk-SK:
total 160
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80904 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sl-SI:
total 160
-rwxr-xr-x 1 root root 79672 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79880 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sr-Latn-RS:
total 160
-rwxr-xr-x 1 root root 80696 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80912 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/sv-SE:
total 208
-rwxr-xr-x 1 root root 79672 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79888 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45072 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/tr-TR:
total 208
-rwxr-xr-x 1 root root 79160 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 79376 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 45584 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/uk-UA:
total 160
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 80184 Dec  7  2019 bootmgr.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-CN:
total 176
-rwxr-xr-x 1 root root 64824 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 65040 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 42512 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Boot/zh-TW:
total 176
-rwxr-xr-x 1 root root 65040 Dec  7  2019 bootmgfw.efi.mui
-rwxr-xr-x 1 root root 64824 Dec  7  2019 bootmgr.efi.mui
-rwxr-xr-x 1 root root 42512 Dec  7  2019 memtest.efi.mui

/boot/efi/EFI/Microsoft/Recovery:
total 32
-rwxr-xr-x 1 root root 12288 Feb 17 16:44 BCD
-rwxr-xr-x 1 root root 16384 Feb 17 16:44 BCD.LOG
-rwxr-xr-x 1 root root     0 Feb 17 16:44 BCD.LOG1
-rwxr-xr-x 1 root root     0 Feb 17 16:44 BCD.LOG2

/boot/efi/EFI/opensuse:
total 3344
-rwxr-xr-x 1 root root      58 Feb 17 22:08 boot.csv
-rwxr-xr-x 1 root root     155 Feb 17 22:08 grub.cfg
-rwxr-xr-x 1 root root 1275904 Feb 17 22:08 grub.efi
-rwxr-xr-x 1 root root  331776 Feb 17 22:08 grubx64.efi
-rwxr-xr-x 1 root root  846240 Feb 17 22:08 MokManager.efi
-rwxr-xr-x 1 root root  934680 Feb 17 22:08 shim.efi

/boot/efi/Recovery:
total 8
drwxr-xr-x 2 root root 8192 Feb 17 15:09 Logs

/boot/efi/Recovery/Logs:
total 48
-rwxr-xr-x 1 root root   72 Feb 17 15:12 BootUX (1).sqml
-rwxr-xr-x 1 root root   96 Feb 17 15:15 BootUX (2).sqml
-rwxr-xr-x 1 root root   96 Feb 17 15:16 BootUX (3).sqml
-rwxr-xr-x 1 root root   72 Feb 17 15:16 BootUX (4).sqml
-rwxr-xr-x 1 root root   96 Feb 17 16:10 BootUX (5).sqml
-rwxr-xr-x 1 root root 1285 Feb 17 15:12 Reload.xml

/boot/efi/System Volume Information:
total 24
drwxr-xr-x 3 root root 8192 Feb 17 16:48 EDP
-rwxr-xr-x 1 root root   76 Feb 17 16:46 IndexerVolumeGuid
-rwxr-xr-x 1 root root   12 Feb 17 16:49 WPSettings.dat

/boot/efi/System Volume Information/EDP:
total 8
drwxr-xr-x 2 root root 8192 Feb 17 16:48 Recovery

/boot/efi/System Volume Information/EDP/Recovery:
total 0

Currently the system will boot into Windows, but only if I enter the bios and select Windows from the bios boot options list. Windows running again is good news, however Grub does not list Windows as a boot option.

I have used the Yast boot manager to verify the os probe is selected.
When I run os-prober, there is no output.

Are you intentionally making computer output more difficult to read? There is preformatted text button, there are <code> and [code] tags to make it properly aligned. Pick your choice.

├─sda1 vfat FAT16 SYSTEM E8FA-DA69 229.1M 12% /boot/efi
/dev/sda1 2048 534527 532480 260M Microsoft basic data

os-prober checks that ESP has proper partition type. Your ESP does not; it should have type “EFI System Partition” (GUID c12a7328-f81f-11d2-ba4b-00a0c93ec93b). Run

gdisk /dev/sda

and use t command to change the first partition type to EF00. It should look like this in fdisk output

Disklabel type: gpt
...
Device         Start       End   Sectors   Size Type
/dev/sda1       2048   1026047   1024000   500M EFI System

or in gdisk

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1026047   500.0 MiB   EF00  EFI system partition

All OS on a boot drive must use the same boot method ie. EFI or MBR/legacy. Or they won’t see each other.

Also Windows fast boot must be off since it leaves Windows partitions in a unreadable condition from Linux.

If above is meet then you should be able to reset grub from Yast bootloader to include Windows.

Sorry and no I am not. The new forum doesn’t show the code option and I was not familiar with the preformatted text button. I will put the code tags in.

I prepared a concise comment on multiboot install: Install Leap / Tumbleweed from USB Stick On Internal Disk Following this procedure never damaged any EFI System Partition and always worked since several years. Taking a short cut is risky and may result in faulty installations.

I am sorry but I am not understanding the commands. Can you please elaborate? What is the command needed?

You should see something like this:

gdisk /dev/sda
p
t
Partition number (1-3): 1
Current type is 700 (Microsoft basic data)
Hex code or GUID (L to show codes, Enter = 700):ef00
p
w

Part of that is computer output. You use the command “gdisk” (as the root user).
The the “p” subcommand asks for a printout of current partitions.
The “t” subcommand is to set the partition type. It will tell you the current type and prompt. You enter the “ef00” as the new partition type.

Then use “p” again to check the results. If they are correct, use the “w” subcommand to write the changes to disk (and quit from the command).

below is the output from running the changes above.

Command (? for help): t
Partition number (1-6): 1
Current type is 700 (Microsoft basic data)
Hex code or GUID (L to show codes, Enter = 700): ef00
Changed type of partition to 'EFI system partition'

Command (? for help): p
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Model: ST1000LM035-1RK1
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): 187623D5-C0E3-434C-A0A4-3E91D4ACA96B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 3437 sectors (1.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          534527   260.0 MiB   EF00  EFI system partition
   2          534528          796671   128.0 MiB   0C01  Microsoft reserved ...
   3          796672      1611409407   768.0 GiB   0700  Basic data partition
   4      1951516672      1953523711   980.0 MiB   2700  Basic data partition
   5      1790033920      1951516671   77.0 GiB    8E00  
   6      1611409408      1790033919   85.2 GiB    0700  Linux Data

Command (? for help): w

Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!

Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/sda.
Warning: The kernel is still using the old partition table.
The new table will be used at the next reboot or after you
run partprobe(8) or kpartx(8)
The operation has completed successfully.

hoping to come back successfully after the reboot.