Several people have reported that CPU samples were not showing up in Timing Captures starting a few months ago. This ended up being an issue with Windows Defender that has been fixed in a Windows servicing update that was released earlier this week. A description of the fix and how to verify that you’ve received it is available on the Visual Studio community site.
If you have the required update and are still seeing this issue, please let us know!
Steven.
Windows Defender continues to be the #1 piece of malware found on any given PC :-/
Between this, erroneously flagging the powershell.exe process last summer, the conhost process earlier this year, and the massive performance penalty you face when you leave Real Time protection enabled during building software, how is Windows Defender not shuttered by now?