Magoo identified the source of the problem – the conversion of WMIC unicode output to ANSI is flawed in that each line ends with CRCRLF instead of the normal CRLF. FOR /F breaks at (and strips) each LF, leaving CRCR. FOR /F strips the last character from each line if and only if it happens … Read more
Your problem is SYSTEMINFO produces ANSII output (as do most commands), but WMIC produces Unicode output. The two do not mix well. Below are three solutions that all produce ANSII output. 1) Pipe the WMIC output to MORE MORE converts Unicode to ANSII. I also pipe that result to FINDSTR to eliminate blank lines. The … Read more
I just came over this topic. I’ve been using findstr /v to exclude empty lines: FOR /f “usebackq skip=1 tokens=1 delims=:” %%a in (`WMIC logicaldisk WHERE “drivetype=3” GET deviceid ^| findstr /v /r “^$”`) do (
It’s a bug in the wmic command. It’s been suggested to copy XSL files into the %WINDIR%\system32 (or equivalent if 64 bit.) However, the command below works just as well without the need to copy files: wmic process get ProcessId,Description,CommandLine,ExecutablePath,ParentProcessId /format:”%WINDIR%\System32\wbem\en-us\csv” Of course, the “en-us” will be different for different locales. If you want to … Read more
Wow, it was really hard to find out what is going on here. First, I could not believe what happens on batch file execution. I executed on Windows XP SP3 x86 after many trials the command line wmic.exe baseboard get /format:list > Output.txt and looked on file Output.txt with viewer of file manager Total Commander. … Read more