I have encountered this issue and reported it on July 9th, but it still hasn’t been resolved. Last week, I was able to temporarily fix it by deleting the Cursor cache folder at C:\Users\USER\AppData\Roaming\Cursor (replace with your own directory), but the problem would reappear after shutting down the computer. I also posted about this issue in my forum, but no one has responded.
Today, after deleting the cache folder again, I found that this workaround no longer works. It seems like this is a common problem with Cursor, and currently, they have no solution for it.