Of course that's how we report issues, but MS never responds directly to the user, so we post here for discussion and possible fixes on our end.
For myself, I found some old discussions from a similar issue in 2015 that were resolved by repairing system files (either with sfc/dism or by...