Blog Post

Windows IT Pro Blog
1 MIN READ

Re: WMI command line (WMIC) utility deprecation: Next steps

D370000's avatar
D370000
Brass Contributor
Feb 07, 2025

Would prefer the W11 broken GUI enforcers to be "deprecated" instead of the WMIC.
It is sooo much pain to re-write and re-debug 10+ years of code instead of building new useful code. From where comes this trend of destruction?

Updated Feb 07, 2025
Version 3.0

3 Comments

  • RickkeeC1925's avatar
    RickkeeC1925
    Copper Contributor

    I got out of programming because FoxBase was retired.  Hey, everybody is using ACCESS 1.0 now.  Meh, it was a piece of junk, so upgrade to Access 2.0 and rewrite your code....No wait, were planning to change everything to C-Sharp...no wait...now we are changing everything to c++ no wait..now we are changing everything to asp.net and we are never looking back.  Never say never, asp.net is DEAD, now we are moving EVERYTHING to UWC...Too late, it only lasted a year.  Go back to school and learn VB.Net, but hurry before it too is depreciated and replaced by something else, totally incompatible with your existing code.

  • Karl-WE's avatar
    Karl-WE
    MVP

    You can still use PowerShell and CIM instead of WMI. Not too much changes. 

    • D370000's avatar
      D370000
      Brass Contributor

      Thanks to Microsoft deprecators I still need to rewrite some 10+ years of scripts and you can add to it "netsh".
      It is like an attempt to glue together a broken tempered glass window.

      Microsoft has resources. People on the receiving end have only one life. 
      It is a profoundly unfair "competition".