microsoft / microsoft/audio

i-can-make-it-happen-glitch.cmd errors out if windows directory path containing space

Open Beginner friendly
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PowerShell
Stars
29
Forks
11
PR merge metrics
No merged PRs in 30d

Description

While collecting audio logs for internal debugging, I encountered an issue with the provided log collection scripts when they are executed from a directory path containing spaces.

Specifically, running I-can-make-it-happen-glitch.cmd from a location such as:
C:\Users\vraja\OneDrive - Microsoft Corporation\AudioLogs\CollectAudioLogs

causes the script to fail immediately with a path parsing error:
'C:\Users\vraja\OneDrive' is not recognized as an internal or external command,
operable program or batch file.

The issue appears to be caused by internal script calls not properly quoting paths that contain spaces. As a result, the script cannot be executed from common locations such as OneDrive folders or directories with space characters in their names.

Expected Behavior:
The log collection scripts should correctly handle paths containing spaces and execute successfully regardless of the installation or execution directory.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with I-can-make-it-happen-glitch.cmd and inspect its internal calls for unquoted paths. Run the log collection script from a directory such as C:\Users\vraja\OneDrive - Microsoft Corporation\AudioLogs\CollectAudioLogs, then verify that collection completes without the path parsing error.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell, shell
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
76/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.