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.