For those of you who are experiencing the 0x643 error, we would like to extend our apologies for your frustration. The number of Network Magic 4.7 users who have experienced this error is less than 1%. But I'd like to assure you that we are putting forth our greatest effort in the support department, test department, and development department to resolve the issue that we are seeing. Your patience and understanding are greatly appreciated.
The root of the issue is due to a change in Network Magic's installer technology that was made in Network Magic 4.5. In Network Magic 4.5 the Network Magic service became the Pure Networks Platform Service, and was put into a separate installer. NMSetup.exe (the Network Magic installer) first installs the Platform, then installs the Network Magic application. The 0x643 error occurs when the Platform installation fails for ANY
So while several customers are receiving the same error message and error number, once we dig into the logs sent to us, there are a variety of problems we're seeing. The bulk of the problems seem to be related to flaws in the Windows MSI installer technology and Windows itself.
With the information that we have, and knowing the nature of Microsoft Windows and the Windows MSI installer technology, one brute force solution would be to format your hard drive and reinstall Windows. Due to the severity of that solution, we are currently investigating other possible solutions.
While we have come across a handful of solutions that have solved a handful of customer issues, we are are currently working to find a solution that will help anyone experiencing this error.
As with other rare issues, we appreciate anyone who is willing to work with us to develop a solution. At this time we are providing theoretical solutions to such customers. Many of these hopeful-solutions are our best guesses and any feedback about these solutions is greatly appreciated.
The most recent fix suggestion is this:
We do believe we have made a pretty significant stride in finding a solution to what the problem is. I firmly believe this is what's going to be our solution, so please be mindful of the steps below:
As with Beta's we are always interested in the logs provided when an error occurs, so if this particular problem is afflicting you, please send us your logs by downloading and running this sendlogs tool from the computer experiencing the problem:
Please remember to let us know the full and exact text of the error message you are seeing when you send us your logs.
The rest of the solution can be found in our general FAQ support page here:
Things to note:
The cleanup script is itself a beta let us know how it works for you.
The script will report some errors while it is running this is expected
NM or SMP will not be entirely removed when doing this the tool is not intended to do this. You need to upgrade to a newer build than what you have after you are done.
The script works on XP and 32-bit Vista only.
If you follow these steps and are successfully, or unsuccessfully, able to resolve the problem, please let us know.
Again, I would like to extend a personal apology from myself for the error that has been occurring and assure you have I dedicated a significant portion of what I do to resolve this error and completely sympathize with your frustrations.