You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
User looked at %TEMP% and asked what was there. Found three real
issues, all fixed.
1. CRITICAL: ApplyResultsWindow XAML had Run.Text="{Binding Before}"
etc. on read-only properties of ResultRow. WPF's default Run.Text
binding is TwoWay, which fails on get-only properties with the
error "A TwoWay or OneWayToSource binding cannot work on the
read-only property 'Before'." Confirmed in user's
%TEMP%\gamerguardian_error.log — they triggered Apply in v0.1.18,
the window threw during measure, and they never saw the
verification details. Added Mode=OneWay to all four Run bindings
(Before, Desired, After, Mechanism). Will be fixed for users on
v0.1.20+.
2. Stale installer EXEs from the auto-update flow (~75 MB each)
were piling up in %TEMP%. UpdateService.DownloadInstallerAsync
writes them, launches them, then exits — never cleans up.
New TempCleanup.Run() called from OnStartup deletes any
GamerGuardian-Setup-*.exe in %TEMP% older than 1 day (1-day
grace so an in-progress install isn't yanked). Also one-shot
removes any stale gamerguardian_trace.log file from earlier dev
builds.
3. gamerguardian_error.log was append-only with no cap. Now rotates
at ~1 MB (.log -> .log.1) the same way changes.log does.
README gains a "Files GamerGuardian writes" table that documents
every path the app touches: install location, config, change log,
error log, self-test output, downloaded installers, autostart key.
Includes the "auto-cleaned on next launch" note for stale installer
downloads so users on v0.1.20+ know they don't need to manually
delete them.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: README.md
+17-1Lines changed: 17 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -225,7 +225,9 @@ GamerGuardian doesn't ask you to take its word for it.
225
225
| Power plan |`powercfg /getactivescheme`|
226
226
| HDR / Refresh / Resolution | Settings → System → Display, or `dxdiag`|
227
227
228
-
**4. The change log.**`%APPDATA%\GamerGuardian\changes.log` — every applied change (manual or silent auto-apply) is appended with a timestamp, source, before/after values, and verification status. Open it from *Settings → General → Open change log*, or from the Apply Results window. Sample line:
228
+
**4. The change log.**`%APPDATA%\GamerGuardian\changes.log` — every applied change (manual or silent auto-apply) is appended with a timestamp, source, before/after values, and verification status. Open it from *Settings → General → Open change log*, or from the Apply Results window. Auto-rotates at ~1 MB.
@@ -237,6 +239,20 @@ Auto-rotates at ~1 MB (`changes.log.1` keeps the previous batch).
237
239
238
240
**6. The source.** Every monitor is a single file under [`src/GamerGuardian/Monitors/`](src/GamerGuardian/Monitors/) that does exactly one thing each. Read [`HagsMonitor.cs`](src/GamerGuardian/Monitors/HagsMonitor.cs), say, to see the full code that reads and writes HAGS — about 30 lines.
239
241
242
+
## Files GamerGuardian writes
243
+
244
+
| Path | Purpose | Lifetime |
245
+
|---|---|---|
246
+
|`%LOCALAPPDATA%\Programs\GamerGuardian\GamerGuardian.exe`| Installed app | Until uninstall |
|`%TEMP%\gamerguardian_selftest.txt`| Output of `GamerGuardian.exe --test`| Overwritten each run |
251
+
|`%TEMP%\GamerGuardian-Setup-x.y.z.exe`| Installer downloaded by the auto-update flow before it launches |**Auto-cleaned on next launch** if older than 1 day |
252
+
|`HKCU\Software\Microsoft\Windows\CurrentVersion\Run\GamerGuardian`| Launch-at-startup entry | Created/removed by the *Launch at Windows startup* checkbox |
253
+
254
+
If you see leftover `GamerGuardian-Setup-*.exe` files in `%TEMP%` from before v0.1.20, you can delete them — they were the previous auto-update flow's downloaded installers. v0.1.20+ cleans them up automatically.
255
+
240
256
## Compatibility
241
257
242
258
-**Windows 11** (any version). Windows 10 support is on the roadmap.
0 commit comments