Update troubleshooting.md

docs/troubleshooting.md

@@ -245,7 +245,8 @@ jobs:
 
 Note: these logs could contain sensitive information (paths, project name...). Make sure to clean them or use the Visual Studio `Send Feedback` button. Don't put anything you want to keep private in the title or content of the initial report, which is public. Instead, say that you'll send details privately in a separate comment. Once the problem report is created, it's now possible to specify who can see your replies and attachments.
 
-## Use procdump https://docs.microsoft.com/it-it/sysinternals/downloads/procdump
+## Use procdump https://docs.microsoft.com/it-it/sysinternals/downloads/procdump on Windows
+
 Sometimes is not possible take the dump using test platform tool because the crash happen before we're able to attach to the process to take the dump self. In that situation we need a way to register for dump at process startup level.  
 To achieve it we can use procdump that will install machine wide Just-in-time (AeDebug) debugger.
 ```bash
@@ -279,3 +280,8 @@ Mode                 LastWriteTime         Length Name
 ----                 -------------         ------ ----
 -a----         8/17/2022   9:42 AM        6161605 dotnet.exe_220817_094234.dmp
 ```
+You can unistall the automatic generation running at the end of the collection phase 
+```bash 
+.\procdump.exe -u
+```
+Keep in mind that this mode will collect machine wide crash so every process in the machine that will crash will collect a dump in the folder.