DLSSync v1.6.5

DLSSync can keep your DLLs current on its own now — a background daemon that scans on a schedule, sits in the tray, and warns you before you touch a game that can ban you for it.

Added

• Background updates. Turn it on and DLSSync rescans your library on a schedule (every 1 to 168 hours) even with the window closed, shows how many games have updates ready in the tray, and raises a Windows notification when something is waiting. It can close to the tray instead of quitting, start with Windows minimized, and apply everything in one click from the tray, the notification, or the Library header. Optional auto-apply always skips anti-cheat games and makes a backup first. Off by default.
• A ban-risk warning at the moment you apply. Games protected by Easy Anti-Cheat, BattlEye, or Riot Vanguard now show a risk chip next to Apply and ask for one explicit confirmation before any DLL is replaced — the warning lands at the apply step, not buried in a panel.
• Manifest signature verification (Ed25519) against a key baked into the app. Verification ships now; fail-closed enforcement is staged for a later release, once the signed manifest is live across the CDN.

Changed

• Notification logos come from the component being updated, not a guess at the wording — so a DLSSync release no longer shows up wearing NVIDIA's logo, and an FSR or XeSS update wears the right one.
• The close-to-tray and start-with-Windows switches moved into the new Background updates section; the Performance section keeps the efficiency (EcoQoS) toggle.
• In release builds the catalog URL can no longer be redirected by an environment variable.

Fixed

• Duplicate driver notifications are gone — dedup is enforced in the database instead of racing in memory — and the ones that had piled up are pruned the next time you launch. Apply notifications also stop being swallowed after the first one per game.
• Authenticode checks validate the whole certificate chain for revocation, falling back only when the machine is offline.
• ZIP extraction is bounded by the bytes actually written rather than a size the archive claims, a single failed download no longer poisons that file's cache for the rest of the session, a cancelled apply stops sooner, and a failed item in a batch now reports which one.
• Updated the test runner to clear a security advisory.