You are welcome. "In testa che avete, Signor di Ceprano?" -- Rigoletto

Interesting but keep in mind that the code as written does not 'use' TLS 1.3. Rather it attempts to specify it and then backs down if the system tells says it is not available. I suspect one would also want to verify that something else is not also doing a backdown even further down the line. (Keep in mind my first post where I mention that encryption algorithms might also be needed which is only determined by the windows OS.)

Yep, you are absolutely right. I already was able to "reconstruct" that behavior and it is simply the lack of connections established that leads to this problem. So basically each time i need to do a query which is not part of a greater transaction we open up another connection. Issue solved :) Rules for the FOSW ![^] MessageBox.Show(!string.IsNullOrWhiteSpace(_signature) ? $"This is my signature:{Environment.NewLine}{_signature}": "404-Signature not found");

theoldfool wrote: Remember: "yes dear" i guess in our case it'l be "yes my Lady"... Women with a title :suss: Rules for the FOSW ![^] if(!string.IsNullOrWhiteSpace(_signature)) { MessageBox.Show("This is my signature: " + Environment.NewLine + _signature); } else { MessageBox.Show("404-Signature not found"); }

Awesome thinks for the link Technician 1. A person that fixes stuff you can't. 2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge. JaxCoder.com