trentfromrid
Member
- Messages
- 38
- Reaction score
- 3
I am in a predicament where I am trying to trim down a Windows 7 image, partially by removing Windows Update. The problem arises that one of the critical applications I need requires TLS 1.2 via PowerShell 3 (or newer) and .NET 4.5 (or newer). Windows 7 comes with PowerShell 2 by default, and upgrading to version 3 or newer requires a Windows Management Framework MSU file to install, which requires you to have the necessary .NET version installed first.
So, this is order in which the events would have to take place:
1. .NET 4.5 (or newer) install during Post Setup
2. Reboot
3. Wait for first logon
4. Upgrade PowerShell to version 3 (or newer) by installing Windows Management Framework 3 (or newer) by running its MSU file
5. Reboot
There's two problems.
1. You cannot integrate the MSU file via NTLite because it requires .NET 4.X to be installed first
2. You cannot manually install the MSU post Windows install without the Windows Update component
Basically, this sort of problem would make it impossible for me to use Windows 7, and force me to redo all of my work on a Windows 10 image instead due to Windows 10 coming with PowerShell 5 by default and therefore supporting TLS 1.2. I know that Windows 7 is already well past end of life, but I will not have the time to transition over to a Windows 10 equivalent of my project for some time due to life priorities, and being able to resolve this issue on Windows 7 would give me the time I need.
Is there a workaround for this currently? nuhi
So, this is order in which the events would have to take place:
1. .NET 4.5 (or newer) install during Post Setup
2. Reboot
3. Wait for first logon
4. Upgrade PowerShell to version 3 (or newer) by installing Windows Management Framework 3 (or newer) by running its MSU file
5. Reboot
There's two problems.
1. You cannot integrate the MSU file via NTLite because it requires .NET 4.X to be installed first
2. You cannot manually install the MSU post Windows install without the Windows Update component
Basically, this sort of problem would make it impossible for me to use Windows 7, and force me to redo all of my work on a Windows 10 image instead due to Windows 10 coming with PowerShell 5 by default and therefore supporting TLS 1.2. I know that Windows 7 is already well past end of life, but I will not have the time to transition over to a Windows 10 equivalent of my project for some time due to life priorities, and being able to resolve this issue on Windows 7 would give me the time I need.
Is there a workaround for this currently? nuhi