Wmic executable file not found in PATH
Show Skip to main content
question
I use WMIC to pull logs from remote machines internally. After we upgraded a few machines to Windows 10 2004 it stopped working for those machines and we now getting the following error: [wmi/wmic.c:196:main()] ERROR: Login to remote object. NTSTATUS: NT code 0x80010111 - NT code 0x80010111 This indicates that Windows has changed something either in Samba or RPC to prevents WMIC from work. I know that WMIC is not an official Microsoft Product but wanted to know if Microsoft has published anything work arounds for this issue or if they have made any statements confirming changes to samba, RPC, or have acknowledged that WMIC no longer will work with there products? windows-10-generalopenspecs-windows Different problem, admittedly, but in case someone else runs into it, I came here because of a different type of brokenness: WinPE with powershell (and WMI) was working fine in previous version, but in one built with the v2004 ADK the /format:csv option obliterates output from wmic command. For something like "wmic computersystem get Manufacturer", without the /format option, or with /format:list, I get correct output. But if I use /format:csv, then suddenly I get no output at all. No error, either. Baffling defective behavior! I don't have a root cause or fix, and my only work-around is to revert to an older version of WinPE that works fine. Another difference was that it starts up in a high-dpi setting such that the command prompt takes up the entire screen, whereas all older versions did not do that at all. These pesky little failures are what makes image deployment solutions so time-consuming 0 Votes 0 · Hi @JamesPeppe-3969 As far as Windows is concerned, wmic is deprecated. Please send an email to my attention to dochelp at microsoft dot com and I'll reply with the instructions on what and how to send me traces. Regards, 0 Votes 0 · Is there any information on how to solve this problem? 0 Votes 0 · Hello, I also use wmic 1.3.14, which is used for Linux machines. The same problem as yours has occurred. Has your problem been solved? Is there any solution? 0 Votes 0 ·
Do you see any logon errors in the security eventlog on the target machine? Did you try re-running "winrm quickconfig" on the target machine? Did you configure the firewall to log dropped packets for Domain/Private/Public? Any entries in the log? Open a Powershell prompt on the source machine using an account that has admin access to the target machine. Do both of these commands fail with the same error? Use your machine name. I don't quite understand your last comments. Wmic.exe has been part of Windows for a long time and while MS may no longer be enhancing it, I would expect it to still work. If you are using some other WMIC, then you should be more specific about your environment and the commands/functions being executed. Thank you for the help. While WMIC.exe was built by Microsoft, I was referring to WMIC for linux machines. I see that the user is able to authenticate from the remote linux machine, but there are no errors in the eventlogs. Running WMIC.exe on the host machine works without any issues it seems to be an issue when running WMIC from a remote linux machine. As far as settings everything was working prior to the Windows 10 2004 upgrade. 0 Votes 0 · Where did you get this Linux version of WMIC? Who supports it? 0 Votes 0 · We have been using this for 3 years now and version is actually: Version 4.0.0 Not exactly sure where we first obtained it, as it looks like I am unable to find any packages online. I know that another big company (not going to name names) pointed us in this direction as
well as they use it in there software. 0 Votes 0 ·
I am not using WMIplus, I am just using WMIC 1.3.14. I have also seen those posts and they don't seem to have a solution either. Thank you though. 0 Votes 0 ·
MotoX80 answered Nov 2, '20 MotoX80 commented Nov 4, '20
Then your best bet is to get this other big company to fix it if their software depends on it working. From a Microsoft point of view, you're using a 3rd party program of unknown origin and if it doesn't work, that not a MS problem. If you can recreate the error from Windows to Windows, then you can open a case with Microsoft and get them to fix it. But you will need to be using supported Windows versions on both the client and the server. (If you recreate the error with XP or Server 2003, you're out of luck.) If this WMIC is open source, then you might be able to fix it yourself. A search of the net indicates that 0x80010111 is an RPC header issue. On the "2004" machine
trace the same WMI call from a Windows machine and the Linux machine using WireShark or Network Monitor 3.4. Then compare the traffic and see if you can find where the error occurs. Compare the good vs bad data packets and see if you can find where in the code that packet is built and modify the code to get it to work. Understood, however it worked prior to the update and still works on machines that are not upgraded so to me it points that Microsoft changed something on their end. My original post was asking if Microsoft made any statements of changes they made with Samba or RPC. I have seen many issue users have brought up on SAMBA issues as well with this latest upgrade..... 0 Votes 0 ·
Hi James Did the patch fix your problem? If not you can add tag openspecs-windows to your original post, one of the Microsoft Open Specifications Support will be glad to assist you.
Hi Hung, The patch did not fix the issue. HI James Thank you for the update, one of Microsoft Open Specifications Support will be contacting you shortly. 0 Votes 0 · Did anyone figure out what caused this issue? 3 Votes 3 · Is there any information on how to solve this problem? 0 Votes 0 ·
We have investigated the problem with the WMIC tool. An issue has been identified with the 2004 release of Windows 10 that impacts DCOM versions 5.1 through 5.6. The issue is being addressed for a future Windows release. The tool is using DCOM 5.1, which is considerably aged. DCOM 5.4 was used by Windows 95 & 98, DCOM 5.6 was used by Windows 2000, but Windows has used DCOM 5.7 since Windows XP. Updating the tool to use DCOM 5.7 or a more modern transport such as HTTP would resolve the issue. Otherwise, it should work once the issue above has been fixed. Best Regards,
Hello Jeff, do you have an ETA for the future Windows release that will address the WMIC issue?
We do not have an ETA yet.
Any update on a fix for this issue?
This fix will be in a future release of Windows. There is no ETA on when this will be released. If there is a more immediate business need, a request can be made by submitting a support case through: Microsoft Support for Business Please reference this thread if you submit a request. Best Regards,
question detailsRelated QuestionsHow do I add WMIC to path?Open Control Panel > System > Advanced System settings. ... . Click Environment variables button and select the System Variables section.. Edit Path variable and add C:\Windows\System32\wbem\ to the beginning of the path followed by semicolon ( ";" ) character. ... . Save the change made to PATH environment variable.. Why is WMIC not recognized?The error states that the WMIC is not recognized as an internal or external command. Windows displays this error message when it does not find the WMIC in the system path. To solve this problem, you have to define a System Variable by adding the path of the WMIC executable file.
How do I install WMIC on Windows?Please follow the steps below to download and properly replace you file:. Locate your Windows operating system version in the list of below "Download WMIC.exe Files".. Click the appropriate "Download Now" button and download your Windows file version.. Copy the file into the appropriate directory for your Windows version:. What is WMIC exe?The Windows Management Instrumentation Command line (WMIC) is a software utility that allows users to performs Windows Management Instrumentation (WMI) operations with a command prompt.
|
