Launch administrative tools from the CMD command line. Methods for installing drivers by users without administrative rights Why installing a network printer requires administrator rights

On July 29, 2015, a free upgrade to Windows 10 was launched, and many have already taken advantage of this opportunity, because Windows 10 promised increased performance, new features, and most importantly, the most painless transition. However, the update did not go smoothly for all users. For example, an unpleasant surprise could be the blocking of the old printer driver when the new one has simply not yet been released. User Account Control (UAC) can now not only ask for your permission to install, but also proactively block an application or publisher, prompting you to contact your computer administrator. If the administrator of your personal PC is you yourself, and you have no one to turn to, then this article is for you. We offer several possible solutions to the problem so that you can find the method that works in your case.

If the program cannot be launched by double-clicking the file, the easiest way is to try opening it with administrator rights.

Disabling UAC

Intrusive User Account Control can be disabled. In some cases, this may help launch the problematic program. To most fully limit the functionality of User Account Control, we recommend that you use the Registry Editor.

Command line

You can try to issue the installation command from the command line.

Running the program from the built-in administrator account

This method also helped us; it can be used instead of disabling UAC if the previous simple manipulations did not help.

We discussed enabling the built-in administrator account in the corresponding article (LINK) earlier. Choose a convenient method and activate the administrator profile.
Log in with an administrator account.
Just run the desired installation file. Thanks to the exceptionally broad rights of this account, User Account Control will not interfere with your actions. The installation will most likely be successful.
Log out. Log in with your account. Disable the administrator account using our article (LINK). Never use the built-in administrator account for everyday work - this puts your computer at risk. In addition, it is impossible to launch Metro applications in this mode.

Removing a file signature

In fact, User Account Control blocks installation files that have an invalid or expired electronic signature. To solve the signature problem, a damaged file signature can be deleted altogether. However, this cannot be done using built-in Windows tools, and the process of using additional software (for example, FileUnsigner) is beyond the scope of this article. In general, the process is quite simple:

Download software to remove a file signature.
at the desired exe file.
Run the installation file. User Account Control will not block the installation.

Good afternoon, dear readers and blog subscribers, today we will talk to you about how to open msc windows snap-in via the command line, why you might need it and how it will help in the daily practice of a system administrator. Trust the knowledge gained in this article, in the future they will be able to save you a huge amount of time and nerve cells, not to mention the opportunity to show off your nerdy knowledge in front of your colleagues, just if you actively use Linux systems and know the basic commands in the console, then you will be interested in these. Always, if possible, try to study in addition to GUI interfaces, as well as alternative configuration methods, since when setting up Windows Server, they are increasingly choosing the core mode with a minimalist interface.

What is msc snap-in

And so msc in Windows stands for Microsoft System Console; even simpler, these are windows, or as they are also called snap-ins, for managing certain functions of the operating system. Previously, I already introduced you to the method of creating a convenient mmc snap-in, in which we added everything that a system administrator needs for everyday administration.

And you’ll probably ask, what does the command line and all that have to do with it, but here’s what it has to do with it. Let's imagine a situation, you have an Active Directory domain in your organization, ordinary users do not have local administrator rights on their workstations, everything goes and works like clockwork, a situation happens that, for example, you need to change some settings for a user, and you need to do it now , so there is no time to look for these settings in Group Policy. What to do, logging in is not an option, since you need to make changes in another user profile, and how to open, for example, the Computer Management or System snap-in.

This is where knowing the names of msc windows snap-ins and the command line will help us. All you need to do is open the command line as an administrator and enter the desired name of the msc snap-in. Below is the list. As you can see, by opening the command line cmd.exe, for example, I entered the value that opens the control panel with system administrator rights.

MSC Management Console equipment elements

appwiz.cpl- Installing and removing programs
certmgr.msc- Certificates
ciadv.msc- Indexing service
cliconfg- SQL Network Client Program
clipbrd- Clipboard
compmgmt.msc- Computer management
dcomcnfg- DCOM component management console
ddeshare- DDE Shares (does not work on Win7)
desk.cpl- Screen properties
devmgmt.msc- Device Manager
dfrg.msc- Disk defragmentation
diskmgmt.msc- Disk management
drwtsn32- Dr.Watson
dxdiag- DirectX Diagnostic Service
eudcedit- Personal symbol editor
eventvwr.msc- Event Viewer
firewall.cpl- Windows firewall settings
gpedit.msc- Group Policy
fsmgmt.msc - Shared folders
fsquirt- Bluetooth File Transfer Wizard
chkdsk- Disk check (usually launched with parameters drive_letter: /f /x /r)
control printers- Printers and faxes - does not always start
control admintools- Computer administration - does not always start
control scheduled tasks- Scheduled tasks (scheduler)
control userpasswords2 - Account Management
compmgmt.msc- Computer management ( compmgmt.msc /computer=pc- remote control of PC computer)
lusrmgr.msc- Local users and groups
mmc- creating your own equipment
mrt.exe- Malware removal
msconfig- System setup (autostart, services)
mstsc- Remote Desktop Connection
ncpa.cpl- Network connections

