v0.3.2 — Add mask… from the dropdown, and three false claims removed from the docs

Create a mask without leaving the page you are on.

⚠️ Not yet code-signed — and v0.3.1 said this one would be

v0.3.1's notes said the next patch would ship code-signed. This is that patch, and the
certificate is not in place yet, so it is not signed. Saying so here rather than quietly
letting the earlier note stand.

Signing has been chosen — SignPath Foundation, which is free for open-source projects — and
is being set up. It is not in place yet, and the release that carries it is the one to wait
for if you would rather not deal with the warning below. Nothing else
about the situation has changed since v0.3.1, and this build has the same standing as that
one: Windows may quarantine it.

Why it happens, measured on one machine with the same engine and the same definition
version within a single hour: an older build scanned clean, a build that had been flagged
earlier the same day scanned clean again — its verdict had reverted on its own — and the
freshly published one was flagged. No definitions changed between those scans. The verdict
is cloud-delivered and it moves. Windows judges every brand-new, rarely-seen, unsigned file
on its own, and Microsoft documents that unsigned files start from zero reputation on every
new version, so nothing an older build earned carries over.

Verify what you downloaded against the hashes at the bottom before trusting it — hash
the zip, or the loose exe if that is all you kept. If the hash matches and Windows still
quarantines it, that is a false positive on this build. Restoring it from quarantine is your
call to make with that information; this project is not going to tell you to switch your
antivirus off, add an exclusion, or ignore a warning.

You can also report it at https://www.microsoft.com/en-us/wdsi/filesubmission — choose
"incorrectly detected" and set the priority to Medium; expect a few days, and a review is
not a promise. Please also open an issue here with the detection name and the date.

What was seen on v0.3.1, kept here because this release supersedes it: the detection
name was Program:Win32/Contebrew.A!ml, severity High, category "Settings Modifier". The
three-verdict measurement above used engine 1.1.26080.3 and definition version
1.457.447.0 throughout — v0.2.0 clean, an older flagged build clean again, v0.3.1 flagged.

Why a scanner scores this app at all, stated plainly: it enumerates processes, opens
the game's process to set its CPU Sets, controls one AMD service when you ask it to,
writes a Start-with-Windows entry when you ask for one, and briefly runs an elevated copy
of itself for the one action that needs administrator rights. All of it is in this
repository.

If it was quarantined: Windows also deletes the Start-with-Windows entry it finds, so
switch "Start with Windows" back on in Settings afterwards.

---

Add mask… where you actually need it

"Add mask…" is now an entry in the mask dropdowns on the Profiles page, at the bottom of the
list, in both Game mask and Heavy apps mask. Choosing it asks for a name, copies the mask
you were looking at, and selects the new one — the same thing the button on the Core map page
does, without going there.

• Cancel the prompt, pick a name that already exists, or pick a reserved one, and your previous
  selection comes back. The entry is never left selected.
• It works from the keyboard as well as the mouse.
• The Core map page keeps its Add mask… and Remove mask buttons; nothing moved away from
  there.

A mask cannot be named "Add mask..." — that name is now refused, so nothing in the list can
impersonate the action.

Also in this release

Everything from v0.3.1, which was public for barely an hour:

• Named custom masks on the Core map — Add mask… and Remove mask. Removal refuses while a
  profile still uses the mask and tells you which profiles; an empty selection is rejected at edit
  time, because an empty CPU Set list is how this app clears an assignment rather than applying
  one.
• Custom masks survive a topology change. The re-derive merges instead of overwriting and tells
  you how many of yours were kept — their processor numbers may mean different cores afterwards,
  so check them.
• Names the app derives on its own — All, Cache, Freq, CCD0 and so on, P-cores,
  E-cores, and the no SMT form of each — are reserved on every machine, not only one that
  has that hardware today, so a config carried to a new CPU cannot collide with a detected mask.
  Existing configurations are untouched: the rule applies when you create a mask, never when one
  is loaded.
• The README's "If Windows Defender flags it" section.

Verify your download

certutil -hashfile GameOptimizer-v0.3.2-x64.zip SHA256
certutil -hashfile GameOptimizer.exe SHA256

file	SHA256
GameOptimizer-v0.3.2-x64.zip	8F8D30CB47B9A89CBFF338375D856E869D9EE9C51A24E6723CF87F537A575CC0
GameOptimizer.exe (inside the zip)	39FDD42D257D801DF41381A70C46BD58B809F0E1CB67DA25C31FD8BD68A25A26

Notes

• Requires Windows 10/11 x64. Unzip and keep WebView2Loader.dll beside GameOptimizer.exe.
• Building from source gives you a binary you compiled yourself; it will not be byte-identical to
  this one.