My Sage 50 Premium Accounting crashes after Windows 10 V1709 upgrade. I can (and am) running Sage 50 in Compatibility Mode...which does work. However, it makes Sage run VERY slowly. When and how will this be fixed in Sage 50?
My Sage 50 Premium Accounting crashes after Windows 10 V1709 upgrade. I can (and am) running Sage 50 in Compatibility Mode...which does work. However, it makes Sage run VERY slowly. When and how will this be fixed in Sage 50?
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…
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…
I did put it in compatibility mode & that is all I had to do to get it to work. I'm really hoping this issue is resolved without requiring Sage users to have to upgrade from their current version....especially…
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.
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
Get a new computer or talk to your IT company about switching over. Windows 7 is still for sale.
I am a Sage employee, yes. If you're on an active yearly plan with us, that includes all software upgrades within the year of your plan, so if you're on a current plan, you've already paid for the 2018 program. Sage moved to an ongoing development plan starting with the 2013 release, where we only support the current two releases of the software.
The 2017 release is already a year and a half old. The 2017.0, 2017.1, and 2017.1.1 releases will be obsolete on 12/1, and 2017.2 will be obsolete on 2/28, so there will be no fixes issued for 2017.
More info: FAQ - Sage 50 US Obsolescence
Point of curiosity: Why isn't this a problem for Sage 50 2017/18 CA? Is it not also written with unmanaged .Net? I also haven't seen this problem with any other program that I run or even know of, so it's quite curious indeed.
To my knowledge, it is not, but that would be better posed under the Canadian forums if you really want to know. Even though the branding is Sage, the Sage 50 Canadian version and the US versions were completely separate software companies acquired by the Sage Group PLC years ago. They were Simply Accounting and Peachtree Accounting, respectively, and were both rebranded as Sage 50 sometime in 2012. Even though both companies have been under the Sage umbrella for years, largely development was still independent, so it's not so curious that the codebases are still completely different.
Right, that makes perfect sense. I had forgotten about the different lineages. Maybe one day they'll be united, but definitely not quite yet. It's a bit unlucky though even one of them has the problem (the CA version definitely doesn't), since I'm pretty plugged into program incompatibilities with Windows and haven't seen this kind of issue in quite a while.
*Community Hub is the new name for Sage City