ntmsmgr.msc- Removable memory
mmsys.cpl- Sound
ntmsoprq.msc- Removable RAM operator requests (for XP)
odbccp32.cpl- Data Source Administrator
perfmon.msc- Productivity
regedit- Registry editor
rsop.msc- Resulting policy
secpol.msc- Local Security Settings (Local Security Policy)
services.msc- Services
sfc /scannow- System file recovery
sigverif- File signature verification
sndvol- volume control
sysdm.cpl- System properties
syskey - Account database protection
taskmgr- Task Manager
utilman Utility Manager
verifier Driver Verification Manager
wmimgmt.msc- WMI management infrastructure

List of msc snap-ins for Windows Server

Let's look at how to launch Windows Administrative Snap-ins from the command line cmd.exe

domain.msc - Active Directory domains and trust
dsa.msc - Active Directory Users and Computers
tsadmin.msc - Terminal Services Manager
gpmc.msc - GPO Management Console (Group Policy Management Console)
gpedit.msc - Group Policy Object Editor
tscc.msc - Setting up a terminal server (TS Configuration)
rrasmgmt.msc - Routing and Remote Access
dssite.msc - Active Directory Sites and Trusts
dompol.msc - Domain Security Settings
dсpol.msc - Domain controller security policy (DC Security Settings)
dfsgui.msc - DFS (Distributed File System)
dnsmgmt.msc - DNS
iscsicpl.exe - ISCSI Initiator
odbcad32.exe - ODBC 32-bit data source administrator
odbcad64.exe - ODBC 64-bit data source administrator
powershell.exe -noexit -command import-module ActiveDirectory - Powershell Active Directory module
dfrgui.exe - Disk optimization
taskschd.msc /s - Task Scheduler
dsac.exe - Active Directory Administrative Center
printmanagement.msc - Print Management
vmw.exe - Volume Activation Tool
eventvwr.msc /s - Event Viewer
adsiedit.msc - ADSIedit Editor
wbadmin.msc - Windows Server data archiving system
ServerManager.exe - Server Manager

As you can see, msc windows snap-ins are very useful system administration tools. I even find it faster to open some snap-ins than to click on a bunch of windows with the mouse, especially if the server or computer is slow or there is no mouse. And in any case, it is always useful to know such things. Most of everything we use is stored in c:\Windows\System32. If you go to this folder you can find a lot of interesting things.

nbtstat -a pc- username of the user working on the remote PC machine
net localgroup group user /add- Add user to the group group
net localgroupgroup user/delete- Remove user from group
net send pc ""text"" - send a message to a PC user
net sessions- list of users
net session /delete- closes all network sessions
net use l: \\computer name\folder\- connect network drive l: folder on the remote computer
net user name /active:no- block the user
net user name /active:yes- unblock the user
net user name /domain- information about the domain user
net user Name /add- add user
net user Name /delete- delete user
netstat -a- list of all connections to the computer
reg add- Add a parameter to the registry
reg compare- Compare parts of the registry.
reg copy- Copies from one partition to another
reg delete- Removes the specified parameter or section
reg export- Export part of the registry
reg import- Accordingly, import part of the registry
reg load- Loads the selected part of the registry
reg query- Displays the values of a given registry branch
reg restore- Restores the selected part of the registry from a file
reg save- Saves the selected part of the registry
reg unload- Unloads the selected part of the registry
shutdown- shutting down a computer, you can turn off another one remotely.
SystemInfo /s machine- will show a lot of useful information about the remote machine

List of commands for Windows Control Panel items

