you probably want to use mingw with clion, because even though clion is working for a lldb debugger for msvc, it's not worth using at the moment, and you may not really care about lldb style commands.
If you really need to use msvc due to library requirements (eg: most google libraries, or debugging tools like crashrtp), I highly recommend either using linux with clion and just compiling the windows build in a VM using ninja, and debugging using visual studios (because of the JIT debugger, AKA open the debugger when the application stops responding), or use cmake to build a visual studio project but ninja will automatically detect cmake changes on build unlike visual studio projects.
If you want to stick with windows, and you have zero interest in linux, you can use vscode as the 2nd best alternative to visual studios, because microsoft uses copyright on their debugger, so clion will never have access to the debugger within vscode cppvsdbg, and clion is forced to make a lldb debugger for msvc which isn't complete or perfect.
vscode is annoying sadly, sometimes you just want a simple IDE, not a annoying system of hotkeys on a text editor written in electron, but clion isn't much more lightweight since it's Java. But cmake support on it is good, and on linux you have vscodium to de-microsoft vscode (telemetry is not a big deal though, note vscodium does not work with cppvsdbg on windows, because of copyrights).