Product icon Help book icon Installation and Troubleshooting : Knowledge Base

Common Error Messages and Symptoms

The errors on this page were reported by one or more customers and resolved with the specified actions.

A. First, Restart your computer

Description: Some problems happen just due to Windows itself being in an unstable state and needing a reboot. The error might be a fluke.

Resolved by: Restart your computer if you haven't yet. Then try running the program again.

B. Installer Program will not start.

Description: If the Installer Program will not run, it may have detected that your .Net Framework prerequisite is missing.

Resolved by: Verify which version(s) of .Net are installed -- see the .Net Framework Prerequisite section of this Knowledge Base. Then install a missing prerequisite if necessary.

C. Unable to install because a newer version...

Description: When running the Installer Program, you get the following message.
"Unable to install because a newer version of this product is already Installed."

Resolved by: It is likely that you did not uninstall a previous release before installing a new one. Go to the Windows Control Panel -- Programs and Features ( Windows® 10/8/7 ) or Control Panel -- Add or Remove Programs (XP) and look for the program in the list. If found Remove/Uninstall it, then try running the Installer Program again.

D. Program will not start, no error message

Description: We assume here that the program had been successfully installed (ie. the installer MSI file was run and showed no errors, and the program appears in the Windows Control Panel -- Add or Remove Programs list). Then when you try to start the program, it does not start and you may get no error message at all or some generic Windows error similar to the following.
Sound Mill has encountered a problem and needs to close.
If you look at the Details, you may see this error which indicates one of the program components could not be found.
P9 : system.io.filenotfoundexception

Resolved by: This is most often a missing or back level program prerequisite (.Net Framework, etc.). You should start the program in TEST MODE to get a more descriptive error message. TEST MODE error message will often give a good clue as to which prerequisite is bad or what the problem is. If the problem isn't obvious, send the error message to Support.

E. Program window has disappeared

There are a couple unique situations where a program window may be moved to a location entirely outside the boundaries of your primary display. The window is simply out of view but the program still has a taskbar button. This can happen if the window was located on a secondary display which is then disconnected. Or sometimes if the program configuration file somehow gets corrupted (ex a Windows crash while the program is open, etc.).

To remedy this condition follow these steps:

  1. On Windows XP, right-click on the program's taskbar button.
    Or on Windows® 10/8/7 , point at the program's taskbar button to see the program's live preview popup. Then right-click on the preview popup.
  2. From the resulting context menu (or Jump List), click Maximize. This makes the window full screen.
  3. Now close the program while it is Maximized.
  4. Then restart the program. It should now be on screen and you'll be able to resize it by dragging the gripper on the lower righthand corner of the window.

F. Program window frozen

Program freezes can be a result of a faulty hardware device driver (soundcard or video card device driver). Error messages for drivers are usually found in the Windows Event Viewer. Verify that all hardware connections are seated properly. Sometimes the remedy is locating and installing an updated driver from the hardware manufacturers website.