Powershell ISE Doesn't Render the Client Area in Windows 7 - powershell

Recently, the Powershell ISE on my Windows 7 laptop developed a problem in which only the title bar and frame would render to the screen. The entire client area (including menus) doesn't appear. Instead, whatever is behind the client area shows through. If I move the ISE around on the screen I get a client area with a jumble of pieces of the desktop or other apps that I drag the ISE over, as well as some ISE frame pieces.
I can blindly click in the area where I think the menu should be, and can occasionally get something to appear (a Save As... dialog, or some such), but the menus themselves are never drawn.
This started sometime during a period in which I didn't use the ISE, so I've no idea how many updates may have been automatically downloaded or pushed to my machine by my IT folks, and since I've no idea when it started happening they can't tell me anything either.
Any ideas on why a Windows 7 app in general or the ISE in particular could have this issue?

Could be video card drivers. Try disabling windows areo to see if it's 3D driver related:
net stop uxsms
Also try running ISE as administrator.

On my system it's an interaction with MaxiVista (www.maxivista.com) which allows me to use an old laptop as a second monitor.
When the second (Maxivista) monitor is enabled, the Powershell ISE does not draw properly. So #BryanVine is right. It's to do with video drivers.

Related

How to remove Window 11 Start Menus bloatwares via Powershell?

In the new Windows 11 Start Menus, there are apps like "TikTok" and "Prime Videos" that are not actually installed on the system, they would start installing when you clicked on the icon. This means that usual way of uninstalling via Powershell (ie: Remove-AppxPackages) does not work. In Window 10, I would get a round this by just replacing the orginal Start Menus layout config file with a blank one (effectively remove all pinned apps), then manually repin all the apps I wanted; but, this does not works on Win11 either.
So... does anyone know how to remove all of this visual bloats on the Start Menus via PowerShell (or any other command-line tools/languages, for that matter)?

Gnome shell two monitors full screen apps

I'm working on the Ubuntu 16.04 whit Gnome Shell version 3.18.5 and I'm using two monitors. Issue which I have regarding aplications opend in the full screen mode.
For expample if I open on the monitor number 1 my browser and on the monitor number 2 terminal in full screen mode plus some additional application such as a code editor(not full screen). Now when I'm focus on the code editor which is on the top of the terminal it's ok but when I click on my broser window(monitor 1) then the code editor gose behind the terminal automatically.
I've prepared some video to better show this problem:
In this video you can see correct behaviour when I'm using one monitor.
Here is video showing incorrect behaviour. Don't care about the elements which are above the terminal on the left screen. Terminal was set to full screen.
Dose anybody know how to change this behaviour? I was looking for solution in google but without success. Thank you.
That's the expected behavior when things are in focus/out of focus. Try resizing your windows so they don't block one another; thus, nothing will be "behind" anything else when you shift focus by clicking here or there.

Active Desktop Recovery

This one's new to me.
I downloaded and installed the VB.Net version 3.5 updates, and got some complaints about my printer drivers, which I ignored. My system auto-rebooted without asking, and then came up with am "Active Desktop Recovery" background screen (everything still works normally). So when I tried to "restore my active desktop" ( a button on the background screen) it claims a script error.
Okay, fine, I wasn't using the active desktop anyhow, so I decided to turn it off. Go to the Display Properties window, and WTF! The Desktop tab is gone!
Anybody know the fix for this, or even a workaround??
Sounds like malware, perhaps trying to hide whatever changes it made to your desktop and prevent you from undoing them. Give your favourite anti-malware a go.
Afterwards, to restore the tab and fix the recover button thingie there's a few MSKBs: 929200 and 929200.
Set the decimal value to 0 under the value DeskHtmlVersion in key HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Desktop\SafeMode\Components.

Is it possible to save a window layout in Windows XP?

When I am working with files on my project I normally have four windows open viewing four different folders in the four quadrants of the screen. My morning ritual involves having to manually open these four folders, takes only a few moments but I was hoping to find a way to automate this with Windows XP?
Any ideas?
You can write a batch file with these commands:
start c:\myfolder1
start c:\myfolder2
start c:\myfolder3
start c:\myfolder4
or, since Bart said in the comments on this answer, he uses this method:
explorer c:\myfolder1 (etc...)
and then run that any way you wish (on Start up, via a shortcut...)
As for saving their position on the screen, I don't know much about that, but you could try using Winsplit Revolution. That will let you use hotkeys to reposition windows (Ctrl+Alt+Numpad 7 moves a window to the top left).

What determines the monitor my app runs on?

