My Goal is to have a kiosk application on Windows that is launched in fullscreen and that user cannot escape. To do that, I replaced explorer.exe by my_fullscreen_app.exe under Configuration\Administrative Templates\System\Custom user interface.
Everything works well, but when user press ctrl+alt+supp and then cancel, the screen becomes black. When I look at the task manager, my_fullscreen_app.exe is processed but not displayed anymore.
How to avoid this problem without disabling ctrl+alt+del ?
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.
Is there a way to temporarily disable the display during a Windows 10 PC restart?
Background: we have a software, which is set to start up automatically after a PC restart. Upon startup (after Windows has booted) this software starts in a console window and then opens a WPF screen, which is displayed fullscreen and always resides in front of everything else. I would like to black out the screen ideally as early as possible during the Windows startup up to the point in time when our software WPF window is set and ready on the screen. This way the console window (as well as the desktop showing for a short period of time) would be hidden from the user.
In an ideal world I would hide the fact that Windows is running on the PC from the user, but I assume this is not possible over a restart...
Is this possible with the help of registry settings/command line tools/batch file commands or similar?
We are looking for a solution to run Windows programs - mainly browsers - on Windows (10) in screen lock mode. Means the browser should be visible and content should be live but nobody should be able to do any click or keyboard input without logging in by Ctrl-Alt-Del or something else.
It shouldn't be the typical kiosk mode because absolutely no interaction should be possible until loggin in. But everybody should see the live (monitoring) content on the screen.
I have an issue where the Windows 8 User Account Control (UAC) popup is minimized when I execute a command line helper program that requests admin privileges in its manifest. The UAC popup window just blinks yellow in the Windows taskbar, causing a confusing user experience:
After clicking the taskbar icon, then the UAC alert shows:
In Windows 7, the UAC alert is not minimized but shows in the foreground. Any thoughts on how to fix this in Windows 8?
For reference, my main application runs under user privilege and executes the helper program with ShellExecuteEx. I am setting ShellExecuteEx's TShellExecuteInfo.nShow to SW_SHOW.
MSDN says ".. you must pass a parent HWND with a ShellExecute .." and explains,
The UAC elevation mechanism uses the HWND as part of determining
whether the elevation is a background or foreground elevation. If the
application is determined to be a background application, the
elevation is placed on the taskbar as a blinking button. ..
Be sure to supply your foreground window's handle to ShellExecuteEx.
Is it possible to force the screensaver to appear whenever a computer becomes locked? Specifically on XP, 7 if possible.
Windows has several desktops. You're familiar with the one you are looking at right now. There's another one for the login screen. And there's one for the screen saver. Locking the workstation switches the desktop to the login screen. You cannot switch back to another desktop (like the screen saver one) until you login.
You can however get the screen saver started, that selects the screen saver desktop. Which automatically switches to the login desktop if you configure the screen saver that way.
I believe that the SS is only triggered when the timeout is reached, regardless if the PC is locked or not.
The other way to think of this is to lock the PC whenever the screensaver fired.
Windows 2000 and above has an option to enable lock the PC when the screensaver is active, just enable this, and set the timeout and you are ready to go.