os-prober 1.81ubuntu1

I suggest you report a bug. This will inform the package mainteners

Have you considered trying to manually install the 1.81ubuntu1 version on your system?

If it works, I'll do it, but I would like it to be updated from the repository

An update of a package in an Ubuntu release that has already been published (like 22.04), will be done only in specific cases.

If you see a problem with recognizing the Windows 10 efi bootloader, then you should create a bug report and leave it to the developers how they solve it.

If the developers conclude that an upgrade to os-prober 1.81ubuntu1 is the best solution, then they will do that, but usually in Ubuntu other options are selected, like patching the existing version with a fix that solves the problem without a complete version update.

Hmm, everything is just like the classics, but when you turn it on it doesn’t work.

efibootmgr -v

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0004,0001,0003
Boot0000* neon HD(1,GPT,0ccb77ce-908b-cf44-914a-8c95cf2ff938,0x1000,0x96000)/File(\EFI\neon\shimx64.efi)
Boot0001 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-a648-bd47664c8012)AMBO
Boot0003 USB BBS(USB,,0x0)AMGOAMNO..........G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2....................A...............................L..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2......AMBOAMNO........y.G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2....................A.......................L..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2......AMBOAMNO..........G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2....................A...............................L..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2......AMBOAMNO..........G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2....................A...............................L..Gd-.;.A..MQ..L.G.e.n.e.r.i.c. .S.T.O.R.A.G.E. .D.E.V.I.C.E. .9.6.0.2......AMBO
Boot0004* Hard Drive BBS(HD,,0x0)AMGOAMNO........o.S.A.M.S.U.N.G. .S.S.D. .8.3.0. .S.e.r.i.e.s....................A...........................>..Gd-.;.A..MQ..L.0.S.K.W.Y.N.B.A.0.C.8.1.3.9. . . . . . ......AMBOAMNO........o.T.O.S.H.I.B.A. .H.D.W.D.1.0.5....................A...........................>..Gd-.;.A..MQ..L. . . . . . . . . . .8. .H.7.J.5.Z.6.S.B......AMBO

Boot0004 Win 10 Drive , grub can`t see tightly

I am not sure whether I correctly understand your comment #5
Is that the situation after installing os-prober version 1.81ubuntu1?

I do not think that a change in os-prober will result in a change in the output of efibootmgr.

os-prober is used to identify operating systems for including in the grub menu.
efibootmgr is reading the UEFI area of your computer's BIOS.
That are two completely different things.

What is the output of the command
os-prober

efibootmgr -v output this status , sudo update-grub not recognized win10 efi , uefi The bootloader sees win 10 efi and calmly loads it, but I want to make win 10 efi appear in grub and I can’t get it

What is the output of

sudo update-grub

Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/99_breeze-grub.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found theme: /boot/grub/themes/breeze/theme.txt
Found linux image: /boot/vmlinuz-6.2.0-1014-lowlatency
Found initrd image: /boot/initrd.img-6.2.0-1014-lowlatency
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
done

I already asked in comment #6 without getting a response:

What is the output of the command
os-prober

os-prober nothing output

Which version of os-prober do you currently have installed?

Version: 1.81ubuntu2

Do you get any output related to os-prober in the system logs with the command sequence

os-prober
sudo dmesg | tail

[ 26.922606] Bluetooth: RFCOMM socket layer initialized
[ 26.922621] Bluetooth: RFCOMM ver 1.11
[ 117.629439] perf: interrupt took too long (2526 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[ 174.499842] perf: interrupt took too long (3172 > 3157), lowering kernel.perf_event_max_sample_rate to 63000
[ 273.741313] perf: interrupt took too long (3973 > 3965), lowering kernel.perf_event_max_sample_rate to 50000
[ 670.002986] perf: interrupt took too long (4984 > 4966), lowering kernel.perf_event_max_sample_rate to 40000
[ 3638.079756] SGI XFS with ACLs, security attributes, realtime, quota, no debug enabled
[ 3638.119544] JFS: nTxBlock = 8192, nTxLock = 65536
[ 3638.166087] ntfs: driver 2.1.32 [Flags: R/O MODULE].
[ 3638.212502] QNX4 filesystem 0.2.3 registered.

At the moment I solved the problem like this

Add an entry like this to /etc/grub.d/40_custom (make a “fake”)

menuentry "Windows" {
         exit
}

At the moment it's "clumsy" but it works

I am sorry, but I do not know a solution for you and your problem.

Just a remark: apparently a manual update to os-prober version 1.81ubuntu2 has not helped, so I think that it does not make sense to request an update in the repositories.

Hmmm UEFI raises more questions than answers