How to disable Bash on Windows notification sound effect





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







35















When running 'Bash on Ubuntu on Windows' it often generates the Windows notification sound while typing. Common causes are when:




  • I use auto-complete for commands (tab) and there are multiple command options,

  • or when I backspace an already empty command line.


How do I disable these sound effects?










share|improve this question































    35















    When running 'Bash on Ubuntu on Windows' it often generates the Windows notification sound while typing. Common causes are when:




    • I use auto-complete for commands (tab) and there are multiple command options,

    • or when I backspace an already empty command line.


    How do I disable these sound effects?










    share|improve this question



























      35












      35








      35


      7






      When running 'Bash on Ubuntu on Windows' it often generates the Windows notification sound while typing. Common causes are when:




      • I use auto-complete for commands (tab) and there are multiple command options,

      • or when I backspace an already empty command line.


      How do I disable these sound effects?










      share|improve this question
















      When running 'Bash on Ubuntu on Windows' it often generates the Windows notification sound while typing. Common causes are when:




      • I use auto-complete for commands (tab) and there are multiple command options,

      • or when I backspace an already empty command line.


      How do I disable these sound effects?







      windows-10 bash windows-subsystem-for-linux windows-10-v1607






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Aug 3 '16 at 15:57









      magicandre1981

      82.5k20127205




      82.5k20127205










      asked Aug 3 '16 at 6:49









      SilveriSilveri

      1,17131018




      1,17131018






















          4 Answers
          4






          active

          oldest

          votes


















          42














          The answer given by Wouter works better overall once set up, but it can be slightly confusing to get working as the correct option doesn't always appear. Follow these steps:




          • Right click the volume control in the Windows taskbar

          • Open the Volume Mixer

          • Open the Bash on Windows console

          • Do something to trigger the console making the notification sound (e.g. press backspace on an empty line). If you've disabled the notification using the alternative method below, you'll have to undo it.

          • Now a Console Window Host option should have appeared in the Volume Mixer (you might have to scroll right)

          • Mute its sound setting


          Volume mixer with Console Window Hos



          Previous/alternative method



          You can simply run the following command from within your Windows Bash shell [source]:



          echo "set bell-style none" >> ~/.inputrc


          or else edit .inputrc manually with a text-editor to add set bell-style none on it's own line.



          You'll need to restart your currently open bash shell before it takes affect.



          This will only work for your current user, and won't help if you ssh into other accounts (unless you run that command again for each account).






          share|improve this answer





















          • 1





            What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

            – Jim
            Sep 5 '16 at 21:02











          • The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

            – AvatarKava
            Feb 19 '17 at 7:01











          • For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

            – Pro Q
            Jun 18 '18 at 18:58





















          12














          Add this to ~/.inputrc



          set bell-style none


          Additionally for vi, add this to ~/.vimrc



          set visualbell
          set t_vb=





          share|improve this answer
























          • It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

            – frank
            Nov 7 '18 at 19:23











          • @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

            – Nemo
            Nov 8 '18 at 15:07



















          6














          Another way is to open the Volume Mixer by right clicking on the volume control in the Windows taskbar and mute the Console.






          share|improve this answer


























          • Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

            – choover
            Aug 16 '16 at 10:36



















          1














          If you would like to just change the sound to something less annoying instead of disabling it completely, you can go to Change system sounds from Start Menu (or under Control Panel -> Hardware and Sound -> Sound) and change the Critical Stop sound to something like "Windows Default" or "Windows Ding".



          Note that this will affect any other Windows program, or Windows itself, which uses the same sound effect. I'm not able to find a good list of which actions/notifications use that sound by default.






          share|improve this answer
























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "3"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1108120%2fhow-to-disable-bash-on-windows-notification-sound-effect%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            4 Answers
            4






            active

            oldest

            votes








            4 Answers
            4






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            42














            The answer given by Wouter works better overall once set up, but it can be slightly confusing to get working as the correct option doesn't always appear. Follow these steps:




            • Right click the volume control in the Windows taskbar

            • Open the Volume Mixer

            • Open the Bash on Windows console

            • Do something to trigger the console making the notification sound (e.g. press backspace on an empty line). If you've disabled the notification using the alternative method below, you'll have to undo it.

            • Now a Console Window Host option should have appeared in the Volume Mixer (you might have to scroll right)

            • Mute its sound setting


            Volume mixer with Console Window Hos



            Previous/alternative method



            You can simply run the following command from within your Windows Bash shell [source]:



            echo "set bell-style none" >> ~/.inputrc


            or else edit .inputrc manually with a text-editor to add set bell-style none on it's own line.



            You'll need to restart your currently open bash shell before it takes affect.



            This will only work for your current user, and won't help if you ssh into other accounts (unless you run that command again for each account).






            share|improve this answer





















            • 1





              What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

              – Jim
              Sep 5 '16 at 21:02











            • The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

              – AvatarKava
              Feb 19 '17 at 7:01











            • For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

              – Pro Q
              Jun 18 '18 at 18:58


















            42














            The answer given by Wouter works better overall once set up, but it can be slightly confusing to get working as the correct option doesn't always appear. Follow these steps:




            • Right click the volume control in the Windows taskbar

            • Open the Volume Mixer

            • Open the Bash on Windows console

            • Do something to trigger the console making the notification sound (e.g. press backspace on an empty line). If you've disabled the notification using the alternative method below, you'll have to undo it.

            • Now a Console Window Host option should have appeared in the Volume Mixer (you might have to scroll right)

            • Mute its sound setting


            Volume mixer with Console Window Hos



            Previous/alternative method



            You can simply run the following command from within your Windows Bash shell [source]:



            echo "set bell-style none" >> ~/.inputrc


            or else edit .inputrc manually with a text-editor to add set bell-style none on it's own line.



            You'll need to restart your currently open bash shell before it takes affect.



            This will only work for your current user, and won't help if you ssh into other accounts (unless you run that command again for each account).






            share|improve this answer





















            • 1





              What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

              – Jim
              Sep 5 '16 at 21:02











            • The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

              – AvatarKava
              Feb 19 '17 at 7:01











            • For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

              – Pro Q
              Jun 18 '18 at 18:58
















            42












            42








            42







            The answer given by Wouter works better overall once set up, but it can be slightly confusing to get working as the correct option doesn't always appear. Follow these steps:




            • Right click the volume control in the Windows taskbar

            • Open the Volume Mixer

            • Open the Bash on Windows console

            • Do something to trigger the console making the notification sound (e.g. press backspace on an empty line). If you've disabled the notification using the alternative method below, you'll have to undo it.

            • Now a Console Window Host option should have appeared in the Volume Mixer (you might have to scroll right)

            • Mute its sound setting


            Volume mixer with Console Window Hos



            Previous/alternative method



            You can simply run the following command from within your Windows Bash shell [source]:



            echo "set bell-style none" >> ~/.inputrc


            or else edit .inputrc manually with a text-editor to add set bell-style none on it's own line.



            You'll need to restart your currently open bash shell before it takes affect.



            This will only work for your current user, and won't help if you ssh into other accounts (unless you run that command again for each account).






            share|improve this answer















            The answer given by Wouter works better overall once set up, but it can be slightly confusing to get working as the correct option doesn't always appear. Follow these steps:




            • Right click the volume control in the Windows taskbar

            • Open the Volume Mixer

            • Open the Bash on Windows console

            • Do something to trigger the console making the notification sound (e.g. press backspace on an empty line). If you've disabled the notification using the alternative method below, you'll have to undo it.

            • Now a Console Window Host option should have appeared in the Volume Mixer (you might have to scroll right)

            • Mute its sound setting


            Volume mixer with Console Window Hos



            Previous/alternative method



            You can simply run the following command from within your Windows Bash shell [source]:



            echo "set bell-style none" >> ~/.inputrc


            or else edit .inputrc manually with a text-editor to add set bell-style none on it's own line.



            You'll need to restart your currently open bash shell before it takes affect.



            This will only work for your current user, and won't help if you ssh into other accounts (unless you run that command again for each account).







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Mar 20 '17 at 10:17









            Community

            1




            1










            answered Aug 3 '16 at 6:49









            SilveriSilveri

            1,17131018




            1,17131018








            • 1





              What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

              – Jim
              Sep 5 '16 at 21:02











            • The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

              – AvatarKava
              Feb 19 '17 at 7:01











            • For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

              – Pro Q
              Jun 18 '18 at 18:58
















            • 1





              What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

              – Jim
              Sep 5 '16 at 21:02











            • The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

              – AvatarKava
              Feb 19 '17 at 7:01











            • For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

              – Pro Q
              Jun 18 '18 at 18:58










            1




            1





            What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

            – Jim
            Sep 5 '16 at 21:02





            What's the difference between putting set bell-style none in inputrc vs putting bind "set bell-style none" in .bashrc? Is one preferable to the other?

            – Jim
            Sep 5 '16 at 21:02













            The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

            – AvatarKava
            Feb 19 '17 at 7:01





            The latter is preferable as it's a user-configured override file and won't be subject to overwrite due to updates on the distribution version.

            – AvatarKava
            Feb 19 '17 at 7:01













            For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

            – Pro Q
            Jun 18 '18 at 18:58







            For some reason, when I type Python and I'm in the Python shell, the beep still goes off. Is there any way to fix this setting for the Python interpreter as well?

            – Pro Q
            Jun 18 '18 at 18:58















            12














            Add this to ~/.inputrc



            set bell-style none


            Additionally for vi, add this to ~/.vimrc



            set visualbell
            set t_vb=





            share|improve this answer
























            • It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

              – frank
              Nov 7 '18 at 19:23











            • @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

              – Nemo
              Nov 8 '18 at 15:07
















            12














            Add this to ~/.inputrc



            set bell-style none


            Additionally for vi, add this to ~/.vimrc



            set visualbell
            set t_vb=





            share|improve this answer
























            • It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

              – frank
              Nov 7 '18 at 19:23











            • @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

              – Nemo
              Nov 8 '18 at 15:07














            12












            12








            12







            Add this to ~/.inputrc



            set bell-style none


            Additionally for vi, add this to ~/.vimrc



            set visualbell
            set t_vb=





            share|improve this answer













            Add this to ~/.inputrc



            set bell-style none


            Additionally for vi, add this to ~/.vimrc



            set visualbell
            set t_vb=






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered May 23 '17 at 2:47









            NemoNemo

            71167




            71167













            • It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

              – frank
              Nov 7 '18 at 19:23











            • @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

              – Nemo
              Nov 8 '18 at 15:07



















            • It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

              – frank
              Nov 7 '18 at 19:23











            • @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

              – Nemo
              Nov 8 '18 at 15:07

















            It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

            – frank
            Nov 7 '18 at 19:23





            It only work for the server were you are, if you need to connect to multiple server, you'll have to do the same on every server...

            – frank
            Nov 7 '18 at 19:23













            @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

            – Nemo
            Nov 8 '18 at 15:07





            @frank .inputrc and .vimrc are user specific, not specific to a host. Are you logging in as different user?

            – Nemo
            Nov 8 '18 at 15:07











            6














            Another way is to open the Volume Mixer by right clicking on the volume control in the Windows taskbar and mute the Console.






            share|improve this answer


























            • Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

              – choover
              Aug 16 '16 at 10:36
















            6














            Another way is to open the Volume Mixer by right clicking on the volume control in the Windows taskbar and mute the Console.






            share|improve this answer


























            • Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

              – choover
              Aug 16 '16 at 10:36














            6












            6








            6







            Another way is to open the Volume Mixer by right clicking on the volume control in the Windows taskbar and mute the Console.






            share|improve this answer















            Another way is to open the Volume Mixer by right clicking on the volume control in the Windows taskbar and mute the Console.







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited Nov 2 '16 at 7:36

























            answered Aug 3 '16 at 8:46









            WouterWouter

            259126




            259126













            • Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

              – choover
              Aug 16 '16 at 10:36



















            • Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

              – choover
              Aug 16 '16 at 10:36

















            Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

            – choover
            Aug 16 '16 at 10:36





            Thank you! This was way more effective for me than the top answer. Even if you edit the local .inputrc, you'll still get beeps when you ssh into remote hosts (unless you put in the effort to propagate your .inputrc everywhere).

            – choover
            Aug 16 '16 at 10:36











            1














            If you would like to just change the sound to something less annoying instead of disabling it completely, you can go to Change system sounds from Start Menu (or under Control Panel -> Hardware and Sound -> Sound) and change the Critical Stop sound to something like "Windows Default" or "Windows Ding".



            Note that this will affect any other Windows program, or Windows itself, which uses the same sound effect. I'm not able to find a good list of which actions/notifications use that sound by default.






            share|improve this answer




























              1














              If you would like to just change the sound to something less annoying instead of disabling it completely, you can go to Change system sounds from Start Menu (or under Control Panel -> Hardware and Sound -> Sound) and change the Critical Stop sound to something like "Windows Default" or "Windows Ding".



              Note that this will affect any other Windows program, or Windows itself, which uses the same sound effect. I'm not able to find a good list of which actions/notifications use that sound by default.






              share|improve this answer


























                1












                1








                1







                If you would like to just change the sound to something less annoying instead of disabling it completely, you can go to Change system sounds from Start Menu (or under Control Panel -> Hardware and Sound -> Sound) and change the Critical Stop sound to something like "Windows Default" or "Windows Ding".



                Note that this will affect any other Windows program, or Windows itself, which uses the same sound effect. I'm not able to find a good list of which actions/notifications use that sound by default.






                share|improve this answer













                If you would like to just change the sound to something less annoying instead of disabling it completely, you can go to Change system sounds from Start Menu (or under Control Panel -> Hardware and Sound -> Sound) and change the Critical Stop sound to something like "Windows Default" or "Windows Ding".



                Note that this will affect any other Windows program, or Windows itself, which uses the same sound effect. I'm not able to find a good list of which actions/notifications use that sound by default.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Oct 24 '18 at 21:24









                Toby JToby J

                920816




                920816






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Super User!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1108120%2fhow-to-disable-bash-on-windows-notification-sound-effect%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How do I know what Microsoft account the skydrive app is syncing to?

                    When does type information flow backwards in C++?

                    Grease: Live!