It was a new install on a new install of Windows. It isn't just leftover files from an upgrade like that one document suggests, or downgrading wouldn't help. I don't do remote management so I think that's OK for me, but obviously there's a bug. Using the old version is really not ideal - it is vulnerable to the log4j exploits - which was the whole reason for the new 17.05.06.00 update It would be useful to have at least a few prior versions of MSM available for download. I found a download for MSM 17.05.02.01 which also resolved it for me. If I uninstall l 17.05.06.00 and go back to the previous version (17.05.02.01) it once again starts working fine. I have verified that the MSMFramework service is running, and I have also checked with netstat that it is listening: Servers could not be found because server may be down or server not installed in the host system

After installing it I can no longer connect to the server: I would like to report a bug in the latest MSM release 17.05.06.00 (with complete install).

I've tried all the troubleshooting - reinstalling after manual cleanup, checking that the driver is showing, ensuring the services are running, etc.

This is not a remote connection - the MegaRAID is on this machine. Where can I get the previous version? I've been trying to get MSM to work on a new installation of Windows 10 after my old Windows installation got fatally damaged. Subject: Bug in MegaRAID Storage Manager 17.05.06.00 Not Connecting

Avago megaraid storage manager download