We are working on this issue, we finally were able to reproduce it. It is due to a new Preview update Microsoft released some days ago for Windows 11 24H2 users:
KB5046740
The provider of the faulty component we are using has been advised too and they are working on the issue too.
Hopefully, we’ll get a fix very soon. The sole workaround currently confirmed by users is to roll back Windows to remove that specific update.
Since it is a Preview update, it is also possible that Microsoft may change it too.