question

JamesPeppe-3969 avatar image
2 Votes"
JamesPeppe-3969 asked Docs-4663 answered

WMIC stopped working on Windows 10 2004

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
· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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

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 ·
Docs-4663 avatar image
0 Votes"
Docs-4663 answered

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://docs.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

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.