The wmic tool can be used for a wide range of purposes and, luckily, also executing commands on remote devices is also among its many powers.

Although it might look like it for some, this is far from being rocket science, and it all comes down to knowing and inputting the right commands.

You will see, as we are about to show you in this article, that running commands on a remote computer using the wmic tool is a piece of cake.

We’re going to guide you through the entire process and share the necessary commands with you, so that you will have it for future reference.

How can I run a command on a remote computer with wmic?

Before we start, it is important to know that, to use this feature, you must have administrative permissions.

Furthermore, if you are also talking about sharing between the remote machines, the file/folder that you want to share must already exist on the target computer.

We are going to use an example of a GPU update command on the target remote computer, to make sure you get the gist of the idea.

Thus, here’s what you need to do in order to successfully complete such a task:

1. Press the Windows key, search for Command Prompt, and select Run as administrator.
2. On the Command Prompt, type wmic, and then press Enter.
3. Input the following command: WMIC /node:ComputerName process call create “cmd.exe /c GPUpdate.exe”

NOTE

As we said, this is only an example, and you can run whatever command you want. Just replace the computer name with the name of the remote device you are trying to access, and the update GPU command with the desired command instead.

And, to be safe keep the " around the computer’s name, as without the quotes, some characters seem to cause issues with this command.

It goes without saying that there is, however, a downside to using this method, because you can’t see the command execute or the results of the process if there was an error or unexpected result.

Don’t let that discourage you though, as many Windows users have been running such commands remotely for years and the problems were few and far apart.

Since we’re talking about wmic, other Windows users have reported dealing with access is denied, and alias not found errors, so we prepared some fixes for you.

Also, be sure to check out the list of commands for accessing all system information on your Windows device, just in case you need it.

If you are trying to use the wmic tool on Windows 11 and the system says it is not recognized, we can help you deal with that situation as well.

Was this article of help to you? Share your experience with us in the comments section below.

Even though many people think that gathering system information is only possible on Linux. However, this can also be done for the Windows OS, using Command Prompt.

There are some commands that need to be used to achieve your purpose and, to execute all these commands, you need to run the Command Prompt as Administrator to get access to the system information.

We’re going to be using wmic commands, in case you were wondering, so stay tuned and see exactly what you have to do.

The Windows Management Instrumentation Command-line (WMIC) is a command-line and scripting interface that simplifies the use of Windows Management Instrumentation (WMI) and systems managed through WMI.

How can I get system information using wmic?

Before we list the commands you need to use in order to have access to that information, you must first open a Command Prompt with Administrator privileges.

Only that way will your system display the requested information, so keep that in mind when trying this.

1. Press the Windows key, search for Command Prompt, and select Run as administrator.
2. Type the desired command and press the Enter key.

After you opened the app with Administrator privileges, it’s time to get the information you need by using one of the following commands, depending on the purpose:

• Gather all information about a CPU, such as name, device ID, number of cores, max clock speed, and status.

wmic cpu

• Send attributes to get the particular details of a CPU in a better view.

wmic cpu get caption, name, deviceid, numberofcores, maxclockspeed, status

• Get the serial number of our BIOS.

wmic bios get serialnumber

• Gather information about the available memory (RAM).

wmic computersystem get totalphysicalmemory

• Get information about all the available partitions on the system.

wmic partition get name,size,type

• Get the list of all processes running on our computer.

wmic process list

• You can terminate these tasks by using the following command.

wmic process where name="name_of_file" call terminate

• This command offers the list of all products/software installed on a computer.

wmic product

wmic product get name,version

• Command that gives details of a particular volume of the disc and the serial number of the volume of that disc.

vol volume_letter:

NOTE

You have to replace volume_letter with the letter of the volume you wish to use.

• Get the exact version of your Windows OS.

winver

• Get a list of all large files and also files that are harmful.

chkdsk

• Use this command to get elaborate system info.

systeminfo

NOTE

This will bring back information about Host Name, OS Name, OS Version, OS Manufacturer, OS Configuration, Os Build Type, Registered Owner, Product ID, Original Install Date, Bios Version, Processor, Input Locale, Time Zone & many more.

• Get details of your hard disk.

diskpart

• Get Mac Address.

wmic nic get macaddress 

getmac

• Get information about user accounts.

wmic USERACCOUNT get Caption,Name,PasswordRequired,Status

• Get information About NICs.

wmic NIC get Description,MACAddress,NetEnabled,Speed

• Get Memory Device DIMM Numbers

wmic MEMORYCHIP get Capacity,DeviceLocator,PartNumber,Tag

These are the commands you can use in Command Prompt in order to access your system information and get the necessary details.

Remember to run the software with Administrator privileges, otherwise, some information will be inaccessible to you.

For more advanced system management, check out the Vssadmin Commands guide that helps you control Volume Shadow Copies from Command Prompt.

Was this article helpful to you? Let us know in the dedicated comments section below.

We’re pretty much all familiar with Wmic, the command-line and scripting interface that simplifies the use of Windows Management Instrumentation (WMI) and systems managed through WMI.

However, remember that Microsoft manufacturers recently reported that they will no longer develop the WMIC command-line feature.

Thus, the functionality will be removed from Windows 10, Windows 11, and Windows Server builds from now on, in case you were wondering.

