mirror of
https://github.com/rmcrackan/Libation.git
synced 2026-09-13 06:07:30 -04:00
Cursor Agentandrmcrackan
a0ca574974
An in-app upgrade overlays files Windows has never seen. Smart App Control blocks unsigned files it does not recognise, so upgrading in place under enforcement is precisely how a working install becomes one that cannot start, which is what #1873, #1876 and #1967 all describe. Read VerifiedAndReputablePolicyState under HKLM\SYSTEM\CurrentControlSet\Control\CI\Policy to find out. The read needs no elevation and cannot raise a UAC prompt: UAC prompts only on an explicit elevation request, and HKLM is readable by standard users. Only the value 1 counts as enforcing. A missing key, a missing value, or anything unrecognised counts as not enforcing, because the cost of guessing wrong is telling someone to disable Smart App Control, which cannot be undone, on a PC that was never blocking anything. When enforcing, the upgrade notification becomes a notice with the download link instead of an update prompt, and the flow stops before downloading even if a UI ignores that. Classic honoured no such flag at all, so its dialog now takes one; its two prompt labels had to be promoted from designer locals to fields to carry the explanation. The blocked-file dialog now states the setting it found rather than asking the user to go and look, and startup logs the state, the install folder, and any cloud sync root containing it, so a report answers these without a round trip. Co-authored-by: rmcrackan <rmcrackan@gmail.com>