Collecting diagnostic logs for support

What to collect

When you open a support request, include as much of the following as you can. It lets support diagnose without a back-and-forth.

If LogsFolder is set by policy, the logs are in that folder instead of the default.

Quick collection script

This gathers the logs, version, and applied policy into one folder and zips it:

$out = "$env:TEMP\deck-diagnostics"
New-Item -ItemType Directory -Force -Path $out | Out-Null

# Logs
Copy-Item "$env:LOCALAPPDATA\Vediram\Deck\core.log"       $out -ErrorAction SilentlyContinue
Copy-Item "$env:LOCALAPPDATA\Vediram\Deck\core-error.log" $out -ErrorAction SilentlyContinue

# System + policy snapshot
"Windows: $([System.Environment]::OSVersion.Version)" | Out-File "$out\system.txt"
Get-ItemProperty "HKLM:\SOFTWARE\Policies\Vediram\Deck" -ErrorAction SilentlyContinue |
  Out-File "$out\policies-machine.txt"
Get-ItemProperty "HKCU:\SOFTWARE\Policies\Vediram\Deck" -ErrorAction SilentlyContinue |
  Out-File "$out\policies-user.txt"

Compress-Archive -Path "$out\*" -DestinationPath "$env:TEMP\deck-diagnostics.zip" -Force
Write-Host "Created $env:TEMP\deck-diagnostics.zip"

Attach deck-diagnostics.zip to your support request.

Reading the activity log yourself

core.log is timestamped and categorized ([Policy], [discovery], profile activation, crash analysis, metrics). Common quick checks:

# Last 60 lines
Get-Content "$env:LOCALAPPDATA\Vediram\Deck\core.log" -Tail 60

# Only policy-related lines
Select-String -Path "$env:LOCALAPPDATA\Vediram\Deck\core.log" -Pattern "\[Policy\]"

Note that core.log is trimmed to roughly the last 1000 lines each time the daemon starts, so capture it before restarting Deck if you're investigating a one-off event.

Crash investigations

For add-in crashes specifically, the Crashes page in Deck already shows the analyzed reports (faulting module, tier, stack trace). Include the relevant report details along with the logs above. See Crash Analysis.