CLI runas admin

Code:

net localgroup administrators

Members
-----------------------------
Administrator
user

Code:

runas /user:Administrator "chkdsk c:"

<enter user, which should be administrator, pass>
user name or password is incorrect

Code:

runas /user:user "chkdsk c:"

<enter user pass>
attempting to start chkdsk c: as user ...

Fails to run.

What am I missing here? Is there a way to give Administrator member its own password. It appears as though my user pass doesn't work even though it's supposedly admin. To be clear, I'm not asking how to right click. How do I elevate to admin privilege and run a program through cli?

Not sure what your question is.

Do you mean you want to set Administrator password?

Code:

net user administrator Password /active:yes

or you want to elevate privileges, for example

Code:

:checkPrivileges 
NET FILE 1>NUL 2>NUL
if '%errorlevel%' == '0' ( goto gotPrivileges 
) else ( powershell "saps -filepath %0 -verb runas" >nul 2>&1)
exit /b

windows - How can I auto-elevate my batch file, so that it requests from UAC administrator rights if required? - Stack Overflow

Over complicating things, just run the Command Processor as Administrator.

Right Click Run as Administrator.

Code:

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is System.

WARNING!  /F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
                                                                                                                                                                  327936 file records processed.                                                
File verification completed.
                                                                                                                                                                  3606 large file records processed.
                                                                                                                                                                  0 bad file records processed.

Stage 2: Examining file name linkage ...
                                                                                                                                                                  397314 index entries processed.                                               
Index verification completed.
                                                                                                                                                                  0 unindexed files scanned.
                                                                                                                                                                  0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
                                                                                                                                                                  34690 data files processed.
CHKDSK is verifying Usn Journal...
                                                                                                                                                                  36069072 USN bytes processed.                                                 
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 233058303 KB total disk space.
  47762496 KB in 141521 files.
     95840 KB in 34691 indexes.
         0 KB in bad sectors.
    555091 KB in use by the system.
     65536 KB occupied by the log file.
 184644876 KB available on disk.

      4096 bytes in each allocation unit.
  58264575 total allocation units on disk.
  46161219 allocation units available on disk.

C:\WINDOWS\system32>

clam1952 said:

Over complicating things, Right Click Run as Administrator.

They did say in the first post:

jnich said:

To be clear, I'm not asking how to right click.

Perhaps you missed it.

Seems to be a pointless over complication just to run chkdsk......

Maybe it doesn't work as the Computer name isn't specified? runas /user:computer name\account name chkdsk C:

Thank you lx07! I needed to set a password for Administrator member reboot and runas /user:Administrator to get it working. I'm sorry for the confusion. chkdsk was just an example.

OK I'm now unconfused, glad you got it sorted. :)

jnich said:

I needed to set a password for Administrator....

Yes, runas requires the account you want to 'run as' to have a password - else you get...

Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed...

By default the built-in Administrator account has a blank password and is disabled. Setting a password for Administrator has a downside, it is the account used when booting to the repair environment and your emergency way in when all else fails. Forget that password and your only repair option may be a clean install.

It would be better to leave Administrator alone, for your purposes I would create another local account (say, Admin) make that an administrator and give it a password. Then you can runas Admin rather than the built-in Administrator.

Bree said:

It would be better to leave Administrator alone, for your purposes I would create another local account (say, Admin) make that an administrator and give it a password. Then you can runas Admin rather than the built-in Administrator.

This is where my troubles began. According to Windows, my user was the Administrator so running as that user and providing its password should have worked. I tried several times, just to be sure there wasn't a typo when entering my password. Assigning a password to Administrator and rebooting did the job. I'm not worried about forgetting a password in this environment, but I'll keep that in mind.