Hello,

I am experiencing two separate but related issues with IBM Aspera Connect on Windows 11 (64-bit):

---

### Issue 1: Aspera Connect 4.x (latest versions) will not start
- Tested installers: 4.2.16 down to 4.2.11 (Windows x64, "Just me" installation)
- Symptoms:
  * Installation completes successfully
  * Launching asperaconnect.exe shows no tray icon, no window, and no persistent process in Task Manager
  * Even with "Run as administrator," nothing happens
  * Browsers (Chrome, Edge, Firefox) show the error:
    `startTransferPromise: No transfer method is available for starting a transfer`

---

### Issue 2: Aspera Connect 3.11.0.5 runs but cannot integrate with extension
- On another Windows 11 PC, version 3.11.0.5 runs normally (tray icon visible, process running)
- However, when trying to download assets via Chrome (with the latest Aspera Connect extension installed), I see the same error:
  `startTransferPromise: No transfer method is available for starting a transfer`
- This suggests that the **3.11.x client may not be compatible with the current extension version (4.x)**

---

### Troubleshooting already attempted
- Installed latest Visual C++ Redistributable (2015–2022, x64)
- Run as administrator
- Clean uninstall including AppData/Program Files/registry cleanup
- Compatibility mode (Win7/Win8)
- Tried multiple browsers (Chrome, Edge, Firefox) with extension enabled
- Same result across all tests

---

### Request
1. Please provide guidance on why Aspera Connect 4.x fails to start at all on Windows 11.  
2. Please confirm if the latest Aspera Connect browser extension is compatible with older 3.11.x clients.  
3. Could you provide a direct MSI download link for a stable version (e.g., 3.11.0.5 or 3.11.2) along with a matching extension, so that I can continue using Aspera for asset downloads?  

Thank you very much for your assistance.

Attachment(s)

aspera_eventlog.txt   1 KB 1 version

When connecting to the IBM Connect SDK on the website, it appears designed to prompt the download of Aspera Connect V3.11.

It seems IBM has not updated this to the latest Aspera Connect v4.X.

I also experienced Aspera Connect v3.11 failing to function properly after updating to the latest version of Windows 11.

Specifically, it would stop immediately after launching.

I understand Aspera Connect v3.11 is End of Support (EOS).

Installing V4.2.17.893 from the https://test-connect.ibmaspera.com/ site should resolve the issue.

Note that path issues can also occur with V4.2.15, potentially preventing Aspera Connect from functioning.