having the same problem. I believe it may be related to a windows update which happened overnight last night for me (10/5/23). I believe that because I wasn't have any issues yesterday, windows updated overnight last night, then I am having trouble today. The suggested workaround works but is annoying. It's also annoying the QB is marking this thread as "solved" which it clearly isn't.
