Windows Vista and Framework 4.5.1 compatibility with TLSv1.2

Question

Windows Vista OS by default does not come with TLSv1.1 and TLSv1.2. However the support is offered by installing .NET Framework 4.5.1.
I have a c# Winforms application using .NET Framework 4.5.1. I use ServicePointManager to default the TLS level to TLSv1.2. This works fine on Windows 7 and above.
Running my app gives the following error:
Type : System.ComponentModel.Win32Exception, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
 Message : The client and server cannot communicate, because they do not possess a common algorithm
 Source : System
 Help link :
 NativeErrorCode : -2146893007
 ErrorCode : -2147467259
 Data : System.Collections.ListDictionaryInternal
 TargetSite : System.Net.SafeFreeCredentials AcquireCredentialsHandle(System.Net.SSPIInterface, System.String, System.Net.CredentialUse, System.Net.SecureCredential)
 HResult : -2147467259
 Stack Trace :    at System.Net.SSPIWrapper.AcquireCredentialsHandle(SSPIInterface SecModule, String package, CredentialUse intent, SecureCredential scc)
    at System.Net.Security.SecureChannel.AcquireCredentialsHandle(CredentialUse credUsage, SecureCredential& secureCredential)
    at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint)
    at System.Net.Security.SecureChannel.GenerateToken(Byte[] input, Int32 offset, Int32 count, Byte[]& output)
    at System.Net.Security.SecureChannel.NextMessage(Byte[] incoming, Int32 offset, Int32 count)
    at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
    at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
    at System.Net.TlsStream.CallProcessAuthentication(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.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
    at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
    at System.Net.ConnectStream.WriteHeaders(Boolean async)
Is there a fixpack orsomething i need to install?
I am using Windows Vista Business 32bit Service Pack 2.
Thanks for the help

Answer 1

Those two updates went away. The update history does not show them having succeeded in installing. They are just gone. But a new .Net update shows up in Windows Update: KB2858725. It also fails to install with error code 641.
I tried running it manually (I'm trying to paste the whole file name here, but all that shows up is ENU.exe. Seriously!? What the fuck!?) and that fails. "Installation did not succeed. .Net framework 4.5.1 has not been installed because: the windows
installer service could not be accessed." A dialog comes up that has a link to a log file, but clicking it does nothing.
I tried following the suggestions in
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/need-to-reinstall-windows-installer-in-windows-7/4cb8e54c-5a4e-439d-9d46-1dcd387d2604
I tried running sfc /scannow. It returned message:
Beginning system scan.  This process will take some time.
Beginning verification phase of system scan.
Verification 18% complete.
Windows Resource Protection could not perform the requested operation.
The other changes didn't apply except unregistering and reregistering the Windows Installer. None of that made any difference.
Today, an update to Windows Activation Technologies showed up: KB971033. I tried to install that and it says that it succeeded.
KB2858725 still fails.
Here's a link to the part of my WindowsUpdate.log file after I tried to run the update of KB2858725 once again from Windows Update:
https://onedrive.live.com/redir?resid=6C4435A4094C794E!251&authkey=!AFGBKgKlV8eTFiE&ithint=file%2c.log