AccessViolationException before first line of code in empty program with VS2013 and .NET 4.6

I recently installed .NET 4.6 on my development system, but I am still using Visual Studio 2013. Since installing .NET 4.6, I get an AccessViolationException whenever I try to run the program with debug:

at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at System.AppDomain.nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

      

        
        
        
      

    

This happens even if the program targets .NET 4.5 and even completely trivial programs. This does not happen when you run a program without a debugger attached in a debug or release build.

An example of a failed program:

class Program
{
    static void Main(string[] args)
    {
    }
}

      

        
        
        
      

    

What's happening?