Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

.NET Framework upgrade and impact on Windows XP/Vista users #3201

Closed
Jaex opened this issue Mar 19, 2018 · 10 comments
Closed

.NET Framework upgrade and impact on Windows XP/Vista users #3201

Jaex opened this issue Mar 19, 2018 · 10 comments
Labels

Comments

@Jaex
Copy link
Member

@Jaex Jaex commented Mar 19, 2018

We were using .NET Framework 4.0 for a long time because it was the last .NET Framework version which supports Windows XP. Because .NET Framework 4.0 does not support TLS 1.2 we are now forced to upgrade the .NET Framework version. Recently GitHub removed support for weak cryptographic standards and because of this ShareX auto updater which relies on the GitHub API to check for updates now only works if you have .NET Framework 4.5 or higher installed. In future, more and more services will drop support for weak cryptographic standards and make TLS 1.2 necessary. Because of this we have no choice but to upgrade the .NET Framework. Unfortunately because of this, ShareX 12.0.0 will be the last update for Windows XP and Windows Vista users. Upgrade of .NET Framework is also going to give us more technologies to work with and it is better for the security of users. We wanted to upgrade our .NET Framework version for a long time and it has now become necessary to do so. Windows XP and Vista users can still use ShareX 12.0.0 but they won't receive auto updates anymore. Unfortunately in the Steam build we are unable to stop Windows XP and Vista users from receiving updates so you must use desktop version if you are a Windows XP or Vista user. If you are using Windows 7 or higher but don't have .NET Framework 4.5 or higher installed, you can download the latest ShareX setup manually and setup will automatically download necessary .NET Framework and install it.

@Jaex Jaex added the Announcement label Mar 19, 2018
@ShereeBrown
Copy link

@ShereeBrown ShereeBrown commented Mar 23, 2018

it can't opened and launch after update,i need help,i used windows 10

@mokeev1995
Copy link

@mokeev1995 mokeev1995 commented Mar 23, 2018

@Jaex Windows Vista has .Net Framework 4.5 as i know. Am I wrong? What will happen with Windows Vista users?

@TheLucky007
Copy link

@TheLucky007 TheLucky007 commented Mar 23, 2018

@mokeev1995 in the changelog they're moving over to .NET Framework 4.6.2 which Windows Vista does not support (Vista goes up to 4.6); likewise Windows 8 (not 8.1 which can go up to 4.7.1) goes up to 4.6.1 so in other words Windows XP, Vista and 8 will no longer be supported. And as what Jaex said ShareX 12.0.0 will be the last version for the aforementioned OS's/users who are on those OS's.

Hope that answers your question.

@mokeev1995
Copy link

@mokeev1995 mokeev1995 commented Mar 23, 2018

@TheLucky007 oh, yeah, thanks. I didn't pay attention to the fact that they switched to 4.6.1.

@thejustsoul
Copy link

@thejustsoul thejustsoul commented Apr 4, 2018

This is bad news, now I will not be able to carry on the ShareX flash drive and run on different computers current portable version. Will have to remain on version of 12.0.0. Because does not work everywhere (on other computers) have a set of monstrous .NET Framework 4.6.2+ It's sad..

Maybe there's a way to make the .NET Framework portable and glue it to the portable version of ShareX? To work all "out of the box" and without installation in the system..

@BHare1985
Copy link

@BHare1985 BHare1985 commented Apr 5, 2018

Dropping windows 7/8 support is too aggressive. Please just move to framework 4.6 and not 4.6.2, or even 4.5.2 which is perfectly stable and safe.

Windows 10 only accounts for ~33% of the market, thats 66% of your client-base you are losing by forcing them to upgrade a monster net framework upgrade (which by the way doesn't work automatically for me)

@campbeb
Copy link
Contributor

@campbeb campbeb commented Apr 5, 2018

@BHare1985 Support for Windows 7 isn't dropped. Support for Windows 8 line isn't dropped, just for 8.0. The upgrade from 8.0 to 8.1 is free (https://support.microsoft.com/en-us/help/15288/windows-8-update-to-windows-8-1)

@Jaex Jaex closed this Apr 14, 2018
@csdsinc
Copy link

@csdsinc csdsinc commented Apr 18, 2018

My "screen recording" function always crashes. I used Windows 10 Pro and ShareX 12.1.1. Can anyone help?

@Tragen
Copy link

@Tragen Tragen commented Jun 10, 2018

In .Net 4.5 you can use TLS 1.2 with this line of code.
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
in .Net 4.0 you have to use
ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072; //TLS 1.2

@ghost

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
9 participants