Elevate myself in a CMD Windows 7 command prompt? ("su" or "sud


Recommended Posts

yes, most have missed something but some have gotten it :p

You can't change the integrity level of a process once it's been started, so you need to launch a new instance of CMD using the "Run as Administrator" option.

Basically this is the best answer to the problem at hand. thank you.

This is the feature I most wish they would add... Nothing more annoying than firing up the command prompt then having to kill it off and do it over...

You can't change the integrity level of a process once it's been started, so you need to launch a new instance of CMD using the "Run as Administrator" option.

It could spawn a new instance of CMD with the elevated permissions (firing up the UAC dialog and the like)...

  • 5 months later...

yes u can go to start all programs accessories find the cmd right click run as admin now..

just remember in windows right click does alot .. and if ur on 8 maybe they changed it but in 7 vista xp right click

Yes, but as Brandon said all that does is just start a new instance...so no it does not elevate the current running CMD Prompt window.

IF microsoft added the feature to elevate to admin CMD from standard, every virus/malware in the world would implement it and take over all machines, defeating the purpose. Think about it. ;) I mean, banking on the fact that most users don't use a limited account from the beginning of their installs...I say MOST, I myself have limited accounts on everything I own excluding my server, that I administrate, and nobody has the password to....just throwing that out there...

IF microsoft added the feature to elevate to admin CMD from standard, every virus/malware in the world would implement it and take over all machines, defeating the purpose. Think about it. ;)

Doubtful since that same malware/virus could just invoke an admin CMD session since it would be prompted for credentials either way (in your scenario). So either way is more or less the same level of secure.

  • Like 1

Been a while since I've been in windows 7 im used to just windows 8 and just right clicking bottom left corner and hitting command prompt admin but I think you can type cmd in the start menus search, right click it and high run as admin

Doubtful since that same malware/virus could just invoke an admin CMD session since it would be prompted for credentials either way (in your scenario). So either way is more or less the same level of secure.

Touche, Shane. Good point. Although, behind my firewalls/security, I've never had that happen, nor do I allow my users to run in an admin space to begin with, and trust me...if you don't know my password, which is over 19 characters long, is nearly impossible to be cracked....I don't allow admin privelages on ANYTHING, except explicitly a very FEW things, most everything my users do is "in the cloud", I've steered them away from local accounts...so meh, never had any problems. It's bad admins that let/allow the bad stuff to get by, which I will not approve unless I'm physically there to see what they are doing. ;) So I am not worried. Microsoft has taught me well, when it comes down to being secure....that and previous experiences....so in other words, "I got this" on my end. Not too worried. (Scanned all my machines personally with various scanners/rootkit revealers/etc...there is no PEBKAC happening here! ;) ) Need I say, Budman, GroupPolicy...etc...self explanitory. I'm not saying it couldn't happen to someone else, it's just never happened to ME, on my domain/network. Not going to either. ;)

Touche, Shane. Good point. Although, behind my firewalls/security, I've never had that happen, nor do I allow my users to run in an admin space to begin with, and trust me...if you don't know my password, which is over 19 characters long, is nearly impossible to be cracked....I don't allow admin privelages on ANYTHING, except explicitly a very FEW things, most everything my users do is "in the cloud", I've steered them away from local accounts...so meh, never had any problems. It's bad admins that let/allow the bad stuff to get by, which I will not approve unless I'm physically there to see what they are doing. ;) So I am not worried. Microsoft has taught me well, when it comes down to being secure....that and previous experiences....so in other words, "I got this" on my end. Not too worried. (Scanned all my machines personally with various scanners/rootkit revealers/etc...there is no PEBKAC happening here! ;) ) Need I say, Budman, GroupPolicy...etc...self explanitory. I'm not saying it couldn't happen to someone else, it's just never happened to ME, on my domain/network. Not going to either. ;)

Oh yes I wasn't saying that. I was just saying that either route provides about the same security. I wasn't questioning your practices. :)

@Shane, and BudMan....I appreciate everything microsoft and BudMan has taught me...even though he (budman) might not have been here for me all the way, physically, but I DO take notes. Thank you for the fine, awesome job you do at microsoft, and I'll forever appreciate it. I was just saying, malware/viruses/compromistation has never bitten me in the bootay, and I don't plan on it starting now. I don't say much on neowin, but I do know that what I've learned has kept my systems MORE than secure...need I say, UAC FTW? Keep up the great work, buddy. Keep on educating people....as long as you do, it'll keep people like me and their networks secure. Not saying that anything bad couldn't happen to someone OR me...I'm sure it does, but it helps to be educated in the right prevention steps, by the right people. This is why I love neowin! Different strokes for different folks! Thank you, Shane! You should get more recognition than you do! Hey, Neowin...LISTEN TO THIS GUY! Just saying, it could stop some trouble in the future! (Thank you too, BudMan, for all of your networking skills...everything you say matters to at least someone who is worthy to listen!)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!