We use a package in our corporate environment which imports your wmic module to execute the wmic command. However in our environment normal users (i.e. non admins) do not have access to the command prompt - it's disabled by policy. This breaks the wmic module as you use child_process.spawn to start wmic.exe in a full shell (cmd /c) rather than using child_process.execfile which would run the exe directly. Is this intentional due to the amount of output data the wmic command can generate? Or does the wmic.exe process require a full cmd shell in order to work properly?