0ca5b57ba3
The command doesn't work as intended. Explanation for the fix: 1. Windows requires the GUID inside quotes because it's treated as a string (the provider name) in this context. Without quotes, the command parser may interpret the braces or hyphens incorrectly. 2. Passing 0x0 as the only flag after the provider GUID is valid. Supplying two numbers like 0 0 (as in some bad examples) misleads logman, which tries to interpret the second value as outputFormat. 3. The -o trace.etl must be at the end and not mistaken for a different parameter like -f (output format), unless you're also explicitly setting -f to text or xml.
Docs @ Docker
Welcome to the Docker Documentation repository. This is the source for the Docker Docs Website.
We welcome your contributions—feel free to open pull requests or issues. Our docs are completely open source, and we deeply appreciate contributions from the Docker community!
Provide feedback
We’d love to hear your feedback! To submit feedback:
- Click New issue on the docs repository, or
- Click Request changes in the right column of every page on docs.docker.com, or
- Click Give feedback on every page in the docs.
To get community support, use the Docker Community Slack. Personalized support is available through the Docker Pro, Team, and Business subscriptions. See Docker Pricing for details.
If you have an idea for a new feature or behavior change in a specific aspect of Docker or have found a product bug, file an issue in the project's repository.
Contribute to Docker docs
See CONTRIBUTING.md.
Copyright and license
Copyright 2013-2025 Docker, Inc., released under the Apache 2.0 license.