Results 1 to 4 of 4
2015-12-01, 20:34 #1
Heads up: Windows 10 / Quickbooks 2016
If you're a small business user about to switch to Windows 10, and you're a Quickbooks user, you might want to wait a while.
First, you can only use Quickbooks 2015 or 2016. 2014 and earlier versions are incompatible with Windows 10. As soon as you upgrade, plan on spending $200.00 for a new version of Quickbooks Pro 2016.
Second, there are major problems with Windows 10 and Quickbooks 2016. I've installed 2016 on three machines so far, two of my own and one belonging to a client. All three machines were recent, squeaky clean, and with a minimum of junk installed. Two are HP desktops and the other is an I7 Dell Inspiron. No problems during the Windows 10 upgrade process. Until I upgraded to Quickbooks Pro 2016.
My main business machine shut down and failed to boot several times Saturday morning. Intuit tech support was no help at all, beyond admonishing me not to attempt to fix it myself, and would only refer me to third party paid support. $275.00 and seven hours later, I'm on a first name basis with a guy named Sanjay in New Delhi. He was eventually able to get it running, but my Windows error logs look like a dog's breakfast.
A second machine, which I use for my personal business, didn't crash and burn, but the error logs are showing the same type of errors, with corruption in .NET 4.0 and task scheduler. I'm holding my breath on this one.
As I write this, I'm in the process of restoring Windows 7 on my client's machine. Same symptoms, including startup errors, registry corruption, and a bloody startup process. Fortunately, in his case, I had upgraded his hard disk for more space just before I did the Windows 10 Magical Mystery Tour, and I had left his old hard drive inside his machine, unconnected...just in case today happened. Best move I made that day.
I don't honestly know if the culprit is Windows 10, the Build 1511 "update", or Quickbooks Pro 2016. What I can tell you is my batting average with this combination is .000. Three tries, three corrupt, unstable machines.
Once I get my client back in business, I'm going back to Windows 7 on my own machines, battered and bitter.
Last edited by bobdog; 2015-12-01 at 20:41.
2015-12-02, 15:13 #2
Sorry to here of your troubles. Did you not have an image of the computers before 'upgrading' to W10.
Just because you don't know where you are going doesn't mean any road will get you there.
2015-12-02, 17:06 #3
I had upgraded about a month and a half before I installed Quickbooks and Build 1511, so rolling back to Win 7 is not an option.
My client's machine had Windows 7 issues before I upgraded to Windows 10, so I put in a new hard drive and did a clean install of Win7, did the updates, and then upgraded. In retrospect, it was the right thing to do. Did have user files backed up, which was all I needed. Slow, but he's starting off clean.
My own machines have backups, but not an image backup. NBD. If I have to go back to Win7, I'll do a clean start on both of them.
The point of my post was to give a heads up to people thinking about upgrading. If they're Quickbooks users, they should wait a while.
2015-12-03, 08:04 #4
But wait! There's MORE!
What I got were 210 Adminstrative alerts in the Windows error log, including a fatal error that crashed the machine. Most related to the R3 update, and most were improper registry permissions.
So the problem isn't Windows 10 after all. The problem is Quickbooks 2016 and an inadequately tested major update. Trouble is, if you're running Windows 10, you HAVE to "upgrade" to either Quickbooks 2015 or 2016.
If you're a Quickbooks user, you've been warned.