The issue has been identified. The change in the Creators Update affects how Windows 10 treats unmanaged .net code. At the time I was told this, about a week after the release of the V1709 update, development was still early in the investigation phase. At the time, it was not clear whether the core issue was a defect in our code, or whether the change in the creators update corrected a defect in Windows for which we were previously working around. At the time, it was also clear from the investigation that the fix would require extensive work.

It is a top priority. It is the current hope to include it in 2018.2, but because the fix requires so much extensive work, it is still too early to say that it definitely will be.

John, are you a Sage employee???

I have 2017 version & I don't feel like I & other 2017 users should have to pay to upgrade to 2018 just to get this problem fixed. It's a Sage & Windows problem & this is something that Sage needs to incorporate in both versions. If Sage was compatible with Mac's we wouldn't be having this discussion 

You can use Parallels and run your software on a Mac.   Sage has given you a fix to run the 2017 on Windows 10. If that does not work, you do have an option to go back to Windows 7.  

I believe the issue is with Microsoft, not Sage.

What is the fix to run the 2017 on Windows 10? Are you referring to running Sage in compatibility mode?

How do I go back to Windows 7?

I do agree that it is a Microsoft problem but there must have been a compatibility issue with something in Sage

What is the fix to run the 2017 on Windows 10? Are you referring to running Sage in compatibility mode?

How do I go back to Windows 7?

I do agree that it is a Microsoft problem but there must have been a compatibility issue with something in Sage

Get a new computer or talk to your IT company about switching over.   Windows 7 is still for sale.

www.amazon.com/.../

• I AM THE IT GUY!
• I'm a one person home based business & have been for over 20 years...
• this is a new computer!