We were trying to run logman against a host yesterday and it was showing wierd results. On running "which logman" we found out that it was referring to /C/Winnt/System32/logman, changing the path order resolved the problem.
This command has been renamed to bllogman.exe in the 6.3
release which has just come out.
We also still provide it as logman.exe (in case anyone
has scripts out there that reference logman.exe)
but moving forward, people should probably start using
The primary reason for this change was the issue you mentioned.