control /name Microsoft.AutoPlay - Autoplay
control /name Microsoft.OfflineFiles - Offline files
control /name Microsoft.AdministrativeTools - Administration
control /name Microsoft.BackupAndRestore - Backup and restore
control /name Microsoft.WindowsFirewall - Windows Firewall Windows
control /name Microsoft.Recovery - Recovery
control /name Microsoft.DesktopGadgets - Desktop Gadgets
control /name Microsoft.DateAndTime - Date and Time
control /name Microsoft.DeviceManager - Device Manager
control /name Microsoft.CredentialManager - Credential Manager
control /name Microsoft.HomeGroup - Home group
Windowscontrol /name Microsoft.WindowsDefender - Windows Defender
control /name Microsoft.Sound - Sound
control /name Microsoft.NotificationAreaIcons - Notification area icons
control /name Microsoft.GameControllers - Gaming devices
Keyboardcontrol /name Microsoft.Keyboard - Keyboard
control /name Microsoft.Mouse - Mouse
control /name Microsoft.TaskbarAndStartMenu - Taskbar and Start menu
control - Control panel
control /name Microsoft.Fonts - “Fonts” folder
control /name Microsoft.IndexingOptions - Indexing options
control /name Microsoft.FolderOptions - Folder options
control /name Microsoft.PenAndTouch - Pen and touch devices
control /name Microsoft.Personalization - Personalization
control /name Microsoft.RemoteAppAndDesktopConnections - Remote desktop connections
control /name Microsoft.GetPrograms - Getting programs
control /name Microsoft.GettingStarted - Getting Started
control /name Microsoft.ProgramsAndFeatures - Programs and Features
сontrol /name Microsoft.DefaultPrograms - Default programs
control /name Microsoft.SpeechRecognition - Speech recognition
control /name Microsoft.ParentalControls - Parental Controls
control /name Microsoft.InternetOptions - Internet Options
control /name Microsoft.TextToSpeech - Speech Properties
control /name Microsoft.System - System
control /name Microsoft.ScannersAndCameras - Scanners and cameras
control /name Microsoft.PerformanceInformationAndTools - Performance counters and tools
control /name Microsoft.PhoneAndModem - Phone and modem
control /name Microsoft.ColorManagement - Color management
control /name Microsoft.Troubleshooting - Troubleshooting
control /name Microsoft.DevicesAndPrinters - Devices and Printers
control /name Microsoft.UserAccounts - User accounts
control /name Microsoft.MobilityCenter - Mobility Center
control /name Microsoft.WindowsUpdate - Update Center
control /name Microsoft.ActionCenter - Action Center
control /name Microsoft.SyncCenter - Synchronization Center
control /name Microsoft.EaseOfAccessCenter - Ease of Access Center
control /name Microsoft.NetworkAndSharingCenter - Network and Sharing Center
control /name Microsoft.BitLockerDriveEncryption - Drive encryption
control /name Microsoft.Display - Screen
control /name Microsoft.PowerOptions - Power Options
control /name Microsoft.RegionAndLanguage - Language and regional standards

If you have anything to add to the list of msc canonical names, please write in the comments and I will add them.

Let's find out how an ordinary user can install drivers if he does not have administrative rights. We will not consider options for hacking the admin account. Let's look at more cultural methods.

What are drivers?

These are programs that run at the system kernel level. That is, they have full access to the computer, or rather to any device. Naturally, the right to install such programs cannot be trusted to the first person you meet. That is why only computer administrators can install drivers. But running around every time to establish a connection for a web camera or phone is also not the case - the administrator has enough worries of his own. Let's try to solve this dilemma.

Methods for installing drivers by users without administrative rights

Below we will outline several methods through which users without administrative rights will be able to install drivers.

Adding a driver to the driver store

Let's remember what is installed automatically! This is because the drivers for such devices are already stored in And this means that the driver data has already been verified and that their installation will not entail undesirable consequences. Therefore, when installing a PnP device, the driver files are copied from the storage to the system location. But in reality, we see that we have picked up the required driver automatically and the device is ready to work. Everyone has enough rights to do this. That is, the user can install the printer if the driver store contains the required driver.

This theory should be enough to suggest the option of installing a device driver for the average user. You need to add the necessary drivers to the driver store on your computer! In order to place the desired driver in the driver repository, you must run the following on the command line:

Pnputil -a c:\newdrives\mydrive.inf

Naturally, the path and name of the inf file will be what you need.

But the device will be installed using a simple user account only if it is available. Even if you added an unsigned driver to the repository, you will need administrative rights to initialize it. To solve such problems, you can create certificates for these drivers. But they will only act within the organization. Creating certificates is a matter for server machines, so we will not consider this for now.

Specify folders with allowed drivers

If you open Registry Editor(Execute and enter regedit) and follow the path hkey_local_machine\software\microsoft\windows\current version, You will find the option there Device Path, in which the default value is %SystemRoot%\inf. This parameter specifies the location where the driver is searched for the newly connected device. You can add any other paths to search for the driver using a comma. Well, of course, if you have the drivers somewhere on your computer, although a more serious step would be to specify a network folder with the drivers. Using this method, you will add several more places from which PnP technology can pull out drivers, which means that ordinary users will be able to install drivers for the device.

Give access to install some drivers

The final option is to allow users for specified device classes. The point is to allow users to install drivers for their phones, cameras, web cameras and other various small peripherals. But at the same time, do not give them access to work with kernel or video card drivers, because inept actions with drivers, for example, video cards, can lead to serious problems. What needs to be done for this?

