DiagReport.bat exits with no results to view
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.6k
- Forks
- 592
- PR merge metrics
- No merged PRs in 30d
Description
rem "Exit" version:
rem powershell -noprofile -command "&{start-process powershell -ArgumentList '-noprofile -file \"%scriptPath%\"' -verb RunAs}"
powershell -noprofile -command "&{start-process -Wait -WindowStyle hidden powershell -ArgumentList '-noprofile -file \"%scriptPath%\"' -verb RunAs}"
Tested on two Windows 10 laptops and one Windows 10 VM.
Windows 10 VM runs fine and pops up with results in Notepad.
One laptop it's random - about every 3rd or 4th time I get results.
Other laptop - no results until modifying the .bat file.
All three are probably slightly different versions of Windows and Powershell.
The change above (adding -Wait -WindowStyle hidden) gives report output without popping up a new window or requiring the user to hit a key to exit.
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.
Research direction
Start with DiagReport.bat and compare the shown PowerShell invocation with the commented version. Test the diagnostic report on the reported Windows 10 environments; done means the report reliably opens with results, without an extra visible window or requiring a key press to exit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, shell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100