It's not a solution, it's troubleshooting that won't affect your current install in any way. The goal is to determine if the issue is with your specific installation of MB. Since the cause of the error is not determined, any proposed solution would be pure guesswork. In this case, you know other apps can receive media key presses; so I've proposed testing to determine if this is a problem affecting your specific MB installation or MB in general on your computer.
The root of the issue may be with how the key presses are being handled by Windows. If you look at this message
, you'll see that that user was able to get MB to respond to media key presses by opening Spotify at the same time. This strongly suggests that other installed applications can affect where Windows is sending the commands.Another user
found that tweaking a setting inexplicably remedied the situation.
The bottom line is that MB isn't broken, most Logitech users have no issue. The problem is that media key commands are not being received by your installation of MB. If you don't attempt to find out why, the issue will never be resolved. Everyone posting here is a volunteer, MB is free. We're spending our time to assist you, please make good use of that time.
Home Desk ~ MB 3.3 Portable • Questyle CMA400i (ASIO) • Sennheiser HD 660S (balanced) / Audeze EL-8 Closed Back / Fostex TR-X00 Ebony • Teac AI-101DA • Jamo C93 + Dayton Audio SUB-1000
Work Desk ~ MB 3.3 Portable / Tidal • SMSL SU-8 v2 • Nobsound NS-05P • THX AAA 789 • Sennheiser HD 58X (balanced)
OTG ~ FiiO M11 • Audiofly AF180 / B&O H6