To further eleaborate on what everyone else has said, the "correct" way to do this is through GPO. You may want to look at the package "Group Policy Common Scenarios Using GPMC", it is a set of group policy scripts to lock down workstations for various situations. I believe you are looking for the AppStation script.
The GPMC is not used anymore but the scripts are still really good templates for starting points for doing this.
AppStation
The AppStation scenario is used when you require highly restricted
configurations with only a few applications. Use this scenario in
“vertical” applications such as marketing, claims and loan processing,
and customer-service scenarios.
The AppStation scenario has the following characteristics:
- Allows minimal customization by the user.
- Allows
users to access a small number of applications appropriate
to their job role.
- Does not allow users to add or remove applications.
- Supports free-seating.
- Provides a simplified desktop and Start menu.
- Users have
restricted write access to the local computer and
can only write data to their user profile and to redirected folders.
- Is highly secure.
TaskStation
Use the TaskStation scenario when you need the computer dedicated
to running a single application, such as on a manufacturing floor, as
an entry terminal for orders, or in a call center.
The TaskStation scenario is similar to the AppStation scenario,
with the following changes:
- It has only one application installed, which automatically
starts
when the user logs on.
- No desktop or Start menu is present.
Kiosk
Use this scenario in a public area, such as in an airport where
passengers check in and view their flight information. Because the
computer is normally unattended, it needs to be highly secure.
The Kiosk scenario has the following characteristics:
- Is a public workstation.
- Runs only one
application.
- Uses only one user account and automatically
logs on. The system
automatically resets to a default state at the start of each session.
- Runs unattended.
- Is highly secure.
- Is simple to operate, with no logon procedure.
- Does not
allow users to make changes to the default user or system
settings.
- Does not save data to the disk.
- Is always on (the user cannot log off or shut down the computer).
A workstation that uses the Kiosk scenario is similar to a
TaskStation, but users are anonymous in that they all share a single
user account that automatically logs on at computer startup. This is
achieved by modifying the Kiosk machine in a manner described later in
this document. No customizations can be made and no user state is
preserved.
Although user sessions are usually anonymous, the user can log on
to an application-specific account, such as to a Web-based application
through Internet Explorer (assuming Internet Explorer is the
“kiosk application” launched at startup).
The dedicated application could be a Line of Business (LOB)
application, an application hosted in Internet Explorer, or
another application, such as one available in Microsoft Office. The
default application should not be Windows Explorer or any other
shell-like application. Windows Explorer allows more access to
the computer than is appropriate for a Kiosk computer. Be sure the
command prompt is disabled and Windows Explorer cannot be
accessed from any application you use for this purpose.
Applications used for kiosk scenarios should be carefully checked
to ensure they do not contain “back doors” that allow users to
circumvent system policies. For example, they should not allow users
access to applications that access the file system. Ideally, you
should only use applications that comply with “The Application
Specification for Windows 2000”, are Certified for Windows, and
that check for Group Policy settings before giving users access to
prohibited features. Older applications will not normally be Group
Policy-aware, so try to disable any features that allow users to
bypass administrative policy.
The registry entries Run and RunOnce are disabled in
the Kiosk scenario through associated policy settings.
Best Answer
Since you are noticing this behavior in a wide variety of applications, this could be a bug with your specific hardware in Windows 8. Or, more likely, something is corrupted in your OS. You mentioned that you did a clean install on a Dell workstation - did you use a vanilla Microsoft Windows 8.1 or a crappy Dell bundleware version? If it is the latter, then that might be worth trying with a vanilla version. Another avenue to explore is graphics drivers - try out various versions and revisions to see if they make any difference.
Regardless of what the root cause is, there might be an easy workaround. AutoHotkey is a program that allows you to change a window's settings (and lots more). We can use it to set up a hotkey to deactivate a window's "frontmost" property. Then, whenever this bug occurs - bam, you quickly hit the hotkey, the window goes back to normal, and you move on with your life.
Sound good? Let's get started.
1) Download and install AutoHotkey from the official website (linked above).
2) Create a new text file called
AutomateStuff.ahkand put the following text in it:Explanation:
#z::part defines windows + z as a hotkey. (#is the AutoHotkey symbol for the windows modifier.)returnwill be executed when you press the hotkey.WinSetis a command to set a window's property.AlwaysOnTopis the property that makes the window always show.offwill make it so that this property is explicitly removed.Ameans that we will set this property to the activate window.SoundPlayline will just play a sound so that we know the hotkey was successfully pressed. This line is unnecessary; remove it if you don't like the sound.3) Save the file, then double click it. You should see the green AutoHotkey icon appear in the system tray - it looks like an “H”. Now, whenever you press win+Z, it will fix the window.
For more information on AutoHotkey, check out: