Forked from dknoodle/Windows Defender Exclusions VS 2017.ps1
  1. Perfwatson2 Error
  2. Perfwatson2 What Purpose

Write code using code completions, debugging, testing, Git management, and cloud deployments with Visual Studio. Download Community for free today. Mspdbsrv.exe file information. The process known as Microsoft® Program Database belongs to software Microsoft Visual Studio (version 2005) or Microsoft SQL Server (version 2005 Tools) by Microsoft ( Description: Mspdbsrv.exe is not essential for the Windows OS and causes relatively few problems. Mspdbsrv.exe is located in a subfolder of 'C:Program Files'. Fashion pop art prints.


Perfwatson2 Error

Adds Windows Defender exclusions for Visual Studio 2019
Windows Defender Exclusions VS 2017.ps1

Perfwatson2 What Purpose

  1. But not this child process called PerfWatson2.exe. Now that I have disabled this option, it no longer starts with Visual Studio, and when I exit out of Visual Studio I can easily delete the folder. So thank you for sharing this tip! – Samir Oct 6 '17 at 8:48.
  2. Logman stop Microsoft-VisualStudio-Telemetry-PerfWatson2-37320 -ets. Copy link Member brianrob commented Feb 4, 2021. It sounds like you're hitting the maximum number of ETW sessions. I know that VS creates one per VS instance, so if you have a few instances, this can contribute to this issue. But in general, I am seeing more and more sessions.
  3. The VSCEIP is turned on by default. You can turn it off, or back on again, by following these instructions: In Visual Studio, choose Help Send Feedback, and then select Settings. The Visual Studio Experience Improvement Program dialog box opens. To opt out, select No, I would not like to participate, and then select OK.To opt in, select Yes, I am willing to participate,.
$pathExclusions=New-Object System.Collections.ArrayList
$processExclusions=New-Object System.Collections.ArrayList
$pathExclusions.Add('C:WindowsMicrosoft.NET') >$null
$pathExclusions.Add('C:Windowsassembly') >$null
$pathExclusions.Add($userPath+'AppDataLocalMicrosoftVisualStudio') >$null
$pathExclusions.Add('C:ProgramDataMicrosoftVisualStudioPackages') >$null
$pathExclusions.Add('C:Program Files (x86)MSBuild') >$null
$pathExclusions.Add('C:Program Files (x86)Microsoft Visual Studio') >$null
$pathExclusions.Add('C:Program Files (x86)Microsoft SDKsNuGetPackages') >$null
$pathExclusions.Add('C:Program Files (x86)Microsoft SDKs') >$null
$processExclusions.Add('devenv.exe') >$null
$processExclusions.Add('dotnet.exe') >$null
$processExclusions.Add('msbuild.exe') >$null
$processExclusions.Add('node.exe') >$null
$processExclusions.Add('node.js') >$null
$processExclusions.Add('perfwatson2.exe') >$null
$processExclusions.Add('ServiceHub.Host.Node.x86.exe') >$null
$processExclusions.Add('vbcscompiler.exe') >$null
$processExclusions.Add('testhost.exe') >$null
$processExclusions.Add('datacollector.exe') >$null
$processExclusions.Add('IntelliTrace.exe') >$null
$processExclusions.Add('CodeCoverage.exe') >$null
Write-Host'This script will create Windows Defender exclusions for common Visual Studio 2017 folders and processes.'
$projectsFolder=Read-Host'What is the path to your Projects folder? (example: c:projects)'
Write-Host'Adding Path Exclusion: '$projectsFolder
Add-MpPreference-ExclusionPath $projectsFolder
foreach ($exclusionin$pathExclusions)
Write-Host'Adding Path Exclusion: '$exclusion
Add-MpPreference-ExclusionPath $exclusion
foreach ($exclusionin$processExclusions)
Write-Host'Adding Process Exclusion: '$exclusion
Add-MpPreference-ExclusionProcess $exclusion
Write-Host'Your Exclusions:'
Write-Host'Enjoy faster build times and coding!'
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment