WMIC stopped working on Windows 10 2004

James Peppe 11

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?

Keith Blackwell 1 Reputation point

2020-11-10T00:42:37.937+00:00

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
Obaid Farooqi MSFT 591 Reputation points Microsoft Employee

2021-01-04T17:40:55.693+00:00

Hi @James Peppe
I would like to set your expectation about my help in this case. I will look into this issue from a protocols perspective. I'll try to find what is changed in the protocol that is giving you this error.

As far as Windows is concerned, wmic is deprecated.
I don't have this tool that you are talking about. You will have to send me traces that I need for investigation.

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,
Obaid Farooqi - MSFT
mikhail.tsirkov 1 Reputation point

2021-03-12T14:36:39.733+00:00

Is there any information on how to solve this problem?
四點壹木 6 Reputation points

2022-01-25T07:15:19.227+00:00

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 Reputation points

2023-12-14T07:50:54.52+00:00

没看到答案

11 answers

Docs 15,521 Reputation points

2022-01-25T10:02:22.953+00:00

WMIC is used widely however this was posted:

Windows 10 features we're no longer developing

Windows Management Instrumentation Command line (WMIC) tool.

The WMIC tool is deprecated in Windows 10, version 21H1 and the 21H1 semi-annual channel release of Windows Server.

This tool is superseded by Windows PowerShell for WMI.

Note: This deprecation only applies to the command-line management tool. WMI itself is not affected. 21H1

https://learn.microsoft.com/en-us/windows/deployment/planning/windows-10-deprecated-features#:~:text=The%20WMIC%20tool%20is%20deprecated,WMI%20itself%20is%20not%20affected.

Please contact Microsoft using the Feedback Hub:

https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

WMIC stopped working on Windows 10 2004

11 answers

Your answer