That being said, you can add the functionality back to your PC as an optional feature or access it through PowerShell.

Many users reported receiving the login to remote object error, which usually pops up when we run the WMI Configuration Wizard.

UNKNOWN – The WMI query had problems. The error text from wmic is: [wmi/wmic.c:196:main()]
ERROR: Login to remote object.
NTSTATUS: NT code 0x800706ba – NT code 0x800706ba

We are going to show you what actions to take when you are faced with this situation so that there won’t be any problems.

How can I fix wmic login to remote object error?

Before we get into how we can solve this problem, we also have to understand its roots. It is possible that the Windows Firewall is not allowing any traffic through, thus the error.

We have to, first of all, make sure that within the Windows Firewall, under Allowed Programs, WMI is actually enabled.

How can I fix the error on Windows Server 2008, 2012, and 2016?

1. Press the Windows key, search for Command Prompt and click on Open.
2. Type wf.msc to opem Windows Firewall with Advanced Security.
3. Click on Inbound rules on the left side panel.
4. Click on Filter by Group on the right side panel.
5. Look for WMI and click on it.
6. Find DCOM-In and WMI-In rules.
7. Right clicking on both of them and select Enable Rule.

However, on the off chance the WMI rule group doesn’t even exist, Microsoft suggests a method that we are about to describe for you right now.

Open a Command Prompt and enter the following command:

netsh advfirewall firewall add rule dir=in name=”DCOM” program=%systemroot
%\system32\svchost.exe service=rpcss action=allow protocol=TCP localport=135

netsh advfirewall firewall add rule dir=in name =”WMI” program=%systemroot
%\system32\svchost.exe service=winmgmt action = allow protocol=TCP localport=any

netsh advfirewall firewall add rule dir=in name =”UnsecApp” program=%systemroot
%\system32\wbem\unsecapp.exe action=allow

netsh advfirewall firewall add rule dir=out name =”WMI_OUT” program=%systemroot
%\system32\svchost.exe service=winmgmt action=allow protocol=TCP localport=any

How can I solve this problem for Windows Server 2003?

1. Press the Windows key + R and type DCOMCnfg.exe, then click OK.
2. Click to expand Component Services, then Computers.
3. Right-clickMy Computer and select Properties.
4. In the Default Protocols tab, double click on Connection-oriented TCP/IP.
5. Press the Add button.
6. Enter a 5000-5020 port range for COM services and press OK.

Now, please allow the port range through the Windows Firewall with the following command, which will open ports from 5000-5020 to match the COM Internet Services Range.

FOR /L %I IN (5000,1,5020) DO netsh firewall add portopening TCP %I “COM”%I

And, finally, open DCOM port 135 and type the following command into Command Prompt:

netsh firewall add portopening TCP 135 “DCOM”

That’s pretty much all you have to do in order to solve your problem. However, this isn’t the only wmic error that’s been giving users sleepless nights.

People have also been reporting wmic access denied, as well as wmic alias not found errors. We can help you with either scenario if you are in need of assistance.

Was this guide helpful to you? let us know in the comments section below.

With Windows 11, Microsoft’s main point of focus was security instead of many other things that your day-to-day user finds essential.

Sure, things are starting to turn around for the new operating system, but there are still many areas where it lacks common functionalities specific to its predecessor.

For example, the new right-click context menu in the Windows 11 File Explorer is a notably different user experience than in Windows 10.

That may be exactly what some users want, but for other users, it is only one of the many reasons why they chose not to upgrade to the latest OS.

However, the full right-click context menu can also be restored for Windows 11 with a few Windows 11 Registry File hacks.

Provided you are ready to begin and have a clear goal, which is restoring the Windows 10 context menu for File Explorer, we can show you how to do it.

How can I restore the classic context menu in File Explorer?

As most of you know by now, right-clicking a file in File Explorer under Windows 11’s new user interface will trigger an abbreviated version of the context menu.

Many users won’t have this and would like to explore other possibilities, such as restoring the Windows 10 version of the File Explorer context menu.

For even more control over how File Explorer behaves in Windows 11, you can follow a dedicated guide to enable access to File Explorer Options and fine tune additional folder and view settings.

Let’s get right into it and reveal the entire process without any further ado. It might take a few minutes of your time, so make sure you aren’t in a hurry.

1. Open the Start menu, search for regedit and open the app.
2. Select HKEY_CURRENT_USER, then click on Software, then Classes.
3. Right-click the CLSID folder and select New, then Key.
4. Name this new key: 86ca1aa0-34aa-4e8b-a509-50c905bae2a2.
5. Right-click the new key you created and select New, then Key.
6. Name this new key: InprocServer32.
7. Double-click the Default settings item in the right-hand window under the new InprocServer32.
8. Press the OK button without typing anything into the Value Data box.
9. Close the Registry Editor and restart your PC.

Of course, you can also revert these changes if you grow bored of them or want to switch back to the Windows 11 style. All you have to do is navigate to the correct folder and delete the new keys you created from the registry file.

And if you find the Print action missing in right-click menu on Windows 11, the steps listed above will surely help!

Speaking of Windows 11, if you need assistance, we can also show you how to manually download drivers, or neat tricks such as how to change the boot logo, or how you can play harmless error pranks on your friends.

Was this guide helpful to you? Let us know in the comments section below.