What do these messages mean?

[WSinc]

I get these every time I stop debugging a program.

This has been going on for some time.

Also, why does my browser give me "security certificate errors" when I go here?

I have IE 8.0 (not sure of version number, but it is recent)

see below -  I don't know what the PDB file is anyway.

'plmin1.exe': Loaded 'D:\William Data\My Documents\Visual Studio 2010\Projects\plmin1\plmin1\Debug\plmin1.exe', Symbols loaded.

'plmin1.exe': Loaded 'C:\Windows\System32\ntdll.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\kernel32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\KernelBase.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Program Files\AVAST Software\Avast\snxhk.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\user32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\gdi32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\lpk.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\usp10.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\msvcrt.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\comdlg32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\shlwapi.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\comctl32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\advapi32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\sechost.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\rpcrt4.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\shell32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\imagehlp.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\imm32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\msctf.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\uxtheme.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\dwmapi.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\ole32.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\System32\cryptbase.dll', Cannot find or open the PDB file

'plmin1.exe': Loaded 'C:\Windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.dll', Cannot find or open the PDB file

The thread 'Win32 Thread' (0x7b8) has exited with code 0 (0x0).

The program '[7968] plmin1.exe: Native' has exited with code 0 (0x0).

[IanH]

Every time you stop debugging, or every time you start? When your program loads a DLL (all of the ones you show are system DLL's that are near ubiquitously loaded by all programs at program startup) the Visual Studio debugger gets a notification. For all VS knows that DLL might contain code that you want to debug, so it goes looking for the debug information for that DLL, which is a kept in a PDB file with the same base name. The messages you see are just indicate that it was unable to find that file - the debugging information for system DLL's is not installed with the Windows operating system by default. These messages are harmless, unless you really do want to understand how you program interacts with those system DLL's. You can control how Visual Studio looks for symbols using the dialog Tools > Options > Debugging > Symbols. Here you can explicitly tell VS not to try and load symbols for certain modules, but if I recall correctly you'll still get a harmless message in the output window (similar to what you show) saying "you told me not to load symbols for this DLL".

[WSinc]

Every time I STOP debugging. I don't always get this though.

[IanH]

Humour me - set a break point on the first executable line of the program, start it running under the VS debugger, when the break point is hit then select the Output pane in Visual Studio and scroll it up to the top.