EarTrumpet

EarTrumpet Troubleshooting Guide

When EarTrumpet stops behaving the way you expect, the fix is usually one of a handful of routine Windows steps rather than anything exotic. This page is the starting point for EarTrumpet troubleshooting: it summarizes the checks that resolve most issues and points to focused pages for specific symptoms like the app not opening, missing sound, or a frozen volume flyout.

Because EarTrumpet relies entirely on standard Windows audio APIs and needs no drivers of its own, most problems trace back to the Windows Audio service, a stuck tray icon, or a Windows Store install glitch rather than the app itself.

Start with the basics

If you arrived here looking for the antique hearing horn instead of the app, see ear trumpet.

  • Restart EarTrumpet from its system tray icon: right-click it and choose Exit, then reopen it from the Start menu.
  • Check that the Windows Audio service is running (see the restart steps below).
  • Open Sound settings (right-click the speaker icon in the taskbar) and confirm the correct playback device is set as default.
  • Make sure Windows itself is not muted at the system level, separate from any per-app EarTrumpet slider.

Restart the Windows Audio service

Many playback and mixer glitches clear up once the underlying Windows Audio service is restarted. Press Win+R, type services.msc, and press Enter. Find Windows Audio in the list, right-click it, and choose Restart. If it is not running, choose Start instead.

Reinstall EarTrumpet cleanly

If restarting the app and the audio service does not help, a clean reinstall often does. Uninstall EarTrumpet from Settings > Apps, then reinstall it from the Microsoft Store or with Chocolatey using choco install eartrumpet as described on the Chocolatey package page.

Check app permissions

EarTrumpet needs to run in the background and start with Windows to be useful. In Settings > Apps > Installed apps, find EarTrumpet's advanced options and confirm background permissions are allowed, and check Settings > Apps > Startup to make sure it is not disabled there.

Common symptoms and where to look

When to check the issue tracker

If none of the routine fixes work, the problem may already be a known, documented issue. Search the open and closed issues on the official EarTrumpet GitHub repository before assuming it's unique to your machine; if it isn't listed, you can file a new issue with your Windows version and reproduction steps.

Why these issues usually happen

EarTrumpet is a thin layer over Windows' own audio session and device APIs — it does not install drivers, does not run its own audio engine, and does not store a hidden configuration database. That design is why so many EarTrumpet problems trace back to something at the Windows level: the Windows Audio service stopping unexpectedly, a default playback device changing after a driver update, or a Store app losing its background permission after a Windows feature update. Understanding this relationship helps explain why the fixes on this page focus on Windows itself rather than on reconfiguring EarTrumpet's own settings.

It also explains why comparing EarTrumpet's behavior against the native Windows Sound settings panel is such a useful first diagnostic step: if a slider or device is broken in both places, the fault sits with Windows, and no EarTrumpet-specific fix will resolve it until the underlying setting or service is corrected.

Preventing repeat problems

A handful of habits reduce how often you'll need this page again. Keep Windows itself reasonably current, since audio-stack changes shipped in feature updates are the most common trigger for a previously working setup suddenly behaving oddly. Avoid running multiple volume-management utilities at the same time — for example EarTrumpet alongside a hardware vendor's own mixer app — since two tools trying to control the same audio session can produce conflicting or unresponsive sliders.

It's also worth periodically comparing EarTrumpet against the built-in mixer described in EarTrumpet vs Windows Sound settings, since knowing what 'normal' looks like in both tools makes it much faster to spot when something has actually broken versus when a device has simply changed.

Frequently asked questions

Is EarTrumpet itself usually the cause of audio problems?

Rarely. Because it uses standard Windows audio APIs and no custom drivers, most issues stem from the Windows Audio service, a corrupted install, or a Windows Sound settings misconfiguration.

Do I need to restart my PC to fix EarTrumpet problems?

Usually not — restarting the app itself or the Windows Audio service is enough. A full reboot is a reasonable fallback if neither works.

Will reinstalling EarTrumpet delete my settings?

A reinstall can reset preferences like theme or hotkeys, but it will not affect your Windows sound devices or other apps.

Where do I report a bug that isn't fixed by these steps?

Open an issue on the official GitHub repository for EarTrumpet with details about your Windows version and the steps that trigger the problem.

Still stuck? Grab the latest build from the EarTrumpet download page and try a clean reinstall.