No alert sound on multiple machines, except on the first I installed to.

[RLK3]

Steps to reproduce

At the Powershell prompt I type New-BurntToastNotification -Text 'My message' -Sound 'Alarm8'
On my computer, the one that I first installed BurntToast to, I get a pop-up and I hear the alert sound. On any of the other computers to which I installed I get the pop-up, but no sound. Other sounds on these computers are working, like the Windows startup sound, so I know the speakers are on.
There is some difference in the installation of my computer in that I have versions 0.8.2 and 0.8.3 both installed in the *C:\Program Files\WindowsPowerShell\Modules\BurntToast* directory. I also tinkered with the module code to discover how to keep the sound from looping on for the entirety of the pop-up display. With each change that didn't work I meticulously returned it to the original form (never really removed lines, just commented out and placed an altered line below it). When I finally discovered removing the -loop switch in line 1966 of version 0.8.3 I proceeded to duplicate that with the installs to the other machines.
In short, the machine on which I did the most tinkering and have installed what could be potentially conflicting versions is the only one that works to give me sound. The others on which I minimally made alterations (the aforementioned line 1966) don't work.
I verified that the BurntToast\lib folders were complete with the necessary files, comparing mine to another. I rebooted. I'm not sure what else to look for. What am I missing? It seems that the over a dozen other machines must have something I missed.

Maybe one other thing. As a shortcut I downloaded the burnttoast.zip file only once to my machine. From there I copied to my other computers; I found that I didn't have to worry about the Unblock attribute. But did that do something to disable the sound?

I am utilizing the module in a little bit more complicated manner, but I have troubleshooted to this basic task which is giving the different behaviors on different machines.

Expected behavior

I expect to see a pop-up with "My Message" and hear the alert sound.

Actual behavior

On my computer, the one that I first installed BurntToast to, I get a pop-up and I hear the alert sound as expected. On any of the other computers to which I installed I get the pop-up, but no sound. Other sounds on these computers are working, like the Windows startup sound, so I know the speakers are on.

Environment data

Mine (computer with alert sounding):
Name Value

---

PSVersion 5.1.18362.1110
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.1110
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Other (computer on which there are no alerts sounding):
Name Value

---

PSVersion 5.1.18362.1110
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.18362.1110
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Identical output.

Mine:
OsName OsVersion OsArchitecture

---

Microsoft Windows 10 Pro 10.0.18363 64-bit

Other:
OsName OsVersion OsArchitecture

---

Microsoft Windows 10 Pro 10.0.18363 64-bit

They are the same,too.

Mine:
Directory: C:\Users\Robert\Documents\WindowsPowerShell\Modules

ModuleType Version Name ExportedCommands

---

Script 0.7.2 BurntToast {Get-BTHistory, New-BTAction, New-BTAppId, New-BTAudio...}

Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version Name ExportedCommands

---

Script 0.8.3 BurntToast {Get-BTHistory, New-BTAction, New-BTAppId, New-BTAudio...}
Script 0.8.2 BurntToast {Get-BTHistory, New-BTAction, New-BTAppId, New-BTAudio...}

Other:
Directory: C:\Users\Robert\Documents\WindowsPowerShell\Modules

ModuleType Version Name ExportedCommands

---

Script 0.7.2 BurntToast {Get-BTHistory, New-BTAction, New-BTAppId, New-BTAudio...}

Directory: C:\Program Files\WindowsPowerShell\Modules

ModuleType Version Name ExportedCommands

---

Script 0.8.3 BurntToast {Get-BTHistory, New-BTAction, New-BTAppId, New-BTAudio...}

Only the aforementioned difference in having two versions on mine.

[RLK3]

UPDATE: The issue may not have anything to do with BurntToast. I have looked further into the particular non-alert-sounding machine and it appears there is a Windows issue. Yes, the Windows startup sound is heard, but any of the other sounds in the System Sounds control panel applet are not heard. Even pressing the Test button as sounds are selected gives no sound. Interestingly, clicking on Test for the speakers in the output setup DOES give a test sound. Perhaps this was a casualty of the Win7 to Win10 upgrade... I will continue investigating this machine as well as others that have given no sound, as I have time and access to them.

[Windos]

Sorry, have been meaning to reply but works had me swamped!

There was an update (or particular update path) at some point which turned off the sound schemes in Windows. What fixed this for me is heading into the "Sound" in the control panel, then the "Sound" tab inside that. Toggle to a random scheme, click apply, toggle back to the Windows Default scheme and click apply again... that should get the sounds back again.

[RLK3]

Thanks for the reply. I would say that your fix is close to the truth. What I have found is simpler than that! I opened “Open Volume Mixer” from the System Tray speaker icon, and there it was – System Sounds were muted (Duh!). Unmuted and we’re poppin’ Singin’ Toasts! I fixed two machines this way so far. The simplest things can be so easily overlooked (“Is your machine plugged in?”) ;-P Robert L Knapp Technical & Support Services Manager McCandless Enterprises, LLC *From:* Joshua King [mailto:notifications@github.com] *Sent:* Thursday, November 19, 2020 2:46 PM *To:* Windos/BurntToast <BurntToast@noreply.github.com> *Cc:* RLK3 <robert.knapp@knappnet.net>; Author <author@noreply.github.com> *Subject:* Re: [Windos/BurntToast] No alert sound on multiple machines, except on the first I installed to. (#137) Sorry, have been meaning to reply but works had me swamped! There was an update (or particular update path) at some point which turned off the sound schemes in Windows. What fixed this for me is heading into the "Sound" in the control panel, then the "Sound" tab inside that. Toggle to a random scheme, click apply, toggle back to the Windows Default scheme and click apply again... that *should* get the sounds back again. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#137 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARX4NTIDDGDQRGAMXAT7P5LSQVYZFANCNFSM4TVEUZFA> .