# Unable to install MemryX runtime v2.2 on Windows **URL:** \ **Category:** Technical Support\ **Created:** [April 17, 2026, 11:25pm UTC](https://community.memryx.com/t/unable-to-install-memryx-runtime-v2-2-on-windows/200 "2026-04-17T23:25:01Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![barkas](https://avatars.discourse-cdn.com/v4/letter/b/858c86/32.png) [@barkas](https://community.memryx.com/u/barkas)\ **Post date:** [April 17, 2026, 11:25pm UTC](https://community.memryx.com/t/unable-to-install-memryx-runtime-v2-2-on-windows/200/1 "2026-04-17T23:25:01Z")
I was upgrading a previous 2.0 MemryX runtime & driver installation, which was working just fine. Here is the steps I followed: - Downloaded MemryXInstaller.exe; - Ran it as Admin; - Checked in Device Manager and saw accelerator connected; - Next step failed: PS C:\Users\degirum\> acclBench --hello DLL\_PROCESS\_ATTACH Hello from MXA! [2026-04-16 12:30:13.451] [error] [Client] Exception: connect: No connection could be made because the target machine actively refused it. [2026-04-16 12:30:13.457] [warning] [DeviceManager] Local memx\_get\_feature() failed for device 0. [2026-04-16 12:30:13.459] [error] [DeviceManager] Invalid chip count 0 or group count 0 for device 0 Device ID | Chip Count | Freq | Volt ----------|------------|-------|----- ``` 0 | 0 | ``` Tried to reinstall several times, no way ---
**Author:** ![lindsay.morel](https://avatars.discourse-cdn.com/v4/letter/l/59ef9b/32.png) [@lindsay.morel](https://community.memryx.com/u/lindsay.morel)\ **Post date:** [April 20, 2026, 7:52pm UTC](https://community.memryx.com/t/unable-to-install-memryx-runtime-v2-2-on-windows/200/2 "2026-04-20T19:52:11Z")
Hello, Thanks for the detail! From the steps you’ve listed, it’s unclear whether you have been performing a system reboot after the installer completes as per the instructions on the [Developer Hub](https://developer.memryx.com/get_started/install_windows.html) (see Step 5 under ‘Installation’). This is an important step in the installation process and must not be overlooked. We went ahead and tested the installer script this morning on a Windows system, and it seems to be working on our end. If you have been performing a reboot following installation, just let us know here, and we’ll be happy to help you with further troubleshooting. Thank you!