"Cannot find or open the PDB file" from Visual Studio 2013 RC

What matters the most is fine, the symbols for your own code could be loaded: ...ConsoleApplication4.exe'. Symbols loaded.

The rest of the missing symbols are for the .NET system's assemblies (dlls). They are not needed all the time, you can debug your code without them, but if you do advanced things like messaging, majority of your stack won't be able to be unrolled (or sometimes it's called "symbolicated").

I prefer to have as much system pdbs (debug symbol files) as possible. It's very easy to setup with VS 2012, I assume that VS 2013 is just as easy or even better. http://msdn.microsoft.com/en-us/library/b8ttk8zy%28v=vs.90%29.aspx

Note, that after setting up symbol downloading you'll experience major delay the first time you'll debug your code. That's when the symbol downloading happens. Once that's done starting debug will be fast again (because new symbols are only needed if the .NET system gets some updates which affects your assemblies too).

I also install "Debugging Tools for Windows xy" and "Windows xy SDK" too (where xy=7, 8, 8.1, 10 depending on which Windows you are using, plus the architecture matters too: X64 or 32), even if I only debug managed (that's the term for programs written in .NET garbage collected and handled languages) code. http://msdn.microsoft.com/en-us/library/windows/hardware/ff551063%28v=vs.85%29.aspx

One assembly you may not get symbol for is the ConsoleApplication4.vshost.exe. That's a stub what Visual Studio debugger uses to start your program. You can see it in the Process Explorer (Sysinternals Tools suite), sometimes more instances are lingering around.