Open device Manager, expand the class of the desired device, select any device and open it Properties. Go to the tab Intelligence and select an item from the list Device class GUID A. In the field Values appear GUID, right click on GUID And Copy. After which, in the menu Execute dialing gpedit.msc and click OK. Will open Local Group Policy Editor. Here we select sequentially: “Local Computer” Policy -> Computer Configuration -> Administrative Templates -> System -> Driver Installation and open the parameter Allow non-administrator users to install drivers for these device installation classes. First of all, we activate this function: switch to Turn on. Then, below we find the button Show and in the field Meaning paste the GUID code we copied. And in the same way we allow the installation of all classes of devices that you consider necessary. For all changes to be made to the system, you must restart the computer, or. After this, users without administrative rights will be able to install drivers for unselected hardware classes.

The last, third installation option is the most effective. Typically, such permissions will be issued for setting up phones, cameras and other small nonsense, which basically automatically grab the necessary drivers. And the main thing here is not to interfere with this. And at the same time block access to installing more important drivers.

This is how you can give users rights and save yourself the extra work.

Good afternoon, readers. Today, once again, I had to go searching for the necessary information. Often you have to help Windows users directly from the user account, and there are no tools at hand other than the cmd.exe command line built into Windows.

When working under a restricted account, you often have to perform some task with elevated Administrator rights. cmd is the most suitable tool for these tasks, so as not to enter the administrator password many times, it is enough to launch the command line once as an administrator and perform the necessary actions, run the necessary commands, which I will describe below:

appwiz.cpl- Installing and removing programs
certmgr.msc- Certificates
ciadv.msc- Indexing service
cliconfg- SQL Network Client Program
clipbrd- Clipboard
compmgmt.msc- Computer management
dcomcnfg- DCOM component management console
ddeshare- DDE Shares (does not work on Win7)
desk.cpl- Screen properties
devmgmt.msc- Device Manager
dfrg.msc- Disk defragmentation
diskmgmt.msc- Disk management
drwtsn32- Dr.Watson
dxdiag- DirectX Diagnostic Service
eudcedit- Personal symbol editor
eventvwr.msc- Event Viewer
firewall.cpl- Windows firewall settings
gpedit.msc- Group Policy
iexpress- IExpress (I don’t know what it is)
fsmgmt.msc- Shared folders
fsquirt- Bluetooth File Transfer Wizard
chkdsk- Check disks (usually launched with drive_letter parameters: /f /x /r)
control printers- Printers and faxes - does not always start
control admintools- Computer administration - does not always start
control scheduled tasks- Scheduled tasks (scheduler)
control userpasswords2- Account management
compmgmt.msc- Computer management (compmgmt.msc /computer=pc - remote control of pc computer)
lusrmgr.msc- Local users and groups
mmc- creating your own equipment
mrt.exe- Malware removal
msconfig- System setup (autostart, services, etc...)
mstsc- Remote Desktop Connection
ncpa.cpl- Network connections
ntmsmgr.msc- Removable memory
ntmsoprq.msc- Removable RAM operator requests (for XP)
odbccp32.cpl- Data Source Administrator
perfmon.msc- Productivity
regedit- Registry editor
rsop.msc- Resulting policy
secpol.msc- Local Security Settings (Local Security Policy)
services.msc- Services
sfc /scannow- System file recovery
sigverif- File signature verification
sndvol- volume control
sysdm.cpl- System properties
sysedit- System file editor (I don’t know what it is)
syskey- Protection of database accounts
taskmgr- Task Manager
utilman - Utility Manager
verifier- Driver Verification Manager
wmimgmt.msc- WMI management infrastructure

This list is mainly GUI applications. Below I will highlight console commands in a separate list.

You can also run applications in the Control Panel with administrator rights by right-clicking while holding down the Shift key. And select Run as (RunAs...) (relevant for Win XP).

List of console commands:

nbtstat -a pc- username of the user working on the remote PC machine
net localgroup group user /add- Add user to the group group
net localgroup group user /delete- Remove user from group
net send pc » text »- send a message to a PC user
net sessions- list of users
net session /delete- closes all network sessions
net use l: \\computer name\folder\- connect network drive l: folder on the remote computer
net user name /active:no- block the user
net user name /active:yes- unblock the user
net user name /domain- information about the domain user
net user Name /add- add user
net user Name /delete- delete user
netstat -a- list of all connections to the computer
reg add- Add a parameter to the registry
reg compare- Compare parts of the registry.
reg copy- Copies from one partition to another
reg delete- Removes the specified parameter or section
reg export- Export part of the registry
reg import- Accordingly, import part of the registry
reg load- Loads the selected part of the registry
reg query- Displays the values of a given registry branch
reg restore- Restores the selected part of the registry from a file
reg save- Saves the selected part of the registry
reg unload- Unloads the selected part of the registry
shutdown- shutting down a computer, you can turn off another one remotely.
SystemInfo /s machine- will show a lot of useful information about the remote machine