This is a bug in VB regarding how it accesses the references. Here are the steps to correct this simple problem:

When you get this specified cast is not valid error, go to the referenced folder in the Solution Explorer, and open the Silver References Folder.

You will see a list of references in this folder, like "System", "System.Data", etc.

Right click on each reference, select "Properties" and set "Copy Local" to false.

Close the Solution / Project and re-open it and you will no longer get that error.

If you are going to compile the solution for use on a different machine, set the "Copy Local" back to true to make sure all of the References are included in the build.

This "Copy Local" situation is not that much of a problem unless you start to add your own references and third party references. In this case, make sure you have "Copy Local" set to true if you are going to compile the app for use on a different machine that may not have the same references installed.