Install on Windows

Use the selected host’s available analysis operation to create a new run; preserve its input identity, engine version, diagnostics and saved output. Cloud jobs require an offered operation, permission and QUOTA. Cloud UVM and the Physical coordinator runtime remain unavailable. Opening a saved run, a setup dialog or a tool catalogue does not submit a job, and a rejected or unsupported action is never a successful zero-valued result.

Before you start

Use Windows 11 x64 (build 22000 or later) with WebView2 available. Download the signed MSIX from the official channel and compare its exact version, filename, SHA-256 and publisher with the matching metadata. Downloads lists the released 2.0.2 Windows and Linux packages. Select the package for this host and retain its matching metadata. Check the tools needed for your selected operation. Microsoft Store distribution is separate.

Save open work and keep a project backup. Existing Store, development and direct-distribution packages can have different identities. Do not uninstall an existing working package or delete its data to resolve an identity conflict; retain the installer message for support.

Download the package

1. Open the DDS download page and choose the Windows signed package.

2. Open the current metadata. Check available, version, filename in downloadUrl, SHA-256 and publisher.

3. Save the .msix and its matching metadata together. If the channel is unavailable, return to the official page later.

Verify the MSIX

In PowerShell, set the exact downloaded path and the SHA-256 from the matching metadata. A successful comparison checks the file bytes; Windows must also accept the package signature and publisher during installation.

Powershell

$DdsPackage = 'C:\Users\YOUR_USER\Downloads\YOUR_DDS_PACKAGE.msix'
$DdsExpectedSha256 = 'PASTE_THE_64_CHARACTER_SHA256_FROM_MATCHING_METADATA'
if ($DdsExpectedSha256 -notmatch '^[0-9a-fA-F]{64}$') { throw 'Set the published SHA-256 first.' }
$DdsActualSha256 = (Get-FileHash -LiteralPath $DdsPackage -Algorithm SHA256).Hash
if ($DdsActualSha256 -ine $DdsExpectedSha256) { throw 'DDS package checksum mismatch.' }
'SHA-256 matches.' 

The direct package publisher is Altifigence. Compare the full publisher shown in the metadata with the installation dialog or package signature details. A renamed file, matching display name or checksum alone is insufficient when Windows rejects its signature.

Install and open

1. Open the verified .msix with Windows App Installer and review the product and publisher.

2. Complete the Windows elevation prompt if installation of the packaged service requires it. Run the application normally after installation.

3. Open Digital Design Studio from Start and check Settings → General → About. Follow First launch to choose guest editing or sign-in. Windows My PC projects need no device licence; local simulators and GDS viewing require a signed-in account.

4. Open a small project, save a comment-only edit, close and reopen it, and confirm the saved content before using a production project.

Windows local files and existing WSL projects

Windows 2.0.2 opens Local / My PC projects directly from Windows folders and does not require WSL. Existing WSL project instructions apply to older releases that expose that connection. Preserve their distribution, original project and unsaved work; use an explicit verified export or copy before opening a separate Windows project. Do not uninstall WSL or delete its data as an app-update step. See: Windows and WSL projects

Update and recover

After an update, launch again and repeat the save/reopen check. Keep the previous verified installer and project backup until that check succeeds. Removing an application is not a backup procedure.

In-app updates and moving to another PC

When an in-app update is ready, save your work and follow the displayed restart instruction. It installs a newer signed version and does not perform a downgrade. Backups, moving projects and retained-installer rollback are covered in Update, move and roll back. The optional OSS simulators are installed separately after you request them; see First RTL simulation.

Using Digital Design Studio 2.0.2

Digital Design Studio 2.0.2 uses one application for RTL, ISA in Flow Navigator, and ALcad. Windows My PC, Linux desktop and Cloud have different execution hosts. A visible command or settings page does not establish that its engine is available. Check the selected host and the operation result before interpreting an output.

Cloud UVM and the Physical coordinator runtime remain unavailable. Built-in HLS, QEDA layout/solvers and virtual-FPGA Evolve require the Linux native host; they do not run on Windows or Cloud. Static OpenQASM circuit import is a separate Windows/Linux capability. A result viewer, imported report or AI response is not an engine execution or manufacturing signoff.

Save files and keep a separate project backup before updating. Before installation, use Downloads and Verify downloads to match the exact filename, SHA-256, signature and publisher of the package you install; the released 2.0.2 packages are listed there. The in-app Windows updater accepts a newer signed version; it does not downgrade. Keep earlier installers for investigation, but do not treat an old forced-downgrade recipe as a supported 2.0.2 recovery path. Linux update and Windows update are separate channels. Tray Open/Quit preserves the unsaved-work check; automatic OS restart, restored windows and rollback preservation require acceptance for the exact installed package.

2.0.2 environment support