Autologger mode (collects logs across reboots) not starting the log collection
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- operating-systems, tooling
Research direction
Start by reproducing the wpr.exe -boottrace and -addboot commands using BluetoothStack.wprp, then restart and run wpr.exe -boottrace -stopboot BthTracing.etl. Compare the reported command results with the 'There are no trace profiles running' error; done means identifying why boot tracing does not persist across reboot and documenting a verified collection path.
Written by the indexing model from the issue text.
Description
wget https://github.com/Microsoft/busiotools/raw/master/bluetooth/tracing/BluetoothStack.wprp -UseBasicParsing -outfile .\BluetoothStack.wprp
wpr.exe -boottrace -addboot BluetoothStack.wprp!BluetoothStack -filemode
shutdown -r -f -t 0
The above commands are not starting the log collection even after multiple tries too.
As per the Document, i restarted the platform two times manually, even it doesn't help to collect logs.
PS C:\windows\system32> wpr.exe -boottrace -stopboot BthTracing.etl
There are no trace profiles running.
Error code: 0xc5583000
In the below image it shows the commands ran successfully.
OS version details
- Dominant language
- C#
- Stars
- 223
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/busiotools
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
microsoft/busiotools#182 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/busiotools#171 ·
-
Improve Readme file Open
Difficulty 1/5 Under an hour Newbie friendliness 35/100
microsoft/busiotools#168 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/busiotools#153 ·
-
DTD is prohibited Open
Difficulty 4/5 3-5 days Newbie friendliness 20/100
microsoft/busiotools#152 · 1 comment ·
All issues in microsoft/busiotools
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·