I’m sorry Seyton that this happened. It was not something we knew would happen until we upgraded the engine. For the last week or so we have been looking into solutions to resolve this as soon as we can. It is very important to us to support Windows 7/8. We do not plan to forget or abandon you supporters.
You do not have to upgrade to Windows 10, but it does mean you will have to wait until we implement the fix to correct this. As a team, we know how important it is to support Windows 7/8.
Update 7/7: I am currently looking into offering refunds to those affected by this issue and are unwilling to wait for a fix. We would like grant refunds, but we need to go through the appropriate channels to do so since this is a new issue for us.
Please standby as I see this through and will update this thread with more information once I have it.
Update 7/8: We have found a possible solution for compatibility, but it is not confirmed if it is working yet. We also have contacted Epic about supporting refunds for those who would prefer not to wait for a fix.
Update 7/10: Still waiting on Epic for more information on how to support refunds as well as a release window for the compatibility fix which should be included in their next engine update. They are on midsummer break, so they will not be responding until Monday. Sorry for the delay.
Update 7/10 Part 2: A community member has suggested a solution that is looking very promising and could be implemented internally without the help of Epic. This could expedite the solution if this works out. More news Monday.
Update 7/13: We have implemented our first attempt to fix compatibility for Windows 7. It has passed our internal tests and we are ready to deploy it to the Main branch any time now. We would love feedback from you all to see if this solves the problem or not. Thank you for your patience thus far.