v8.0 and MM v5.42 Upgrades

[robert5733]

I see that v8.0 is now out, I am in the middle of some major changes myself so I was putting off the 8.0 upgrade until after working out the Windows upgrade. One at a time as they say. So first question

I accidentally installed the new MM v5.42 and it remade my database and made some changes and created conflicts I wasn't ready for, so I reverted to a backup and started over with 5.40. I know they removed WMC in the upgrade, are you running the v5.42 or still on 5.40 and are you having any problems with 5.42 if you did the update? I know that in order to install 5.40, because the link to the SQL Server is no longer valid, now you have to install 5.42, then after it downloads the SQL Server, you quit the install with task manager and then install 5.40 and it works.

Second, before updating to CCC v8.0, will I need the MM v5.42 update? I want to go at it one at a time, so I am essentially asking should I do MM or CCC first?

[Pauven]

I'm still running 5.40, or at least I think I am. I run MM and CCC inside a virtual machine on my NAS server, and the SSD they were on died a few weeks ago, and I haven't recovered yet. (Side rant, that's now 3 dead Samsung SSD's due to bad firmware on the SSD's. I used to swear by them, but I didn't learn about the firmware issue until after the first two died, and somehow I totally forgot I had a 3rd one hiding in my server. I will never buy Samsung drives again, too much pain inflicted, even if their current drives are okay now). So I can't start up my MM VM PC to even see what version it is running.

I think other users here are on 5.42, but I have seen an uptick in complaints lately, so I'm not sure if 5.42 is a good idea. I think it's best to treat it as suspect.

CMC is a replacement GUI styled to look like WMC, but CMC/CCC has never used any WMC features that were in MM. So I don't think the removal of WMC functionality is an issue, but there might have been side effects, like a disabled port # that I was accessing might now be gone, or API commands might be depreciated/disabled. So again, I say 5.42 is suspect until more is known.