As the title says. How can I open up a new elevated tab in the new windows terminal without having to open an entire new window? I had a look at this question. However it only talks about opening up a new elevated window in a comfortable way.
You cannot currently open an elevated tab in a non-elevated Terminal instance as this could expose the user/processes to various integrity level vulnerabilities.
However, you CAN launch a separate elevated Terminal instance just as you would any other Windows app - right clicking the Icon in your taskbar or start menu, and then right clicking the "Windows Terminal" entry in the pop-up context menu:
Alternatively, hold CTRL + SHIFT while clicking the Terminal icon in your taskbar or start menu.
⚠️ Note: It is highly recommended that you only run an elevated application long enough to complete a given task that requires elevation, and then close that application and continue running a non-elevated instance. This will help ensure that you do not unnecessarily expose yourself, your data, and your systems to potential violation.
Related
I'm trying to create a shortcut (.lnk) file that will launch scrcpy without showing the console window, but I need to be able to pin it to the taskbar and have the window and shortcut merge. Scrcpy is bundled with a vbs script that launches scrcpy through wscript, hiding the console, but when I made a shortcut opening that through wscript that made a duplicate window (icon?). I also found a somewhat promising question here about Pinning advertised shortcuts on the taskbar, which led me to an MS Docs page about AppUserModelIds, the only problem being I don't really understand how they work, or how to make a shortcut with them.
I've currently connected two monitors via a dock to my notebook.
When I'm running my console application, the console window always pops up on the first monitor. How can I change that it's automatically opened on another monitor, e.g. on monitor 3? Maybe there is a property I need to modify?
It's very annoying to always drag the console window onto the monitor on which my IDE is opened.
Console applications (unlike GUI applications) don't create their own window; that's done by Windows, and in the case when you're running in an already created console, then you kinda inherit, e.g., cmd's window.
What you can do, though, is to find your window and move it to a different monitor.
Another option is to change the window manager settings for that application in the properties of the console window under Layout. Especially the check box »Let system position window«. To do so, first move the window where you'd like it to appear, then open the properties, go to the Layout tab, and just click »OK«.
So I've been working on my personal Steam account swapper with pre-game choice options but, I've been running into a few problems. The program works fine but I'm getting this problem where when I chose which profile I want logon to (for smurfing purposes) the Steam window pops up in my face and it prevents me from being able to choose which game I want to play. So I was wondering if there's a way to close the Steam window (and only the window) as soon as it pops up. taskkilling it won't work because if you taskkill it right away it will close the login (login starts when I choose which account I want to play on)
TL;DR I want to close steam window as soon as it pops up
NOTE: When logging in, task manager reads the steam logon window as SteamLogin and not Steam Not sure if this would make the lightbulb go off.
In steam there is an option to suppress the login prompt on system boot, I am not 100% if this will work with your loginswitcher, but is worth a try.
Go to "start menu", "run", type "regedit".
In the registry editor, expand the tree until you find this HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
In "Run", you will find all applications that are starting with Windows. Edit the value for "Steam" and add the silent option (-silent).
Reboot and try your login switcher.
Here is the scenario:
In the Wix install script for our application , start menu shortcuts and desktop shortcuts are now handled differently than before.
These changes causes any user pinned shortcut to the application on the taskbar to be orphaned when a user runs an update from a previous installation. In other words, the shortcut remains but is no longer pointing to anything.
The shortcut is shown as a blank page indicating that the link has been removed. A quick peek at the C:\Users[UserName]\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar folder confirms this. Clicking on the shortcut will remove it and then show a windows dialog asking whether to remove the shortcut or not (answer has no meaning since it has already been removed).
My question is:
Is there any way to tell the taskbar to remove orphaned shortcuts ?
Preferrably this would be triggered by a custom action in the Wix script after installing the new version.
The roaming profile can move from machine to machine so it's pretty much impossible. About all you could do is leave behind a component that runs on logon and detects that your app is no longer installed and deletes the shortcuts.
I'd consider this user data and let the user worry about it.
How can I force the window that opens when I run a website from Visual Studio to be maximized? Everytime I run my site VS automatically resizes the window to something that seems arbitrary.
After your browser window has been opened once (as not maximized) press the maximize button. Then HOLD ctrl key and press the close button ('X'). Then you may release the ctrl key.
Next time your window will be open as maximized (holding ctrl key while pressing close forces windows to remember the window's last state)
Go into the project settings - Web - Start Action, and set it to be "External program" with start.exe and command line arguments of
/MAX http://localhost:12345/myproject/default.aspx (or whatever)
This will open default.aspx in a maximized window, but only if you don't have any other IE windows open - if you do (and you have IE7) - you'll just get a tab in one of those windows instead.
This will probably keep your debugger from attaching to the iexplore process and may indeed return immediately because start.exe only runs for a second. You may have to manually attach to the iexplore.exe process.
But it doesn't involve a bunch of window-manipulating JavaScript.