New Minimum Windows OS requirement for 7.10
Due to a lack of support for .NET 4.7 on certain versions of Windows, as of today Logos 7.10 will only be supported on the following or later versions:
- Windows 7 SP1
- Windows 8.1
- Windows 10 Anniversary Update (Windows 10 Version 1607 or later)
If you are not running one of the supported versions of Windows, then you will need to either update your Operating System or return to 7.9 on the stable branch using the instructions listed in this post: http://community.logos.com/forums/t/52967.aspx
To determine which version of Windows you are running see this support article:
https://support.microsoft.com/en-us/help/13443/windows-which-operating-system
Comments
-
Can we be clear about this:
Windows 10 Anniversary Update = Windows 10 version 1607 build 14393 or later (check Settings > System > About for your version)
Returning to v7.9 means completely uninstalling v7.10 as per the 3rd paragraph of the post.
Dave
===Windows 11 & Android 13
0 -
Philana R. Crouch said:
Due to a lack of support for .NET 4.7 on certain versions of Windows, as of today Logos 7.10 will only be supported on the following or later versions:
- Windows 7 SP1
- Windows 8.1
- Windows 10 Anniversary Update (Windows 10 Version 1607 or later)
I do run Windows 10 Version 1607 and the current Logos 7.10 Beta 2 build 7.10.0.0013 - however it does not seem that the Logos installer updated me to .NET 4.7:
Here's the setup logfile: 2654.LogosSetup.zip - I see no issues in it.
Should I install .NET 4.7 manually?
Have joy in the Lord!
0 -
Your install log is reporting you do have Net Framework 4.7 (460805)
2017-09-19T20:02:21Z 0x3334 Info CheckRegistry Value in registry: '460805', compare result 7.
Dave's suggestion of just running the 4.7 Net Framework Web Installer is the easiest way to double check you have it installed correctly, but the Logos installer takes care of it for you.
You can also check with this Power Shell script, adapted from What is Your .NET Framework Version? Use PowerShell to Check
0 -
Randy W. Sims said:
Your install log is reporting you do have Net Framework 4.7 (460805)
2017-09-19T20:02:21Z 0x3334 Info CheckRegistry Value in registry: '460805', compare result 7.
Dave's suggestion of just running the 4.7 Net Framework Web Installer is the easiest way to double check you have it installed correctly, but the Logos installer takes care of it for you.
Ok, the installer refused to work, confirming I have .NET 4.7 already installed (even if my Win 10 seems to believe otherwise). Oh well.
Have joy in the Lord!
0 -
This powershell script didn't work for me either. I tried it just because, as you can see by the picture installing 4.7 fails because its says 4.7 is already installed, and the script says 4.5 or later is not installed. This is Windows 10 version 1709 Build 16291.0.
0 -
I would not expect that powershell script to work correctly to detect any version of .NET later than 4.6.2.
Andrew Batishko | Logos software developer
0 -
I would not expect that powershell script to work correctly to detect any version of .NET later than 4.6.2.
I suspect you were looking at the script on the website? The script I attached checks for the 4.7 versions as listed in Microsoft's Docs.
Don Awalt said:This powershell script didn't work for me either. I tried it just because, as you can see by the picture installing 4.7 fails because its says 4.7 is already installed, and the script says 4.5 or later is not installed. This is Windows 10 version 1709 Build 16291.0.
The script only checks for currently released versions of the NET Framework. You're running a preview release with a later version.
The code is not very robust code. I wasn't trying to write a script; just copied the code from that site and added the two new versions listed in the Microsoft Documentation. Looking at the documentation further, the script should have done a greater-than-or-equal-to test instead of checking specific versions to remain robust against future versions (as well as some error detection). But again, I wasn't trying to spend time writing a script. I took 15-20 mins to copy his code, append the new versions, and test it on my system before posting. It seemed it might be a useful script, but I should have left it off.
0 -
Randy W. Sims said:
I would not expect that powershell script to work correctly to detect any version of .NET later than 4.6.2.
I suspect you were looking at the script on the website? The script I attached checks for the 4.7 versions as listed in Microsoft's Docs.
You are correct. I missed that.
Andrew Batishko | Logos software developer
0
