Security updates are not enhancements or bug fixes. I doubt that you have an ESU contract.
Your issue has been addressed by Microsoft for years. I have received more than 100 emails nd articles warning of this and that it would be an issue. I addressed this issue with one customer two years ago. The customer forced us to remove the patch
because they had services that they used that failed to implement the new requirements.
The cause of this has nothing to do what Microsoft. TLS is not a Microsoft product. m Windows 7 was altered to address this issue years ago but noon-technical users likely didn't read any of the articles and emails sent out by Microsoft and most other
vendors.
There have also been numerous articles and discussions about how to allow PowerShell on pre-Win10 systems to address this issue.
To understand what happened you first have to take the time to learn what TLS is. This can be easily learned by searching or by getting a modern book on networking.
As an example of what happened to you consider what happened to all of the millions of people who were using Widows 3.1 and modems for networking. Why is this no longer done? We can still buy modems. What changed?
Why is TLS not an issue on Windows 10? How does TLS effect Windows? Where is it used? Why is it used?
To understand this and the answers to these questions you will need to learn computer engineering and network engineering as a pre-requisite,
Since you are an end user and not an engi9ineer or trained technician I can only say that you have hit a common wall. The world changes, Things in technology change. Companies hire trained and certified or degreed technical professionals
to keep the company in sync with these world changes.
Have you tried talking to the people responsible for your network? Do you have a network engineer in the company or does your company rely on consultants? Either would be able to help you.
Also you failed to tell us what stopped working with your script. Code that worked on Windows 7 still works on Windows 7 assuming you didn't change the code. ON Windows 7 and Windows 10 the code could be written to fail on both the same way.
Turn off the default security protocols on Windows 10 and the script will fail the same way. The cause of the failure has nothing to do with Windows. What was the code doing? What changed and why did Win10 keep working?
This is the kind of rut you get into by blaming others for failures that are not really failure but are the result of change. Learning the basics of networking and Windows are the first step to understanding change.
To demonstrate what is happening you can do the following:
On both Win10 and Win7 run the following at a prompt
[enum]::GetNames([System.Net.SecurityProtocolType])
Now run the following line on both systems:
[Net.ServicePointManager]::SecurityProtocol
Notice the difference.
Now read the following: https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi
Notice that Microsoft published that article years ago.
PowerShell 3 is a very old version of PowerShell. It was written before these changes. PowerShell 5.1 on Windows 7 can use the protocols but was not written to set the system default. This was for compatibility. Windows 10 came with
the protocols enabled and the SystemDefault set for the future. Y
The future arrived for you in January 2020. You stumbled into the future like someone who only new about horse and crossed paths with a horseless carriage.
Microsoft an al other vendors warn us constantly about changes (breaking changes) but companies require either trained technicians, a consultant or a Microsoft support contract to keep up with the changes since desktop people in companies are not trained
beyond the basic GUI.
AS to why your script stopped you will have to determine what the script was doing when it failed. This would be part of the complete error message but not part of a conversion of the error to a string. Conversion or errors to string removes
all of the information required to troubleshoot the problem. From you question I can assume that you didn't write the script or that you copied a script and edited it without any training in PowerShell.
The full error will tell you exactly what caused it to fail. Once you klnow what failed then you know thee source of the failure. I guarantee that it is not Windows 7 and not PowerShell. It is some external force. Have you noticed any Klingons
around. They are know to cause this kind of issue.
Anyway follow the above instructions and you will eventually rack down who changed what.
\_(ツ)_/
