> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/stifler/3.0/troubleshooting/stifler-client-command-line-options.md). # StifleR client command line options This page covers what command line options can be sent to the StifleR client. The StifleR Client executable accepts various command line arguments which can be used for troubleshooting and configuration. When executing most command lines, the /Service switch should be used. /? - Check the manual for command line options. /Service - Simulates running as a service, should always be used otherwise clients exits. /Locale - Displays OS installed language info /IETW - ETWInstaller.InstallETWManifests /UETW - ETWInstaller.UninstallETWManifest /Set - Sets values in config file as in Key=value format /RemoveFilterDriver - removes the StifleRS.sys filter drivers /ResetPolicy removes the BITS & DO Maintenance Policy /Task - Do not run as a service but as triggered from events, client will exit /jobid: - Command line execution for BITS service, used with /Task /LogEventLevel - 0-5 /Log - specifies which log to display * Bandwidth * BITSBranchCache * DeliveryOptimization * Location * MainLoop * Program * SignalR * TypeDetection /Debug - Waiting for debugger - for development purposes only. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.2pintsoftware.com/stifler/3.0/troubleshooting/stifler-client-command-line-options.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.