I am using Windows, and I have two monitors.
Some applications will always start on my primary monitor, no matter where they were when I closed them.
Others will always start on the secondary monitor, no matter where they were when I closed them.
Is there a registry setting buried somewhere, which I can manipulate to control which monitor applications launch into by default?
#rp: I have Ultramon, and I agree that it is indispensable, to the point that Microsoft should buy it and incorporate it into their OS. But as you said, it doesn't let you control the default monitor a program launches into.
Here's what I've found. If you want an app to open on your secondary monitor by default do the following:
1. Open the application.
2. Re-size the window so that it is not maximized or minimized.
3. Move the window to the monitor you want it to open on by default.
4. Close the application. Do not re-size prior to closing.
5. Open the application.
It should open on the monitor you just moved it to and closed it on.
6. Maximize the window.
The application will now open on this monitor by default. If you want to change it to another monitor, just follow steps 1-6 again.
Correctly written Windows apps that want to save their location from run to run will save the results of GetWindowPlacement() before shutting down, then use SetWindowPlacement() on startup to restore their position.
Frequently, apps will store the results of GetWindowPlacement() in the registry as a REG_BINARY for easy use.
The WINDOWPLACEMENTroute has many advantages over other methods:
Handles the case where the screen resolution changed since the last run: SetWindowPlacement() will automatically ensure that the window is not entirely offscreen
Saves the state (minimized/maximized) but also saves the restored (normal) size and position
Handles desktop metrics correctly, compensating for the taskbar position, etc. (i.e. uses "workspace coordinates" instead of "screen coordinates" -- techniques that rely on saving screen coordinates may suffer from the "walking windows" problem where a window will always appear a little lower each time if the user has a toolbar at the top of the screen).
Finally, programs that handle window restoration properly will take into account the nCmdShow parameter passed in from the shell. This parameter is set in the shortcut that launches the application (Normal, Minimized, Maximize):
if(nCmdShow != SW_SHOWNORMAL)
placement.showCmd = nCmdShow; //allow shortcut to override
For non-Win32 applications, it's important to be sure that the method you're using to save/restore window position eventually uses the same underlying call, otherwise (like Java Swing's setBounds()/getBounds() problem) you'll end up writing a lot of extra code to re-implement functionality that's already there in the WINDOWPLACEMENT functions.
It's not exactly the answer to this question but I dealt with this problem with the Shift + Win + [left,right] arrow keys shortcut. You can move the currently active window to another monitor with it.
Get UltraMon. Quickly.
http://realtimesoft.com/ultramon/
It doesn't let you specify what monitor an app starts on, but it lets you move an app to the another monitor, and keep its aspect ratio intact, with one mouse click. It is a very handy utility.
Most programs will start where you last left them. So if you have two monitors at work, but only one at home, it's possible to start you laptop at home and not see the apps running on the other monitor (which now isn't there). UltrMon also lets you move those orphan apps back to the main screen quickly and easily.
I'm fairly sure the primary monitor is the default. If the app was coded decently, when it's closed, it'll remember where it was last at and will reopen there, but -- as you've noticed -- it isn't a default behavior.
EDIT: The way I usually do it is to have the location stored in the app's settings. On load, if there is no value for them, it defaults to the center of the screen. On closing of the form, it records its position. That way, whenever it opens, it's where it was last. I don't know of a simple way to tell it to launch onto the second monitor the first time automatically, however.
-- Kevin Fairchild
Important note: If you remember the position of your application and shutdown and then start up again at that position, keep in mind that the user's monitor configuration may have changed while your application was closed.
Laptop users, for example, frequently change their display configuration. When docked there may be a 2nd monitor that disappears when undocked. If the user closes an application that was running on the 2nd monitor and the re-opens the application when the monitor is disconnected, restoring the window to the previous coordinates will leave it completely off-screen.
To figure out how big the display really is, check out GetSystemMetrics.
So I had this issue with Adobe Reader 9.0. Somehow the program forgot to open on my right monitor and was consistently opening on my left monitor. Most programs allow you to drag it over, maximize the screen, and then close it out and it will remember. Well, with Adobe, I had to drag it over and then close it before maximizing it, in order for Windows to remember which screen to open it in next time. Once you set it to the correct monitor, then you can maximize it. I think this is stupid, since almost all windows programs remember it automatically without try to rig a way for XP to remember.
So I agree there are some apps that you can configured to open on one screen by maximizing or right clicking and moving/sizing screen, then close and reopen. However, there are others that will only open on the main screen.
What I've done to resolve: set the monitor you prefer stubborn apps to open on, as monitor 1 and the your other monitor as 2, then change your monitor 2 to be the primary - so your desktop settings and start bar remain. Hope this helps.
Do not hold me to this but I am pretty sure it depends on the application it self. I know many always open on the main monitor, some will reopen to the same monitor they were previously run in, and some you can set. I know for example I have shortcuts to open command windows to particular directories, and each has an option in their properties to the location to open the window in. While Outlook just remembers and opens in the last screen it was open in. Then other apps open in what ever window the current focus is in.
So I am not sure there is a way to tell every program where to open. Hope that helps some.
I've noticed that if I put a shortcut on my desktop on one screen the launched application may appear on that screen (if that app doesn't reposition itself).
This also applies to running things from Windows Explorer - if Explorer is on one screen the launched application will pick that monitor to use.
Again - I think this is when the launching application specifies the default (windows managed) position. Most applications seem to override this default behavior in some way.
A simple window created like so will do this:
hWnd = CreateWindow(windowClass, windowTitle, WS_VISIBLE | WS_OVERLAPPEDWINDOW, CW_USEDEFAULT, SW_SHOW, CW_USEDEFAULT, 0, NULL, NULL, hInst, NULL);
Right click the shortcut and select properties.
Make sure you are on the "Shortcut" Tab.
Select the RUN drop down box and change it to Maximized.
This may assist in launching the program in full screen on the primary monitor.