Windows 11 I downloaded a volume Amplifier app And now every time a systewm sound goes off Or play audio i get a reverb

Arthur Block 0 Reputation points
2026-09-27T00:05:35.43+00:00

Literally every Time a system Sound goes off or if I play a video or music I get a nasty reverb Causing whatever sound it is to continue on and on

Windows for home | Windows 11 | Apps
0 comments

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Alex-L 12,740 Reputation points Microsoft External Staff Moderator
    2026-09-29T07:18:20.06+00:00

    Hi Arthur Block

    Since the issue began after installing a volume amplifier app, the most likely cause is that the app installed an audio enhancement, virtual audio device, or audio processing effect that remains active even after closing the app.

    Try the following:

    1. Uninstall the volume amplifier app and restart your PC.
    2. Go to Settings > System > Sound > All sound devices, select your playback device, and turn Audio enhancements off.
    3. Open Control Panel > Sound > Playback, select your audio device, choose Properties, and disable any effects such as Echo, Reverb, Spatial Audio, or Loudness Equalization if present.
    4. If the issue persists, reinstall the audio driver from Device Manager and restart Windows.

    If you can share the name of the amplifier app and whether you're using speakers, headphones, or Bluetooth audio, we may be able to provide more specific guidance.

    Was this answer helpful?

  2. saif salahmohamed 0 Reputation points
    2026-09-27T00:28:07.3766667+00:00

    <?xml version="1.0" encoding="utf-8"?>

    <RunSettings>

    <!-- Configurations that affect the Test Framework -->

    <RunConfiguration>

    <!-- Use 0 for maximum process-level parallelization. This does not force parallelization within the test DLL (on the thread-level). You can also change it from the Test menu; choose "Run tests in parallel". Unchecked = 1 (only 1), checked = 0 (max). -->

<MaxCpuCount>1</MaxCpuCount>

<!-- Path relative to directory that contains .runsettings file-->

<ResultsDirectory>.\TestResults</ResultsDirectory>

<!-- Omit the whole tag for auto-detection. -->

<!-- [x86] or x64, ARM, ARM64, s390x  -->

<!-- You can also change it from the Test menu; choose "Processor Architecture for AnyCPU Projects" -->

<TargetPlatform>x86</TargetPlatform>

<!-- Any TargetFramework moniker or omit the whole tag for auto-detection. -->

<!-- net48, [net40], net6.0, net5.0, netcoreapp3.1, uap10.0 etc. -->

<TargetFrameworkVersion>net40</TargetFrameworkVersion>

<!-- Path to Test Adapters -->

<TestAdaptersPaths>%SystemDrive%\Temp\foo;%SystemDrive%\Temp\bar</TestAdaptersPaths>

<!-- TestCaseFilter expression -->

<TestCaseFilter>(TestCategory != Integration) &amp; (TestCategory != UnfinishedFeature)</TestCaseFilter>

<!-- TestSessionTimeout was introduced in Visual Studio 2017 version 15.5 -->

<!-- Specify timeout in milliseconds. A valid value should be greater than 0 -->

<TestSessionTimeout>10000</TestSessionTimeout>

<!-- true or false -->

<!-- Value that specifies the exit code when no tests are discovered -->

<TreatNoTestsAsError>true</TreatNoTestsAsError>

    </RunConfiguration>

    <!-- Configurations for data collectors -->

    <DataCollectionRunSettings>

    <DataCollectors>

  <DataCollector friendlyName="Code Coverage" uri="datacollector://Microsoft/CodeCoverage/2.0" assemblyQualifiedName="Microsoft.VisualStudio.Coverage.DynamicCoverageDataCollector, Microsoft.VisualStudio.TraceCollector, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">

    <Configuration>

      <CodeCoverage>

        <ModulePaths>

          <Exclude>

            <ModulePath>.*CPPUnitTestFramework.*</ModulePath>

          </Exclude>

        </ModulePaths>

        <!-- We recommend you do not change the following values: -->

        <UseVerifiableInstrumentation>True</UseVerifiableInstrumentation>

        <AllowLowIntegrityProcesses>True</AllowLowIntegrityProcesses>

        <CollectFromChildProcesses>True</CollectFromChildProcesses>

        <CollectAspDotNet>False</CollectAspDotNet>

      </CodeCoverage>

    </Configuration>

  </DataCollector>

  <DataCollector uri="datacollector://microsoft/VideoRecorder/1.0" assemblyQualifiedName="Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder.VideoRecorderDataCollector, Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" friendlyName="Screen and Voice Recorder">

    <!--Video data collector was introduced in Visual Studio 2017 version 15.5 -->

    <Configuration>

      <!-- Set "sendRecordedMediaForPassedTestCase" to "false" to add video attachments to failed tests only -->

      <MediaRecorder sendRecordedMediaForPassedTestCase="true"  xmlns="">           

        <ScreenCaptureVideo bitRate="512" frameRate="2" quality="20" />

      </MediaRecorder>

    </Configuration>

  </DataCollector>

  <!-- Configuration for blame data collector -->

  <DataCollector friendlyName="blame" enabled="True">

  </DataCollector>

