Sage 50 Accounting Windows 11

[Desiderato Merriwether]

MySage 50 2016 Complete Accounting (built 23.2.00.0184) has been working well. I recently updated my Windows 10 V1709 KB4041994 and all of sudden Sage 50 keep on crashing specifically when I tried to create NEW inventory item. It does not allow me to create new inventory item.

I had a similar issue - the program crashing - but my experience was on attempting to enter a new sales invoice or a new vendor bill (I do not use inventory). I did all integrity checks and data verification, all with no issues found. I was able to get Sage 50 back to working only after uninstalling the 1709 update to the previous version of Windows 10.

Crashing on tasks we have experienced with the install of the (KB4041994) Windows update, but not trying to save a new maintenance record (yet). However, that symptom has been reported on failed Windows updates in the past, so it is very likely related, I agree.

I can confirm the same issues. It is becoming more widespread now, Sage 50 accounting 2016 will crash randomly anywhere with message that "windows has to close the application and will notify if a solution is found".

My Sage 2016 complete accounting is no longer supported product and I was willing to upgrade to new version 2017 which is still supported. After reading this message, I now know that the issue is also happening with 2017.

My temporary fix right now is running Sage 50 2016 on my old laptop running old i5 which is not affected by the latest windows update as SINGLE user. So far it has been stable and not crashing randomly.

Thank you for the solution. I set up SAGE to run in compatibility mode for Windows 8 last night. I tested sage for all the modules and the transactions which usually crashed the system and it has been stable so far. Thanks again for the solution.

2. What does running Sage on "Compatibility mode for Windows 8" mean?. Will it affect how the database is structured etc, to a point that the database is no longer compatible with Windows 10 when the solution is provided by Sage?

1. I would say it will be highly unlikely that a patch would be provided for 2016, considering it is already obsolete. Historically, I think we have only patched an obsolete product once in my 20 years here, and it was only because it was a "dead in the water" situation that prevented clients from upgrading. Since this situation has a workaround, the chances of a patch being provided for 2016 is closer to none than slim. Never say never, but I definitely would count on there not being one forthcoming.

2. Something in the V1709 Update made a change in the way Windows handles unmanaged .net code, specifically in the Windows 10 settings. This is why running it in compatibility mode works. It is safe and has no effect on your data or database.

I am told the fix for this will not be small or simple, so there won't be a fix forthcoming until at least 2018.2. In the meantime, running in compatibility mode for Windows 8 will get around the problem.

I am using Sage Line 50 Ver 11 (!) on Windows 7 64bit without any problems. I do not use the Sage PDF printer so do not know if that works. Sage only supported Ver 11 on Win XP, not Vista or Windows 7.

Looking at the Windows 7 Professional details, am I right in thinking one could reinstall it as a 32 Bit version (it's very hard to tell whether there is a 32 Bit version of Windows 7 Professional)?

3) I am reliably advised, that for a Desktop PC, there will not be any noticeable difference in performance between 32bit and 64bit. Where 64bit really comes into it's own is on laptop PC's where 64bit will be noticably faster.

I have just done a transfer from a Windows XP machine over to Windows 7 64. Sage Payroll seems OK, Job Costing version 8 seems ok, but Sage Line 50 accounts dosn't fully work. The issue I have just hit and have no work around for is saving bank rec's. Sage saves a PDF of the reconsiliation when it trys to do this I get an 'Out of Memory' error? But there is plenty of free memory. Just Spoken to Sage Technical support and he has admited they have no workaround for this, nor do they have a timescale on when this will be addressed. They are awaiting a new version of the Amyuni PDF printer which is 64 bit compatitable. From what technical support said the 32 bit version has only been released 3 weeks ago. It is very frustraiting as everything else worked without a problem. And I know of other software companys which use the Amyuni PDF driver and it works fine on Windows 7 64.

I am very suprised that such a large company carn't get this problemresolved . If anyone has got around this I would be very interestered in how they done it as my only option is to put in a 32 bit os.

