Windows 10: Executing "net user" command in cmd or powershell causes the window to close. No idea how...

Discus and support Executing "net user" command in cmd or powershell causes the window to close. No idea how... in Windows 10 Ask Insider to solve the problem; [ATTACH] submitted by /u/Patftw89 [link] [comments]... Discussion in 'Windows 10 Ask Insider' started by /u/Patftw89, Apr 5, 2021.

  1. Executing "net user" command in cmd or powershell causes the window to close. No idea how...

    /u/Patftw89, Apr 5, 2021
    #1

  2. Problem with command "net user"

    Hello,

    If I write "net user" into cmd window or into powershell windows it always close it. Not effect, nothing.

    Any idea what can be wrong?
     
    Tomáš Drábek, Apr 5, 2021
    #2
  3. Dutch2 Win User
    Can not execute/run FCAT-VR in powershell or CMD

    If typing that I did get a message “the server service is not started.”

    So I did enable server in the Windows services and now after typing “net session” recieving the message “There are no entries in the list”
     
    Dutch2, Apr 5, 2021
    #3
  4. Steven L Win User

    Executing "net user" command in cmd or powershell causes the window to close. No idea how...

    Using PowerShell via MMC to execute admin level CMD commands

    I'm new to PowerShell. I want to do something like this on shutdown before turning off the computer. I plan to have Windows MMC/Local Group Policy Editor do it with a PowerShell script.

    Basically, after triggering the shutdown or reboot event it should:

    1. Open CMD as admin (and automatically select Yes at UAC?).
    2. Execute SOME COMMAND (there will be many).
    3. Close CMD and then allow Windows 10 to shutdown/reboot.

    Now, I know how to get MMC to add a PowerShell script to execute before the shutdown command is completed. I just need to know the syntax on how to do the above three steps.

    To be clear though:

    My main point is to be able to open CMD as admin, type in a command and then exit CMD. PowerShell does not normally execute a few particular commands as admin correctly, but CMD does. In that way, PowerShell itself does not need admin privileges, just the temporary run CMD.

    I dont' mind clicking YES on a UAC, when needed, because I figure if it comes down to it, I can probably just used sendkeys {TAB}{TAB}{ENTER} or something. What I can't seem to find on the interwebs is how to start a PowerShell script so that one can save it. I'm seeing a lot on sendkeys in syntax though. In bash in Linux, it's simple: #!/bin/bash and presto insta-bash, but Windows seems bass-ackwards in this regard.

    If there is a better way to do this than, CMD > Echo "stuff" > exit CMD, please let me know. I know what stuff I want to type in each Echo "stuff" (or rather, sendkeys, if I end up using that), I just don't know how to open CMD as admin.

    Thanks.
     
    Steven L, Apr 5, 2021
    #4
Thema:

Executing "net user" command in cmd or powershell causes the window to close. No idea how...

Loading...
  1. Executing "net user" command in cmd or powershell causes the window to close. No idea how... - Similar Threads - Executing net user

  2. CMD and PowerShell Closing after a couple of seconds, CMD and Powershell closing.

    in Windows 10 Gaming
    CMD and PowerShell Closing after a couple of seconds, CMD and Powershell closing.: My Laptop is fine i didnt download any viruses, Didnt mess with system files nor modify it. After a normal restart, A message that pops up for half a second saying "This app wont work on this computer" Or something like that The messages appears and disappears too fast its...
  3. CMD and PowerShell Closing after a couple of seconds, CMD and Powershell closing.

    in Windows 10 Software and Apps
    CMD and PowerShell Closing after a couple of seconds, CMD and Powershell closing.: My Laptop is fine i didnt download any viruses, Didnt mess with system files nor modify it. After a normal restart, A message that pops up for half a second saying "This app wont work on this computer" Or something like that The messages appears and disappears too fast its...
  4. CMD and PowerShell Closing after a couple of seconds, CMD and Powershell closing.

    in Windows 10 Customization
    CMD and PowerShell Closing after a couple of seconds, CMD and Powershell closing.: My Laptop is fine i didnt download any viruses, Didnt mess with system files nor modify it. After a normal restart, A message that pops up for half a second saying "This app wont work on this computer" Or something like that The messages appears and disappears too fast its...
  5. Powershell command "net users"

    in Windows 10 Gaming
    Powershell command "net users": I recently did a powershell search using 'net users'. It brought up all the accounts in my windows 10 computer. it showed 3 accounts: a 'default acct' with a name that I apparently created a long time ago. it also showed a 'guest acct' with another name. it also showed a name...
  6. Powershell command "net users"

    in Windows 10 Software and Apps
    Powershell command "net users": I recently did a powershell search using 'net users'. It brought up all the accounts in my windows 10 computer. it showed 3 accounts: a 'default acct' with a name that I apparently created a long time ago. it also showed a 'guest acct' with another name. it also showed a name...
  7. Powershell command "net users"

    in Windows 10 Customization
    Powershell command "net users": I recently did a powershell search using 'net users'. It brought up all the accounts in my windows 10 computer. it showed 3 accounts: a 'default acct' with a name that I apparently created a long time ago. it also showed a 'guest acct' with another name. it also showed a name...
  8. Most windows executable commands not recognized by CMD and PowerShell.

    in Windows 10 Gaming
    Most windows executable commands not recognized by CMD and PowerShell.: Out of nowhere commands which involve executables like explorer.exe, msedge.exe, mspaint.exe, where, etc. are not working in command prompt or PowerShell. The output of the command prompt seem to be quite simple: ```C:\Users\grass>where 'where' is not recognized as an...
  9. Most windows executable commands not recognized by CMD and PowerShell.

    in Windows 10 Software and Apps
    Most windows executable commands not recognized by CMD and PowerShell.: Out of nowhere commands which involve executables like explorer.exe, msedge.exe, mspaint.exe, where, etc. are not working in command prompt or PowerShell. The output of the command prompt seem to be quite simple: ```C:\Users\grass>where 'where' is not recognized as an...
  10. 10 CMD commands that can be executed with PowerShell

    in Windows 10 News
    10 CMD commands that can be executed with PowerShell: [ATTACH] PowerShell is Microsoft’s own alternative to their own Command Prompt. Earlier, Microsoft announced that they will be open sourcing PowerShell and will be bringing it to recent versions and different Linux flavors like Ubuntu, CentOS, Red Hat Enterprise Linux,...