I was trying to look at natvis for my own uses. I am running on 17.13.6 in the same workload (winrt/winui3 native desktop). I notice natvis files were being loaded from somewhere on my system that didn't seem to line up with other things. Also, I see no indication that any natvis files included in my solution are even seen much loaded. I took a cursory look at some of the files being loaded and I think I saw some external code extensions to the debugger were supposed to be invoked but reported an error. I also got the feeling that they were trying to break through the COM system to get to the underlying data. It all became more complicated than I could deal with since there's no source or symbols. Sadly, it means that I can't see ANY of my underlying data for some reason. Everything seems to stop at an IUknown or IIinspectable with no further drill down to see the data. So my conclusion is that natvis is a great idea that's been poorly implemented for the WinRT or WinUI platform. Reminds me that what the user calls bugs, Microsoft calls a feature and when they fix the bug, it's an upgrade that'll cost you an upgrade fee. You'd think after 17 versions of VS they'd have stuff working acceptably. I mean Windows has become more stable (sort of) after only 11 versions (and I remember being excited when Win3.1 was released).