A six-view Driver Center for Overview, Available Updates, Installed Drivers, Sources & Coverage, Recovery, and Activity.
System-wide discovery across every registered Windows or organization-managed update service that advertises driver updates.
Per-device Windows driver rollback with exact device and package evidence, restore-point-first protection, confirmation, administrator approval, and post-change verification.
Install now controls for exact Windows Update offers already selected in Praesidium, using the existing confirmation, restore-point, UAC, and revalidation workflow.
A selectable Windows restore-point workflow with a plain-language impact warning and handoff to the native System Restore wizard.
Immediate Aeternum-themed local-AI explanation flyouts with visible processing and deterministic fallback guidance.
Security & integrity
The official Windows x64 installer is Authenticode-signed by Aeternum IT Solutions LLC and timestamped by SSL.com.
The release asset publishes the exact SHA-256 digest shown on this page.
The stable signed update manifest points to version 2.38.6, the same official installer, and the same digest.
The public release includes an SPDX 2.3 software bill of materials and release checksum record.
Published SHA-256394EC27C98BB4FB064BC6B159E66678C9BF2CC4A2940B80B80A35DEB2AAC8F9A
Version numbers identify behavior. Signatures identify the publisher. Hashes identify exact bytes. Each answers a different verification question.
VERSION
2.38.6
The current stable public application and installer version.
PUBLISHER
Authenticode signature
Inspect the installer properties in Windows and verify the digital signature before running it.
CONTENT
SHA-256 digest
Compute the installer hash and compare every character with the published value above.
CHANNEL
Stable manifest
The signed production manifest names the same version, package, and digest.
SOURCE
Official download path
Aeternum’s stable download route resolves to the exact GitHub release asset.
LIMIT
No invented completeness
This record describes verified release evidence; it does not imply that every internal engineering change is public.
03 // Previous releases
Previous public releases.
Every archived entry remains tied to its published installer identity, complete customer changelog, and release record. Earlier internal builds are not presented as public releases.
Aeternum publishes what changed, what file was released, and how that file can be identified. Unknowns remain named rather than converted into marketing claims.
01
Identify
Name the product, version, channel, date, and supported platform.
02
Describe
Categorize only changes supported by the release record.
03
Verify
Publish the installer signature path and exact SHA-256 digest.
04
Preserve
Keep the record available after the next release replaces it.
