FormerMember

Sage 50 2017 Premium Accounting crashes after Windows 10 V1709 (KB4041994) upgrade?

SUGGESTED
Posted By FormerMember

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?

Parents
  • 0

    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.

Reply
  • 0

    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.

Children
  • 0 in reply to John Parr

    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 

  • 0 in reply to Nedra

    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.

  • 0 in reply to Best Business Strategies

    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

  • 0 in reply to Nedra

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

    www.amazon.com/.../

  • 0 in reply to Best Business Strategies
    • I AM THE IT GUY!
    • I'm a one person home based business & have been for over 20 years...
    • this is a new computer!
  • 0 in reply to Nedra

    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

  • 0 in reply to John Parr
    I don't use any of these: What are the add-on products that stop working after the obsolescence date?
    1. Program updates
    2. Tax updates
    3. Tax form updates
    4. Direct Deposit
    5. Sync with Managed Payroll
    6. Credit card processing

     

    I stopped liking Sage back in 2013....but since ​losing support for add-on products I don't use anyway, it wasn't a deal breaker for me to migrate my business to another software program.
    Over the years (long before Peachtree became Sage) I upgraded the software every couple of years & was happy with that. Then Sage came along, prices increased & the technology with the software did not keep up with the times, or similar programs who have run past Sage in what they provide consumers. Since I don't use the add-on's upgrading every year was not important me & was not necessary. The software worked fine, I rarely had problems that needed tech support & I probably could have gotten away with not even updating every 2 years.
     
    Once Sage started the subscription plan I thought seriously about switching to other software but I couldn't justify the work & money involved in trying to migrate to another software program so I have endured figuring I'm going to retire one of these days & I won't need to deal with Sage anymore.​
    That day seems to be getting closer & closer as software bugs/problems with Sage, etc keep increasing...especially each time Windows comes out with an update. With every update I seem to spend hours on the phone with Sage & Microsoft & It seems that there is always a lot of finger pointing as to the source of the problem.
     
    Yes Windows updates cause problems with other software but with billions of people using Windows & perhaps thousands, maybe millions using Sage I think Sage needs to be a bit faster & more proactive about keeping up with Windows updates to ensure users aren't left hanging while Sage figures out how to fix the problems.
    Consumer's can't be left hanging with software that doesn't work after a Windows update...even days is unacceptable but weeks or longer is cause for firing!
    It's not Microsoft's responsibility to ensure that their updates are compatible with Sage but it is Sage's responsibility to ensure it is compatible with Windows & the updates that Microsoft puts out.
  • 0 in reply to John Parr

    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.

  • 0 in reply to rseiler

    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.

  • 0 in reply to John Parr

    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.