</DataCollectors>

    </DataCollectionRunSettings>

    <!-- Parameters used by tests at run time -->

    <TestRunParameters>

    <Parameter name="webAppUrl" value="http://localhost" />

<Parameter name="webAppUserName" value="Admin" />

<Parameter name="webAppPassword" value="Password" />

    </TestRunParameters>

    <!-- Configuration for loggers -->

    <LoggerRunSettings>

    <Loggers>

  <Logger friendlyName="console" enabled="True">

    <Configuration>

        <Verbosity>quiet</Verbosity>

    </Configuration>

  </Logger>

  <Logger friendlyName="trx" enabled="True">

    <Configuration>

      <LogFileName>foo.trx</LogFileName>

    </Configuration>

  </Logger>

  <Logger friendlyName="html" enabled="True">

    <Configuration>

      <LogFileName>foo.html</LogFileName>

    </Configuration>

  </Logger>

  <Logger friendlyName="blame" enabled="True" />

</Loggers>

    </LoggerRunSettings>

    <!-- Adapter Specific sections -->

    <!-- MSTest adapter -->

    <MSTest>

    <MapInconclusiveToFailed>True</MapInconclusiveToFailed>

<CaptureTraceOutput>false</CaptureTraceOutput>

<DeleteDeploymentDirectoryAfterTestRunIsComplete>False</DeleteDeploymentDirectoryAfterTestRunIsComplete>

<DeploymentEnabled>False</DeploymentEnabled>

<AssemblyResolution>

  <Directory<?xml version="1.0" encoding="utf-8"?>

    <RunSettings>

    <!-- Configurations that affect the Test Framework -->

    <RunConfiguration>

    <!-- Use 0 for maximum process-level parallelization. This does not force parallelization within the test DLL (on the thread-level). You can also change it from the Test menu; choose "Run tests in parallel". Unchecked = 1 (only 1), checked = 0 (max). -->

<MaxCpuCount>1</MaxCpuCount>

<!-- Path relative to directory that contains .runsettings file-->

<ResultsDirectory>.\TestResults</ResultsDirectory>

<!-- Omit the whole tag for auto-detection. -->

<!-- [x86] or x64, ARM, ARM64, s390x  -->

<!-- You can also change it from the Test menu; choose "Processor Architecture for AnyCPU Projects" -->

<TargetPlatform>x86</TargetPlatform>

<!-- Any TargetFramework moniker or omit the whole tag for auto-detection. -->

<!-- net48, [net40], net6.0, net5.0, netcoreapp3.1, uap10.0 etc. -->

<TargetFrameworkVersion>net40</TargetFrameworkVersion>

<!-- Path to Test Adapters -->

<TestAdaptersPaths>%SystemDrive%\Temp\foo;%SystemDrive%\Temp\bar</TestAdaptersPaths>

<!-- TestCaseFilter expression -->

<TestCaseFilter>(TestCategory != Integration) &amp; (TestCategory != UnfinishedFeature)</TestCaseFilter>

<!-- TestSessionTimeout was introduced in Visual Studio 2017 version 15.5 -->

<!-- Specify timeout in milliseconds. A valid value should be greater than 0 -->

<TestSessionTimeout>10000</TestSessionTimeout>

<!-- true or false -->

<!-- Value that specifies the exit code when no tests are discovered -->

<TreatNoTestsAsError>true</TreatNoTestsAsError>

    </RunConfiguration>

    <!-- Configurations for data collectors -->

    <DataCollectionRunSettings>

    <DataCollectors>

  <DataCollector friendlyName="Code Coverage" uri="datacollector://Microsoft/CodeCoverage/2.0" assemblyQualifiedName="Microsoft.VisualStudio.Coverage.DynamicCoverageDataCollector, Microsoft.VisualStudio.TraceCollector, Version=11.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a">

    <Configuration>

      <CodeCoverage>

        <ModulePaths>

          <Exclude>

            <ModulePath>.*CPPUnitTestFramework.*</ModulePath>

          </Exclude>

        </ModulePaths>

        <!-- We recommend you do not change the following values: -->

        <UseVerifiableInstrumentation>True</UseVerifiableInstrumentation>

        <AllowLowIntegrityProcesses>True</AllowLowIntegrityProcesses>

        <CollectFromChildProcesses>True</CollectFromChildProcesses>

        <CollectAspDotNet>False</CollectAspDotNet>

      </CodeCoverage>

    </Configuration>

  </DataCollector>

  <DataCollector uri="datacollector://microsoft/VideoRecorder/1.0" assemblyQualifiedName="Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder.VideoRecorderDataCollector, Microsoft.VisualStudio.TestTools.DataCollection.VideoRecorder, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" friendlyName="Screen and Voice Recorder">

    <!--Video data collector was introduced in Visual Studio 2017 version 15.5 -->

    <Configuration>

      <!-- Set "sendRecordedMediaForPassedTestCase" to "false" to add video attachments to failed tests only -->

      <MediaRecorder sendRecordedMediaForPassedTestCase="true"  xmlns="">           

        <ScreenCaptureVideo bitRate="512" frameRate="2" quality="20" />

      </MediaRecorder>

    </Configuration>

  </DataCollector>

  <!-- Configuration for blame data collector -->

  <DataCollector friendlyName="blame" enabled="True">

  </DataCollector>

