Problem
I dont like it, when the windows taskbar is flashing orange, for example Microsoft Teams if there is a new notification. It disturbs my workflow and breaks my concentration.
Steps done
I tried to remove the orange flashing with the following:
Windows + R -> Regedit
Go to Directory Computer\HKEY_CURRENT_USER\Control Panel\Desktop
Change ForegroundFlashCount and ForegroundLockTimeout to value 0
Restart Computer
Wished Behavior
It would be best if the symbol did not blink at all, but it would also be nice if it only blinked once when there was a new notification.
If I remember correctly, 0 is invalid and Windows will ignore it, so just use 1. And don't zero the foreground lock, or any program would steal your window focus, thus indeed break your workflow.
Related
I'm running a Windows 10 system with one touch screen, one normal screen and no mouse or keyboard. I need to run an application with administrator privileges.
I'm worried about which screen the Account Control popup will appear on - if it appears on the non-touch screen then users will have no way to allow the program to run.
I know that:
It runs on screen 2 on my development PC (with mouse and keyboard, no touch screen), regardless of whether screen 2 is on the left or right
It runs on the same screen regardless of whether the application was launched by a shortcut on the left or right screen.
I tried to google this, but the only things that came back were links on how to disable User Account Control, which we really don't want to do.
What is the logic that determines which screen the popup appears on?
[Edit for new things I have tried]
Unplugging screen 2, running the application, closing the application, plug screen 2 back in.
Dragging the UAC popup to screen 1, clicking details, changing UAC settings and returning them to the original state.
[SOLVED]
I figured it out (at least partially) but I can't mark it as answered for at least two days.
Basically, after unplugging and replugging screens the other way around, changing the primary display worked. This didn't work until after I did the plug/unplug, but there's no guarantee that was the thing that did it, since I'd tried a few other things.
So after physically unplugging and replugging monitors so that screen one became screen 2 and the reverse, switching which screen was the primary display works to control the popup now.
Changing the primary display didn't work before. But it does now. I have no idea why - there's no guarantee that it was to do with switching them around.
I would suspect it to pop up by default on the primary display, but remember its last position. This would appear to be confirmed by TechNet: UAC Prompt displays on 2nd monitor only RRS feed:
escknx:
Regardless of what I try, UAC prompts display only on 2nd monitor, while everything else works fine on primary monitor.
Stereoman:
drag the UAC Prompt to your Primary Monitor and click show more details on the prompt then click change when these notifications appear, another UAC window will open up with a vertical bar with 4 different settings, just drag the bar setting down and then back up to it's original setting position then click ok, this will re trigger UAC's screen position to your primary monitor.
So: upon deployment, make sure the touch screen is your primary display, and position the UAC popup there if it isn't.
i have been trying to get a windows startup/shutdown sound to play, i couldn't get the sounds to play so i asked on Microsoft, here is the link https://answers.microsoft.com/en-us/windows/forum/all/cannot-change-windows-start-up-sound/8bbcb0a0-1402-4f1e-b080-9c8d526bc205
and i was told that its not possible. well too bad because i am not going to stop there, so i went to local group policy editor on windows 10 where you can choose scripts to run during shutdown and start up. i then wrote a very small PowerShell command with the file name of "shutdown.ps1" the code inside of shutdown.ps1 is
start "C:\Windows\System32\GroupPolicy\Machine\Scripts\Shutdown\TADA.wav"
this file is located in the C:\Windows\System32\GroupPolicy\Machine\Scripts\Shutdown directory along with the TADA.wav file that it plays when it shuts down.
now the issue i am having is that when windows is shutting down, its ending all processes so it does not play the sound. what can i do to change that?
I'm pretty new to all of this and am very grateful for any input you can give.
thanks in advance,
Devin
From How to Change the Windows 10 Logoff, Logon, and Shutdown Sounds in Windows 10:
...
While you can still customize what sounds sounds play for most OS events, Windows 10 hid shut down, logoff, and logon from view. They’re still around, though. You just need to make a few mild changes in the Windows Registry to get them back.
Add the Actions Back to the Sound Control Panel by Editing the Registry
To add the shutdown, logoff, and logon actions back to the menu in the Sound Control Panel app, you just need to make a few little tweaks in the Windows Registry.
...
Open the Registry Editor by hitting Start and typing “regedit.” Press Enter to open Registry Editor and then give it permission to make changes to your PC.
In the Registry Editor, use the left sidebar to navigate to the following key:
HKEY_CURRENT_USER\AppEvents\EventLabels
You’re going to be making one small change in each of three different subkeys inside that EventLabels key. First, we’ll tackle the shutdown sound or, as Windows likes to call it, System Exit. Under the EventLabels key on the left side of Registry Editor, select the SystemExit subkey. On the right side, double-click the ExcludeFromCPL value.
Note that by default, the value is 1, meaning that the action is excluded from the Control Panel. Change the value to 0 and then click “OK.”
Next, you’re going to make exactly the same change in two other subkeys inside the EventLabels key: WindowsLogoff and WindowsLogon. Head into each of those folders, open the ExcludeFromCPL value inside, and change the value from 1 to 0.
No need to restart Windows. You can go ahead and test your changes right away. Open up the Sound Control Panel app by right-clicking the speaker icon in your Notification Area and selecting “Sounds.” 1
You should now see the new actions (Exit Windows, Windows Logoff, and Windows Logon) available in the selection window and you can assign whatever sounds you like to those actions.
If, for whatever reason, you want to hide those actions from the Control Panel again, just head back into Registry Editor and change each of those ExcludeFromCPL values back to 1.
1: On my machine, to get to the Sounds control panel, I had to go into the Settings, choose "Personalization", then "Themes", then `Sounds".
UPDATE:
And indeed, all three sound events show up in my Sounds control panel once I re-enable them in the Registry. However, I tried assigning audio files to them, and although Windows remembered the assignments, nothing played when invoking those actions.
So, I guess the playback functionality is simply not implemented for those events anymore. This seems to be confirmed in your discussion with a Microsoft Insider on answers.microsoft.com (with an 89% upvote rate of 143K replies, I would think he knows what he's talking about):
In Windows 10 there is no way to change the Windows Startup Sound, that sound is set permanently in a DLL in Windows, it is not an audio file like the other system sounds, and even when you turn on the Startup sound on that dialog, sometimes the startup sound will play and other times it will not, this is a known bug in Windows 10, which seems to have been fixed in Windows 11
Windows10 does not support a shutdown sound like previous versions of Windows, you wil find many methods posted online, sadly, none of them work.
Sometimes when dragging a window around on the Windows 7 desktop, all of my other open windows will suddenly minimize. I can go to the task bar and reopen them, one by one, but is there a way to get them all back at once? And is there a way to turn off this annoying behaviour?
Thanks.
That will be Aero Shake.
You can shake the window that you were moving and your windows will be restored.
You can also disable Aero Shake, following instructions here:
Go to Run (Windows+R) and type gpedit.msc
Navigate to User configuration > Administratives Templates > Desktop
Search for "Turn off Aero Shake window minimizing mouse gesture" and enable the policy.
If you shake a window (left-right rapidly or another direction) then it minimizes all windows except that one. To get them back, shake the first window again.
This is what worked for me.
Open Windows Explorer.
Maximize and close it with Shift pressed.
Windows Explorer should open maximized.
By now everyone writing for Windows probably knows that applications cannot (officially) steal focus from foreground processes, and why. But I have just managed to steal focus, inadvertently, and don't understand how this is even possible.
I have a Delphi app that user brings up with a hotkey (or by a mouse click, or by Alt+Tab), selects a piece of text and hits Enter. My app then minimizes (hides to the tray, even), and pastes the text user just selected into the active window. Nothing new here, plenty of similar projects out there - clipboard extenders, glossaries, macro programs, etc.
What is puzzling to me is that after doing all the above and then sleeping for 1500 ms, I restore my main form and it gets the focus back! It becomes the foreground window, even though it wasn't 1500 ms ago (tested; Windows 7 32-bit.).
In fact, I don't want this at all, so before restoring my main form I record which window has foreground and I give it back to that window after it's been given to me. I'm just curious why my app gets to be in the foreground when by rules it should not. Maybe I don't understand the rules as fully as I thought I did?
If you look at the documentation for SetForegroundWindow you see a list of conditions for the call to succeed, one of them is "The process received the last input event." So if the user does not do anything after pressing enter in your app you still have the right to steal focus. I don't know if Delphi calls SetForegroundWindow for you when the window is restored but it might be something to look into.
I don't know how you restore your window but using SW_SHOWNOACTIVATE with ShowWindow might help...
My manager thinks he's seen other people "lock" the windows on screen keyboard to the bottom of their applications, effectively docking it with their window, and wants me to reproduce this. They're using vb6 and occasionally vb.net.
I've done a good amount of googling on the subject and I'm resorting to looking into the windows SDK at the minute, but if someone out there can save me a few days of pain by either confirming that it's not possible or pointing me in the right direction if it is I'd appreciate it.
I find that the keyboard locks if I open it from the taskbar icon. It will stay on the bottom of the screen then, even if I'm not on a text field.
No idea how to achieve that programmatically though