So why are you considering 64-bit? Do you have a specific need for a 64-bit system? Most Windows software is stll 32-bit and (unless you're a major power user who will benefit from having more than 4GB of physical memory) you'll get no performance advantage from a 64-bit system when running 32-bit software.

"If you're trying to decide between 32-bit and 64-bit Office, you should ask yourself what your needs are. Are you an Excel power user working with huge amounts of data? Do you need to work with file sizes greater than 2GB? If so, then you would benefit from 64-bit Office being able to utilize more memory. If not, we're recommending 32-bit Office 2010 as the default installation on both 32-bit and 64-bit Windows mainly due to compatibility with existing 32-bit controls, add-ins, and VBA."

For reasons of future proofing in a nutshell. I recall reading somewhere that a large proportion (possibly a majority) of new Windows 7 systems sold are 64-bit. Computing is moving in that direction and I wouldn't be surprised if in 3 or 4 years time some software will be 64-bit only (my current laptop is over 7 years old now!)

Agreed that 4GB of physical memory is large, but Bill Gates thought 640kb of RAM was more than anyone could possibly use - so even the best people in the business get it wrong. It's good to give yourself some flexibility, just in case one day Sage's minimum installation requirements are 64 bit Windows with 8Gb of RAM.

Sage line 50 does not work with Office 2010 64 bit. Only have 64 bit because office 2010 32 bit has bits missing that are available in 64 bit. Bits only if having a volume license. You have to love the large corporations arrogance to small users

All you need to do once this is installed is choose print though sage and then go to you drop down menu and choose CutePDF and it will save you a PDF file of the print job. This will save you time and money and waiting for lazy assed companies doing their job correctly in the first place.

Because it is a touch screen it is like working on a white board , it is excellent for training and showing clients their accounts they just touch the info they want and it comes up. I have had it about six months. It is also used as a normal computer as well.

Version 2010 was not great on anything windows 7 but all the PDF and excel problems would appear to have been resolved in 2011-. I am also using it on a virtual machine windows 7 32bit on my macbook pro using VMware fusion as well as accounts production and ct and they seem to work well . I not tried the accounts production on the 64 bit yet , only because I have not had the need. My Sage cover has covered me on windows 7 64 bit. Software is getting larger and larger so if your getting a new machine go for the better GB . I got that Packard Bell 3GB 260GB Touch screen for 600. Their not really that expensive anymore, and that was out of Staples so I am sure you can get cheaper.

I found after upgrading to a new PC with Windows 7 that Sage Accounts 50 2009 wouldn't save any file as a PDF. When I bought the PC I gave no thought to whether it was 32 or 62 bit, just bought a PC with a spec that suited me.

I have run Sage Line 50 version 9.10, on XP, Vista, and Windows 7, in 32 bit on a 64 bit machine. I have no trouble at all but do not network the program. It runs on one machine at a time. Back ups are duplicated on each machine.

Sage 50 has been a well-classified and technically dedicated accounting software that has given space for all technically advanced tools and features. This technical advancement gives it an edge over other accounting software. However, your software may fail this accomplishment due to certain internal and external reasons. The sage 50 not open error/issues in the software can be due to the inculcation of external software, corrupt Windows registry after the update, malware/virus, or firewall/antivirus.

In the month of July 2018 a number of people ask why Sage 50 Not Working After Windows 10 Update, which is solved by experts with proper instruction. Also you can check directly here Latest Windows 10 Update release information .

It is imperative to keep your Windows up to date with the latest version launched by Microsoft. These updates comprise security patches, drive updates, and other important back-end applications. Once your window is up to date, it is good to have all your software up to date to match software and system requirements.

Also AccountsPro team after studying the case of more than a thousand customers posted most common causes why Sage 50 Not Starting on different situation, the Sage user can also find situations when Sage 50 Crashing while performing transactions.

Follow these steps as we are mentioning them or even consult with the Sage Chat Support team regarding your OS version. Failing to follow the steps may lead you to various other issues or errors.

Sage 50 accounting software may freeze after updating to Windows 11 due to various reasons such as minor errors, misconfigured settings, viruses, failed critical services, outdated versions, or not meeting the Windows 11 requirements. This issue can be frustrating, but fortunately, there are several methods to fix it.

3a8082e126