</DataCollectors>

    </DataCollectionRunSettings>

    <!-- Parameters used by tests at run time -->

    <TestRunParameters>

    <Parameter name="webAppUrl" value="http://localhost" />

<Parameter name="webAppUserName" value="Admin" />

<Parameter name="webAppPassword" value="Password" />

    </TestRunParameters>

    <!-- Configuration for loggers -->

    <LoggerRunSettings>

    <Loggers>

  <Logger friendlyName="console" enabled="True">

    <Configuration>

        <Verbosity>quiet</Verbosity>

    </Configuration>

  </Logger>

  <Logger friendlyName="trx" enabled="True">

    <Configuration>

      <LogFileName>foo.trx</LogFileName>

    </Configuration>

  </Logger>

  <Logger friendlyName="html" enabled="True">

    <Configuration>

      <LogFileName>foo.html</LogFileName>

    </Configuration>

  </Logger>

  <Logger friendlyName="blame" enabled="True" />

</Loggers>

    </LoggerRunSettings>

    <!-- Adapter Specific sections -->

    <!-- MSTest adapter -->

    <MSTest>

    <MapInconclusiveToFailed>True</MapInconclusiveToFailed>

<CaptureTraceOutput>false</CaptureTraceOutput>

<DeleteDeploymentDirectoryAfterTestRunIsComplete>False</DeleteDeploymentDirectoryAfterTestRunIsComplete>

<DeploymentEnabled>False</DeploymentEnabled>

<AssemblyResolution>

  <Directory path="D:\myfolder\bin\" includeSubDirectories="false"/>

</AssemblyResolution>

    </MSTest>

    </RunSettings> path="D:\myfolder\bin" includeSubDirectories="false"/>

    </AssemblyResolution>

    </MSTest>

    </RunSettings>

    Was this answer helpful?

    0 comments

  3. AI answer

    2026-09-27T00:05:52.2333333+00:00

    A volume amplifier app can change audio processing, so the quickest fixes are to reset Windows audio handling and reinstall the audio driver if the effect continues.

    1. Check the active output device.
      • Select the Speakers icon on the taskbar.
      • Select the arrow next to the volume slider.
      • Make sure audio is going to the intended device, such as the built-in speakers or headphones.
    2. Check that the device is not muted or misconfigured.
      • Right-click the Speakers icon on the taskbar.
      • Select the arrow next to the volume slider.
      • Select the settings icon next to Volume mixer.
      • Confirm the device is not muted.
      • Go to Start > Settings > System > Sound.
      • Under Advanced, select More sound settings.
      • On the Playback tab, select the output device, then Properties.
      • Next to Device usage, make sure Use this device (enable) is selected.
    3. Try a different audio format.
      • In the search box, type control panel and open it.
      • Select Hardware and Sound > Sound.
      • On the Playback tab, right-click the Default Device and select Properties.
      • Open the Advanced tab.
      • Under Default Format, change the setting, select OK, and test audio.
      • If needed, try another format.
    4. Restart the Windows audio services.
      • In the search box, type services and open it.
      • Restart these services:
        • Windows Audio
        • Windows Audio Endpoint Builder
        • Remote Procedure Call (RPC)
    5. Update or reinstall the audio driver.
      • In the search box, type device manager and open it.
      • Expand Sound, video and game controllers.
      • Right-click the audio device and select Update driver > Search automatically for drivers.
      • If that does not help, uninstall the device:
        • Right-click the audio device > Uninstall device.
        • Select Attempt to remove the driver for this device.
        • Select Uninstall.
        • Restart the PC.
      • Note: save open work before restarting.
    6. If the problem started after a recent update, roll back the audio driver.
      • In Device Manager, right-click the audio device and select Properties.
      • Open the Driver tab.
      • Select Roll Back Driver.
    7. If the issue continues, install the latest audio driver from the PC manufacturer’s support site.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.