Your original thread title was too long, so I was cutting it. You said the boot error appears since your Windows update.
Go into your EFI / BIOS settings and check the boot order of partitions. Some Windows updates change it, but that's not our fault.
pspablo_pl Please edit your post. Only English language is allowed.
PS: Thanks.
Please always use the forum search before starting a thread: results.
Check the microSD for errors before you re-install LE on it.
Maybe the internal Bluetooth broke. Check it with a different Bluetooth device, if you have. An external Bluetooth adapter is a cheep replacement.
Unfortunately I can't give you an advice, which adapter to buy, because I don't use WiFi. Maybe another user can help.
Disable audio pass-through at Settings -> System -> Audio.
Surprise, it's a Realtek: 
kernel: usb 1-1.1: New USB device found, idVendor=0bda, idProduct=c811, bcdDevice= 2.00
kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
kernel: usb 1-1.1: Product: 802.11ac NIC
kernel: usb 1-1.1: Manufacturer: Realtek
kernel: usb 1-1.1: SerialNumber: 123456I can't find the chipset anywhere (incl. shop descriptions). That's strange.
PS: I don't trust those "Bros Trend" bros: SerialNumber: 123456 
@DaFlex that's running a 64-bit OS in a container (on 32-bit userspace) so not really a solution that works.
Could the opposite, a 32 bit container at 64 bit, work for us?
PS: It seems like it's possible:
We’ve created a sample project to demonstrate that for the first time ever, you can now install 64-bit balenaOS on the Raspberry Pi 4, and run a combination of both 32-bit and 64-bit containers together simultaneously; notably the exclusively 64-bit MongoDB image.
Due to the increased RAM usage probably only an option for RPi 4B.
I'm using exactly the same XML to get "ContextMenu" on my RPi 3B+, and it works fine. Maybe you additionally have a keymap editor installed, which "overwrites the XML overwrite".
You can mark this thread as solved by editing your initial post.
Then we are probably still outside Kodi runtime. Try this at autostart.sh:
#!/bin/sh
(
kodi-send -a "RunScript(/storage/.kodi/userdata/scripts/start_music.py)"
) &Seems there is no chances to get this device to work except waiting for the mainline kernel driver?
Already tried the latest milhouse build?
It seems like the context of autoexec.py is outside Kodi runtime, so the XBMC lib isn't usable from there.
To start the script right, do this:
#!/bin/sh
(
python /storage/.kodi/userdata/scripts/start_music.py
) &#!/usr/bin/python
import xbmc
xbmc.executebuiltin('PlayMedia("/var/media/Music1.5.2020/bbc1xtra.strm")')Does that add to or replace the default settings?
Both. It adds a non-exiting definition or replaces an existing one.
What would be the accepted Remote key for a mouse Right-Click?
Wrong question 
. The question is, which Kodi action is linked to the right-click.
If "ContextMenu" doesn't performs the right action for your needs, selects yours here.
An example if I have the "side" menu open and need to go back.
Is that correct?
Using the "Back" action is correct. You probably need different Kodi actions. Define different actions on your remotes color keys.
No log file needed this time. Login by SSH and start autoexec.py manually:
python /storage/.kodi/userdata/autoexec.pyPost the command line answer of that call.
I found this instruction how to setup a 32 / 64 bit hybrid system on RPi: raspberrypi.org forums.
Hmm, Google must have that DRM algorithm from somewhere. Why do they get it, but we don't? We are good and legal, too. Maybe we just have to ask them.