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

    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
    • And with SO much better perf than the laggy mess that is Files.
    • 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
  • 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.
      67
  • Tell a friend

    Love Neowin? Tell a friend!