1.  Please make sure you are using the latest drivers provided by your video card manufacturer: ATI, nVidia

---

2.  Please verify that you have the latest Service Pack for your Operating System installed (Windows Vista SP2, Windows XP SP3): http://windowsupdate.microsoft.com/ 

---

3.  Another user reported the following fixed his issue on Windows 7: "After going into the resolution settings for the display and clicking detect, and then ok, the MuvUnder Cover window displayed.

---

4.  If the above solutions still don't correct the issue, you can try updating your version of DirectX.

http://www.microsoft.com/downloads/details.aspx?FamilyID=2da43d38-db71-4c1b-bc6a-9b6652cd92a3&displaylang=en

---

5.  Some users have reported that restarting their computer does the trick.

---

6.  If during the installation of MuvUnder Cover, the .NET Framework 3.5 SP1 was not installed, MuvUnder Cover will not run.  Please re-run the installer and make sure you install the .NET Framework 3.5 SP1 when asked.

If that does not resolve the issue, you may need to repair your .NET installation by doing the following:

• Click on your "Start Menu".
• Click on "Control Panel".
• Double-click on "Add/Remove Programs" on Windows XP or "Programs and Features" on Windows Vista. 
• If "Microsoft .NET Framework 3.5 (SP1)" is listed click on it and then click on "Change/Remove" on Windows XP or "Uninstall/Change" on Windows Vista/7.  On the next window, make sure "Repair" is selected and click "Next".
• If "Microsoft .NET Framework 3.5 (SP1)" you will need to re-run the MuvAudio installer and have it install the .NET Framework 3.5 SP1 when prompted.  You can also manually download and install the .NET Framework 3.5 SP1.
  
• This should repair your installation of the .NET Framework.
• Now, restart your computer and try running MuvUnder Cover.
• If MuvUnder Cover still fails to load, you may need to follow the steps at the following site to fully repair the .NET Framework (we cannot and do not guarantee the content of the site or any actions it tells you to take in resolving this issue): What to do if other .NET Framework setup troubleshooting steps do not help.