x Want to participate? Join the group to interact
Options
  • State Suggested Answer
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 21936 views
  • Users 0 members are here
Browse Forums
Announcements
151
topics
113
replies
General Discussion
5k
topics
13k
replies
Payroll & Tax
633
topics
894
replies
Reporting and Analytics
574
topics
1k
replies
Service Alerts
1
topics
0
replies
Software Development Kit (SDK)
436
topics
674
replies
Year End
83
topics
128
replies
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?

  • 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.

  • 0 in reply to Best Business Strategies

    NOT so.  I could not run my payroll tax form updates (ie,W2) for this year (2018) while in compatibility view.  Had to take it out, run the updates and put it back in.  It still crashes occasionally while in CW windows 8 when posting cash receipts.  I've found if there are very many lines of entry like maybe a half dozen or so, well poof, it's gone.  What a giant waste of time.  This is a huge freaking problem.  I've been a Peachtree/Sage customer for a good 15-20 years and given all my client complaints I am seriously considering QB.  I've never heard anyone complain about it, but I get more and more complaints about cost  with Sage amongst my clients and problems like this only compound all of our frustrations. If it worked great, then cost would not be an issue.  

  • 0 in reply to Tom1410

    Tom, Did you update to2018.1   Are you running  your program as an administrator?   You may wish to check the box to DPI scaling also.   ( Right click Icon, go to proporities> Compatibility Mode. 

    I have a lot of customers and this has worked for all of them so far.

    Shirley Byard, Owner -  Best BusinessStrategies.com

  • FormerMember
    0 FormerMember in reply to Tom1410

    Tom1410....

    I doubt you care, but this is not a Sage issue, it's clearly a Windows 10 issue.   Creator update has been a nuisance among all my clients.  Heck, Windows 10 minor updates in general cause issues all over the place.  Whether it's printers being lost, software not working, and changing network settings, it's always something with Windows 10.   Now with this feature Creator update, it has caused many computers to be no longer compatible with 10 at all.   Network card drives, motherboard drivers...  the device manager ends up with exclamation marks all over the place where before they all functioned fine.   You cannot expect Sage to be able to keep up perfectly with the number of screw ups that Microsoft is causing on a daily basis.

    As for Quickbooks, I deal with it as well.   It has also been a nightmare with Windows 10 because of all the same reasons mentioned above.

    Simply put...   Windows 10 is a disaster and will continue to be a disaster for a long time!

*Community Hub is the new name for Sage City