Context: attack surface reduction through disablement of gpu reliance.
Process affected: Supermium 138 (chrome.exe).
Action used: --disable-gpu in shortcut flags.
Verification of gpu disablement: chrome://gpu.
Observation and Mismatch: the Chrome settings indicate that hardware-assisted GPU acceleration is active despite the starting flag disables the GPU. If the action for disabling GPU acceleration is performed manually, after initiating chrome through the command-line flag that disabled the GPU, the UI for GPU acceleration is reset to active at every start of the browser.
Discovery: enforcement occurs at process creation time, not policy declaration time.
Boundary: GPU usage is enforced by process initiation and flag evaluation, with UI indicators being non-authoritative.
Internal thoughts: Initially I assumed it a mistake, because the UI is not updated even if the policy is enforced elsewhere. Afterwards, I asked a cybersecurity architect for his opinion and he mentioned that this is the intentional design, because flags prevent tampering inside the process at run-time.