QuickBooks 2016 R7 Released

Written by Charlie Russell

Intuit has released the QuickBooks 2016 R7 update for the U.S. version of QuickBooks. This is available as a manual update from the Intuit support website. I’m not sure when it will go out as an automatic update, but it should be soon if it isn’t out already.

QuickBooks 2016 R7 ReleasedI haven’t had a chance to test this yet. You may want to wait a week to see if there is any great outpouring of grief from early adopters (which I don’t expect, but I’m cautious). However, looking at the list, assuming everything works fine, if you are using QuickBooks 2016 then you want to install this update. There are a lot of important bug fixes and changes here!

If you are an add-on software developer, or you use an add-on program, you will have to update some information before the add-on can access QuickBooks data.

Charlie Russell will be presenting the session, Recent Developments in QuickBooks and Looking Ahead, at Accountex 2016.

Security Updates

There are some big changes here. Some people are going to be annoyed by these changes, but if it makes things more secure for you, all the better. Note that these updates only affect the Windows versions of QuickBooks desktop. This doesn’t apply to QuickBooks for Mac.

Credit Card Protection

If you have enabled the “Credit Card Protection” feature, or if your file contains sensitive data (credit card data, “personally identifiable information”), then every user must have a password. Up until now some of your users may not have had a password, now they will be required to.

All users who can view full credit card data, when “Credit Card Protection” is enabled, will have to change their password every 90 days. No exceptions. And this has to be a “strong” password.

QuickBooks SDK Add-On Programs

If you are using an add-on program that has “background access” (that is, you have given it permission to log in to your QuickBooks data even if the QB file isn’t currently open) then users will have to re-enter their login credentials. Here’s how I understand it will work (I’m still testing this).

  • The Admin user will need to log in to each QuickBooks file and then run the add-on program, to re-establish access permissions.
  • In addition, every user will have to log in to enable the add-on program.
  • If there is “personally identifiable information” in the QuickBooks file then keep in mind that every user will have to log in with a password. If there is no password for that user then the add-on won’t be able to connect for that user.

Windows 10 and Microsoft Office 2016

Windows 10 and Microsoft Office 2016 are now officially supported by QuickBooks 2016. I’ve been running QuickBooks 2016 on Windows 10 and Microsoft Office 2016 for some time now, without problems, but it is nice to see Intuit officially support them.

QuickBooks 2016 R7 Bug Fixes

  • Permissions: Always hate to see problems with permissions!
    • Corrects an issue that allowed users with no access or limited access to be able to change Company General Preferences.
    • Corrects problems with the Batch Enter Transactions feature that let you enter transactions into a closed period, as well as getting around user permission restrictions.
  • QuickBooks Crashes: Always love to see these fixed!
    • Fixes an issue that caused QuickBooks to crash when printing a transaction after that transaction had been edited.
    • Fixes a problem that caused QuickBooks to crash when exporting a large report to Excel.
  • Fixes an issue that prevented accountants from unlocking the Accountant Toolbox.
  • Fixes an issue in advanced Excel import that allowed changing the type of an existing item from inventory part to non-inventory part, which would cause the balance sheet to go out of balance.
  • Fixes the scheduled backup feature that prevented the backup file from being created.
  • Inventory/Items:
    • Fixes an issue that caused a warning message to display incorrectly after changing the “quantity to build” for an assembly item.
    • You can now save transactions that contain items that had previously been converted from an inventory item, non-inventory item, or purchased assembly item to any other item type.
    • Corrects a problem that caused a warning message to display incorrectly after you added a memo to an existing assembly item.
    • The Inventory Valuation Summary and Inventory Stock Status by Item reports will now accommodate long item descriptions by showing them partially.
  • The memorized transaction list will no longer show as blank when you filter for frequency.
  • The Auto Data Recovery (ADR) and Desktop Search features have been restored to full functionality. These had been disabled for maintenance on May 23, 2016.
  • This release fixes an issue where odd dates would be shown in the Make Deposits window after adding a payment in the merchant services deposit.
  • Fixes an issue that caused sales tax amounts from showing as “unclassified” on reports based on Class.
  • Shipping Manager: An issue is fixed that caused small, medium, and large flat rate options to not show up in the dropdown packaging options.

About the author

Charlie Russell

Charlie Russell has been involved with the small business software industry since the mid 70's, and remembers releasing his first commercial accounting software product when you had an 8-bit microcomputer with one 8 inch floppy disk drive. He has a special interest in inventory and manufacturing software for small businesses. Charlie is a Certified Advanced QuickBooks ProAdvisor with additional certifications for QuickBooks Online and QuickBooks Enterprise, as well as being a Xero Certified Partner. Charlie started blogging about QuickBooks in 2008 (Practical QuickBooks) and has been writing for the Accountex Report (formerly the Sleeter Report) since 2011. He retired from accounting and QuickBooks activities in early 2018.

Visit his CCRSoftware web site for information about his QuickBooks add-on products. He is also the author of the California Wildflower Hikes blog.


    • 1) Is it possible to receive emails when new comments are added without posting a comment?
      2) We are a 2 person office with one license for 2016 Premier. Occasionally the boss asks me to close QB so he can peek at numbers, enter a transaction or two, then I can get back in. I have installed the R7 update but I’m not sure if he has. I’m curious what might happen if he neglects it?

      • Kimbre, to get notifications of further comments you have to leave a comment yourself, as you did here. You can always leave a “great article!” comment or something of that sort.

        As for the other issue, I’ve not tested that, but either nothing will happen or (more likely) he’ll get a notice that the file has been updated and he has to update. In any case, no damage to the file will occur.

  • Due to the huge difficulty (previously discussed) in upgrading the company file for those upgrades/updates that require it, in the Enterprise environment we are finding it best to do updates at most once a year.

    • It shouldn’t be difficult to upgrade a file within one “year” of QuickBooks. If you have an earlier 2016 release then moving to a later 2016 release isn’t that complicated. Waiting once a year for that kind of upgrade isn’t highly recommended.

      If you are talking about moving from one year of product to the next, that might make more sense. Then it depends on what new features are available, and if they have any impact on your business.

  • Charlie, I installed the R7 Release into my QB Premier 2016 this past weekend, which resulted in a big problem for me. I am a very basic user, only one PC, no add-ons, relatively unexciting. Was using QB 2013 Premier until March 2016 when I updated to 2016. No issues, use QB almost daily for my small business, no credit card processing, no automated payments, just recording daily business transactions, etc.
    After the R7 release was installed, it advised that my company file would be updated. After this was performed, the Complex Password screen appeared indicating that I would need to update my password according to new rules, and would need to select a password question and answer. This was new to me, but added security seemed like a good idea, so I completed the form with the old and new passwords. I hit enter and for about 2 seconds the QB home screen appeared, then it disappeared, and then the Complex Password screen appeared. I re-entered all of the information, but repeated the same process and did not accept my entries, without any explanation or error codes. My biggest problem is that this has locked me out of opening my company file. I am unable to bypass the Open File process by using my old password to open the company file.
    I am now in the process of uninstalling and re-installing QB and will not allow R7 to be installed.

    • The password is in the Company File not in the QB install, so re-install may not be a fix. At this point your backups are precious.

    • I’ve converted several company files in test situations up to R7 (from R5, usually) without any problems. I have a feeling that this may be due to an issue in your particular file, although that is hard to say without having hands on the file. When you restore to an older version, I would recommend running a file rebuild and viewing the QBWIN.log file for errors.

    • Bruce, from what I understand, a few people are reporting this issue (complex password screen keeps coming back), and it is most likely due to some file corruption issues in your file prior to installing the update. You may be contacted by someone from Intuit about this.

      • No time nor need to get on the hamster wheel with Intuit people. They have no clue either. This has happened on my versions – multiple company files as well as 3 clients company files. AND it’s happened in 2015 as well to my own company file for my business and 2015 for 2 of those 3 clients. It’s all so ridiculous to state that this is “for security” C’mon – no CC’s are stored – all of the files are on my PC or my clients PC – it’s not needed. Yet forced. Intuit it seems needs to address bigger issues and stop trying to “fix” issues that weren’t an issue to start with. I have far better things to do then to now have to remember more flipping passwords AND change them every 90 days too. Was not a happy camper in the tiniest bit when this happened to my own company file in 2015 but then to start getting panicked phone calls and emails from clients asking WTH?

        • The thing that I’m investigating is what conditions require a complex password and 90 day changes. Some cases it asks for a password but doesn’t REQUIRE a complex one. Still looking into this.

        • I’m with Sue – being forced into creating passwords when not needed. UUGGHH! Intuit needs to change this – pronto!!

          • I agree with you. I purchased this product and I should be able to use it as I see fit. There should be an option or preference to not use the useless “security.” Shame on Intuit!!!

  • Pete, my suspicion is that the problem has nothing to do with the password itself but rather an error in process that was caused by the installation of R7. I have re-installed QB, which was purchased in Apr 2016 and already included the R5 release, and opened a backup file from last week prior to the R7 installation. All is working fine. For now, I have turned off Automatic updates and will monitor future releases.
    I should note that several people have posted on the Intuit Community website the same or similar experiences after the R7 installation.

    • I am afraid it is very difficult to upgrade in typical Enterprise situation. I’ve listed reasons in another post. Add that the Owner/CFO needs to get dragged into the job for their Admin password. Half day down time is kind of a big deal when you have accounting people sitting around, POS not working, etc., not to mention the technician’s (lucky me) billable hours.

      I prefer to keep all software fully up to date, but agree with our customers that it is not worth it, considering the cost, and prior update “issues” (getting better this year?).

      The greatest concern is external security. But in Enterprise, Intuit’s coding is not considered a source of security versus:
      Network firewall and associated services
      Server (Domain) security
      User policy and training
      Malware protections (third party Enterprise level)
      Physical security, etc.

      • Woops, I meant this as a reply to Charlie above.

        Bruce: Well done. Agree with Charlie to check your company file. Agree with you to not rush into doing update. Keep your general security tight (e.g., a Real firewall).

        Backups save the day again!

      • Pete, I don’t know what you would consider to be a “typical Enterprise situation”, but all I can say is that:
        -If you are moving within the year, such as R5 to R7, the interruption can be minimal. It does depend on the size of your file, but it doesn’t have to be complicated. It CAN be, but not always. In any case, I would do this in the off hours just in case a problem occurs, and to minimize any interruptions.
        -If you are moving from one year to the next, such as V15 to V16, it is more likely to be inconvenient, but again not always. Depends on the number of users, size of file, features used. Again, I would do it in off hours, but I’ve had Enterprise conversions that take less than an hour of time

        Yes, in some situations, it can be a major chore. But you can’t make a totally blanket statement that it is always a problem.

        As far as security, certainly all of the kinds of things that you are talking about are very, very important. All too often some or all of these issues aren’t taken into consideration, I’m sad to say. But I’ll point out that there are considerations in “security” that go beyond what you list, and that is part of what is involved here. This is where you often see the differences between a technical advisor and an accounting advisor (I’ve worn both hats myself over the years). The issues here relate to PCI compliance, which IS a “security” issue. This release is an important part of Intuit’s approach to PCI compliance. This is something that too many businesses aren’t paying attention to, and in many ways it is just as important as the other issues you list (depending on the business).

        • 5 to 15 installed workstations and a (real) server is my example of typical for QB Enterprise. In my testing setup I can upgrade in a lot less than an hour plus reboot time but the real world is different. I wish I could do after hours but am only able to pull that off in tiny businesses (& not charging overtime). Restart alone (as specified in the Intuit procedure) of Server 2012 Essentials (taking precautions to prevent something going terribly wrong–I am not paid to take chances) takes half an hour, more if there are RAID controllers or several lurking Windows updates.

          Admittedly there are some things that take IT longer to do than a small timer doing the job themselves (assuming everything goes well). IT has the obligation to ensure all is stable before leaving, so that they don’t have to be called back or the users get stuck with problems.

          I haven’t seen a skilled PCI compliance audit finding yet that wasn’t solved with a minor setting of the firewall or server, regardless of what version of QB was running. However, I am lucky that none of our Enterprise customers use Intiut’s merchant (credit card) service.

          • Every installation has a different situation, every technician has different parameters. In “real” server environments I don’t always have long drawn out updates when doing an R level update. “it depends”, sometimes can be simple. Restarts aren’t always needed. Off hours? Well, that is your particular situation, doesn’t apply to everyone.

            PCI compliance, well, as you say, you have a situation that isn’t universal.

          • Server 2012 Essentials is taking half an hour for reeboot? I have it running at a branch office on a lower end LenovoTS140 with and i3 and 8GB or RAM, with QBE 15 installed, and I can reboot the whole thing in under 5 minutes.

            At our main office I have a Proliant with a Xeon E3-1240 and 8GB of RAM, with QBE 15 installed, both database manager and program. I can reboot that one in less than 8 minutes, and it’s the slowest one I have.

            I’ve never had to reboot from an R update, and I’ve been using QBE since 2007 on a variety of equipment.
            Typically, I do my annual version updates largely from home. I also have the admin password, even though I’m not the owner, so that helps a lot. I’m the IT guy. The owner is set up as a non-admin user, but with full permissions.

            The office part:
            Rebuild and verify file
            Back up QB file.
            Capture disk image of the OS partition (which is also where QB program is installed, the data (company files and attachments folder) on another disk).
            Update QB to the next version.
            Go into services and open up QuickbooksDB** service and change the logon form the default to logon as system account, and check the box to allow the software to interact with the desktop.
            RDP back into server and open the company file using the locally installed (server installed) program, and make sure everything is working.
            Total time 1.5 to 2 hours.
            Go home.

            At the house:
            Teamviewer in to my office PC
            Copy the QBE installation files to a network share accessible to all users
            RDP into each office PC from my office PC, and start installing the new software. I can “leap frog” and get 3 or 4 going at a time.
            As each client finishes updating, log in to the company file on that client as Admin and let QB do the whole initial set-up Nag Fest (version selection, etc.), so the users don’t have to be involved in that.
            Total time to update 39 client machines is about 4-5 hours.

            In the future, I plan to explore adding RAM to the server (32GB) and getting remote licenses for clients and deploying QB as a server app. This vastly simplifies the update process to just having to do it once on the server. Users are then just remoting in to a terminal session, and everything happens on the server.

        • Here is the ROOT of the problem: in recent times the update from R5 to R7 can take as long as the upgrade from V15 to V16. Both require that the Company File be upgraded and reboots, which is the source of alot of the time consuming work I refer to with a Server. In the good old days, an R update happened automatically with only a message to the users, a click of Yes, and a restart of QB with a few minutes delay; no other disruption.

          • There have been many cases over the past few years (if not longer) where an R-level update has required a database update. And, in my test environment, I didn’t have to do a reboot. I haven’t implemented THIS update in any client sites, because I don’t install these updates this quickly after they are released. And, note, I’m not sure that Intuit has the security stuff working properly in all cases. I’m still testing, I’m not ready to unleash this on clients yet.

          • I see a broad variety of situations. Add to the security list along with PCI: Industry standards and Federal law compliance (e.g., HIPPAA).

            Have you seen an accounting firm go through something like InfoSafe certification? Great stuff, this kind of thing is the future and well should be.

          • Low end servers usually are faster rebooting along with less redundancy and fewer roles. And I am including the time to coordinate with users and other precautions. Anyway, it is Windows updating on reboot that can take the most time.

            You don’t have to reboot on a QB update, it only violates Intuit’s specified procedure and can lead to unstable operation.

            39 clients and not one going haywire is impressive, as is 39 clients on Essentials which is limited to 25, so I think you have Server Std there.

            You will want another (Server Std) server for the remote (RDP) Host per best practices and half a chance of it working well.

          • I wasn’t clear. The branch office, being a much smaller operation, uses Essentials. At our main office, the server is running Server 2008 R2 (soon to be 2012 R2) , and also acts as our backup DC.

            Our primary DC at the main office is on 2012 R2, and has a Xeon E3-1246 V3 with 8GB of RAM and a Samsung 850 Evo SSD for the OS drive. It handles AD/DHCP/DNS for roughly 75 users and 200 networked devices. It also is set up with file server role, IIS, print server, doles our Group Policy, and runs our central AV administration console and deploys updates to clients. It also houses a couple of 2TB drives that are backup targets for itself and other devices on the network. It can reboot in three minutes. SSDs work wonders for servers.

          • Thanks for backing my point up: In a rather ideal situation, 6+ hours of a dedicated IT professional, most of which would be down time for users, for a job QuickBooks marketing refers to as “automatic.” At least Charlie concedes it might be “inconvenient.”

          • Agreed. I don’t know why, given that “enterprise” is in the name, it isn’t geared more toward an environment where end users don’t typically have admin privileges, and can’t install software themselves in their machines. And having to fire up QB on each one after the fact and register them individually…
            They need an msi installer that can be deployed through group policy, with the option for an answer file to entrer admin credentials, enter the license and product codes, set the version (manufacturing and wholesale, etc), set whether to uninstall the previous version, handle the registration, and turn off the “yellow banner nags” for users that are already quite familiar with the product. If they had that, a network wide upgrade could be initiated on an evening or weekend and largely take care of itself.

  • Intuit’s procedure clearly specifies to reboot after these type of update installations, and before upgrading the Company File, regardless of whether it is forced in the installation executable.

    Per PCI compliance you Must install R7 whether it works or not, or you are non-compliant. It depends on how the word “regularly” is defined by the all powerful compliance person (who may barely know even what QB is).

    • All I can say is “don’t be the first to install any R level update, let other people be the guinea pigs first”. There are reports of some issues with R7, it isn’t clear yet if this is a good update. I suspect most errors that I’m seeing have to do with data issues already in the file, but it is too soon to tell.

  • One nice thing I found is that the complex password is reversible. I had a simple accounting file for a trust – but presence of the EIN in company information triggered the complex passwords when I installed the R7 update. I was able to go in and remove the EIN (wasn’t necessary anyway) and delete the password. Now the file opens without any password requirement.
    This page has been updated – see Q11:

    • Intuit has been updating that article, and I’m spending time examining all this. The problem is, look at Q13, which lists what info kicks this off (“PII”). Just having a bank account number makes it sensitive. That is going to force a lot of people to get passwords that didn’t have them before. That is a good thing, but it will generate a lot of complaints.

      I’m still looking at the details here…

        • Do you have a bank account in the file? Does that bank account have an account number or routing number associated? That will trigger this too, not just credit card numbers or an EIN/SSN in the company info.

      • Charlie,

        Let’s be honest here, at the end of the day, Intuit needs to be servicing the CUSTOMERS. And your comment that this foolish password requirement “is a good thing, but it will generate a lot of complaints” is a bit self-important, in my opinion. If the CUSTOMER doesn’t want to have a password, then they should be allowed this option. This whole Big Brother idea that Intuit knows what is best for the customer, and the customer doesn’t know what is best for him/herself is going to get them into hot water. I suspect Intuit will see an exodus of customers — not only due to this holier-than-thou attitude, but also for to not be responding to the many many many threads that clearly show that the customer does not want this “security” feature. Extremely disappointed in both you and Intuit.

        • Perhaps I am mistaken, but I was under the impression that a lot of the new password features were being driven by HIPPA and similar requirements, and further, that Intuit is making these changes and not making them optional to void possible liability in the event that user data is compromised in some fashion. I know my company spends a lot of money and time doing a lot of things that we don’t want to do, or really shouldn’t have to do. But we do them to protect ourselves against litigation, our customers against fraud and theft, and make our insurance company happy.

          • Yes, you are mistaken — it is not a HIPPA requirement for the origin of the PII security to be from the software itself. As long as the user has sufficient secondary safeguards in place, there is no problem. Intuit is taking it upon themselves to play Big Brother. It is currently and will continue to get them into hot water with customers. As they say “the customer is king.” Without the customer, you have an empty kingdom.

        • Everyone is entitled to their own opinion, Tyler, and I’m sorry if you are disappointed in me. My comment was “That is going to force a lot of people to get passwords that didn’t have them before”, and I’ll still stand by that. Too many people don’t password protect their accounting information when they should, in my opinion. I think that accounting advisors should perform a security review of their customers if they are in a position to be a “trusted advisor”.

          However, before you condemn me completely, you should read the followup article that I wrote about this feature at https://www.sleeter.com/blog/2016/07/quickbooks-desktop-security-update/

          The 2016 R7 article was written on the day that the release came out, and the full impact of what it meant wasn’t fully understood. After having more time to look into the details, I wrote that followup article, where I again state that I think that improved security is a good thing, and that people should be more concerned about these kinds of issues, BUT I also say that I don’t agree with Intuit’s approach in this case. It should be something that is optional

          • I appreciate your response and acknowledge that you did say this. That being said, Intuit is not anyone’s father, mother, or nanny. This pedestal that they have put themselves on will only put them on the path to lose their market dominance for small business/personal accounting software. When a company loses sight of the customer, that generally is not a good sign for the future. Sad to see such a long-standing piece of software get lost in the big company, self-important mindset. At the end of the day, if the customers stop coming, Intuit’s opinion of what security users should or should not have will be irrelevant.

  • The issue with the password update is that it doesn’t matter if we have CC checked or not – I don’t have that checked on any of my company files and yet I was still forced to password protect my files when there was totally no need for it. Frustrating to say the least – this should be an option yet it’s not.

    • The question is “what should be protected”. And, what kind of password – must it be changed every 90 days, and be complex, or not? I’ll have an update on this in another week, probably.

  • We have the same problem on updating QB Pro 2016 to R7 with being asked for a new complex password, supplying the old one and creating a new, then QB home screen appears for a minute, then the complex password dialog comes up AGAIN and we can not get into our QB file. This is definitely a bug and note related to any one company’s file. Has no one heard anything from Intuit about this? (our only fix was uninstall, reinstall then apply R5 (not R7))

    • Douglas, what I’m hearing is that this happens if there is some corrupted data in your file prior to converting. It is something that you need to talk to Intuit about, or a certified ProAdvisor who can assist you in working with Intuit.

      • Or not corrupted–and the problem is that the company file update process, which is supposed to ensure the company file is ready for the new code, isn’t doing its job in all cases.

        Which is more likely? That might be answered in the form of a maintenance update to fix R7.

          • It’s just that I have found that telling people their company file is corrupted causes them a lot of stress. Something I avoid unless absolutely necessary and a solution is at hand.

      • Yeah – the file was not corrupted, the extremely poor handling of the new passwords can cause the file to be encrypted with a password that can then not be recovered. I did contact Intuit and they were of no help whatsoever. This worked though (QB Pro 2106 on Windows 10):
        Uninstall QB and reinstall (with no updates)
        In the base version (or any version pre-R7), change the admin password to one that conforms with the new requirements:
        Company > Users > Set Up Users and Roles
        Select the Admin user (built in) and click Edit User.
        Change the password to a strong password
        Click Next and then Finish.
        QuickBooks will re-encrypt data in your file; this could take several minutes.
        Install R7

  • and… r10 for QB2015 just dropped today. Not sure if it has these same issues, but it should at least compound the “fun.”

      • Charlie: It’s there at the usual R-versioned manual download URL — they just haven’t linked to their update site yet.

        If anyone wants to get a head start testing it, let me know and I’ll post the link.

  • Charlie,

    I called QuickBooks support this afternoon to get more clarity on this release update and how it relates to user logins. Somethings have been mentioned in your article and in QuickBooks web pages, but here is a summary:

    • All admin passwords need to be changed to a new complex password with a security question.
    • All users (external accountant, included) will need to change their password the first time they login. If you are setting up new user logins, assign a temporary password for the user and let them know they will need to change the password after them login for the first time.
    • All users will need to create complex passwords (at least 7 characters in length with at least 1 number and at least 1 uppercase letter).
    • All users will need to change their passwords every 90 days.
    • Previously used passwords cannot be used.

    This applies to QuickBooks Pro or Premier 2016 and Enterprise 16. Intuit will also have the same requirements for the prior year versions they support (2014 and 2015). It wasn’t clear when we can expect these updates to be pushed out.

    I love to have us create a list of commonly used 3rd-party applications that login to QuickBooks in the background. I have clients who use a variety of apps and I’m not familiar with some of them. Also, with some applications syncing with the QuickBooks Web Connector, I’m guessing those connections need to be “refreshed” also.

    BTW, I did register my complaint that Intuit should have minimally sent an email alert to all QuickBooks ProAdvisors regarding this update and the impact on QuickBooks users. I became aware of the new update yesterday afternoon and was scrambling to find answers. Even with the information I found, there were many unanswered questions. I rather be proactive with my clients than caught up reacting to upset clients.

  • Has anyone had an issue with receiving an Accountant’s copy from the client, having to set up the new password on the Accountants end and then when change file sent back client cannot import the change file?

  • Wow, this sounds like a major headache and I’m taking time out of my day to email my clients to tell them not to update to R7

    Update on the scan check error some of us has encountered….it was NOT fixed in this update.

  • Hi Joan,

    Would you be willing to post your comment and findings into The Sleeter Group Network, under Discussions, QBD ‘2016 Release 7, blog?

    We think others there might be interested in your findings as well.

    Thank you,


    Tamra Groff, Senior Consultant, GASC/GHFG

  • Hi Charlie, it looks like we can no longer install the “database manager only” without first entering the license key. Also, i got an error message when trying to update the database manager from R3 to R7 saying that i need an active subscription. I’ve never seen this before, we only have the database server manager installed on the server and Intuit’s support said Today that we need to install the whole suite. We hung up on them, downloaded R7, entered the license key and then installed the database manager only option – so we didnt need to install the whole suite afterall.

    Just a heads up that it seems they’re starting to trouble the database manager now to enforce the subscriptions. I bet there will be a new string of corruption stemming from this motive…

    • I always install the full app on the (Windows) Server: much easier for updates, especially now that they have R’s that do a Company File upgrade (in addition to the annual releases). But I understand why you would prefer just db manager. It allows manual updating without a Server reboot. But you still have to get all users logged off or they will crash, I presume?

      I would have been tempted to ask that support person how to install the whole suite on a Linux server!

  • I sure wish I could turn off this password requirement too! I’ve ensured no account numbers or feeds or credit card protection are on, but I’m still required. Grr.

  • Darn. This is from the QB site. Not impressed.
    Q11. What happens if I disable credit card protection or remove all the credit card information from the file?

    The update is designed to deliver strong password controls to help ensure that the person attempting to access a QuickBooks Desktop account is authorized. Once the application detects that a QuickBooks Desktop company file has sensitive data, it is configured to add another layer of security protection. However, removing credit card information and Personally Identifiable Information (PII) from the file will not turn off this configuration and users will still be required to set up a password.

  • Am I correct that this R7 update is equivalent to the R10 update on version 2015? If so, what’s the safest way to go about this since so many people seem to have issues. I am ready to update to 2016, but I’m thinking I’m safer running the R10 in 2015 first and then doing the update to 2016. Does that make sense logistically in an attempt to not have any major hiccups? Or does it not matter at all and should I just jump up to 2016? When asking intuit, they say just update to 2016… Any thoughts for this non IT mind of mine?

        • I don’t expect that updating your V15 release to the next revision prior to upgrading to V16 would make any difference. I’ve not seen any issues there. As always, make backups with V15 before the upgrade, and install V16 in a separate program folder, so that you can roll back if you need to.

      • Hi Charlie, I’ve read through some of this and I’m still not sure what to tell a client who is asking what version to upgrade their 2013 desktop to? Sounds like 2016 R5 is the safest bet (if I can get that specific release)? Appreciate your advice!

        • Choice 1: Never upgrade again, use a different program/service for payroll that imports to QB.

          Choice 2: Pay the money, download and install the current install package from Intuit. Do a install on a testing PC and import/upgrade your Company File offline to see that everything is OK. Then do the upgrade to your systems, making use of Intuit Support as necessary.

          If you are going to get up to date, be up to date.

          No better time than upon doing upgrade to use support and make Intuit get you going right. And get it right on the test run, not on your production systems.

        • The other thing I realized afterwards is our client is running on RightNetworks so they probably only have the option to go to the latest 2015 or 2016. Given that, I agree with the suggestions to ask RightNetworks to setup a sandbox for testing but do I suggest they go to the latest 2015 or try 2016 R7? Appreciate all advice!

          • When you use a hosting company you are at the mercy of what they offer to you. The issue with 2016 R7 is pretty clear – do you want to accept the additional password requirements?

        • I’d normally say 2016 R7 because you want all the internal bug fixes that it includes. Then they have to deal with the password issue, possibly. Always dangerous to recommend something that is older but has bugs in it.

          • There was a 2016 R8 release, and it is “legit”. Intuit released it, and then pulled it back about an hour later. I actually got a copy of it.

            That release had a change in how the security feature would work. However, Intuit found that the results weren’t what they hoped for and quickly pulled it back. I know the changes that they made, I don’t know the details of the reason why they pulled it back.

            I didn’t publish an article on this because it had such limited distribution and was pulled off the market.

  • El consejo sería que durante los próximos días, vigiles las temperaturas con el termómetro, y en caso de volver a presentar anomalías, llamar al Servicio Técnico oficial, ya que tienes dos años de garantía. Los frigoríficos No Frost, eliminan el exceso de humedad del interior mediante unos conductos (normalmente en la pared trasera) y conectan con un recipiente que se encuentra al lado del motor y evapora el agua.

  • There has certainly been a lot of controversy regarding the requirement for complex passwords, but I haven’t heard anyone explain why it’s so vitally important to have complex passwords for the Windows version, but…

    “Note that these updates only affect the Windows versions of QuickBooks desktop. This doesn’t apply to QuickBooks for Mac.”

    Really… There is not need to protect the data if running on a Mac?

    • The real answer to this will most likely upset the masses but there isnt much we can do but accept it anyway. I’ll state that this is my opinion, but i have however performed extensive research and have concluded with hard evidence that the enforcement of passwords has nothing to do with Intuit’s care for our security. The real motive behind this is to enable a mechanism that will lock us out of our data files if we don’t renew our licenses.

      I dont have access to the QuickBooks code, but from what i can see, i believe there is a master password associated with our license when it is activated; (Activated License Master Password + User’s Complex Password = Password Stored in QBW File). When our license expires and we do not renew, the ALMP (for short) will not be present, and as such we will not be able to log in.

      Dont expect them to confirm this, only time will tell if it is simply speculation or fact.

      • SJ, show use your evidence. I see no reason to think that there is any sort of conspiracy here to lock you out of your files, in conjunction with licensing. QuickBooks Pro/Premier/Accountant aren’t licensed for a given amount of time, unless you subscribe to the “Plus” program, and in those cases you still get to use the product after your subscription expires. Enterprise is on a subscription basis, but that is something that was implemented prior to the password changes. I don’t see any sort of conspiracy here.

        • Believe me Charlie, there are new mechanisms in place. There is a wide spread issue right now that is locking up QBES users and this ability was not present before. Research in to the matter shows that a sort of “telemetry” or tracking server is imposing the lockups.


          I dont expect them to keep this page available for long after they resolve it.

          The question is… How or why should it be possible for something on Intuit’s internal servers to effect response time within the desktop versions of QuickBooks? Are they tracking each and every click we make? What else are they tracking and why? This wasn’t possible before, but it is now.

          Are they responsible for slowness in Pro and Premiere? Do they still recommend that companies need to upgrade to QBES to resolve the slowness? Hmmm.. multiple coincidences are not just coincidences, but what can we do? You should look in to this.

          You now need a subscription to install or update the database server, which means your database server will stop working if and when they lock your subscription status – hence the mechanism.

          What’s next? I foresee monumental price hikes over the next few years and if you don’t renew your license you’ll get locked out of your file entirely.

          • https://community.intuit.com/articles/1587264-quickbooks-freezing-when-accessing-invoices-or-customers-in-enterprise

            11:00 AM PDT Update:
            We continue to investigate root cause.

            It has been determined that some customers trying to install QuickBooks Enterprise may receive an error message: “Sorry, we need to verify your subscription before installing QuickBooks Desktop” or “Sorry, it looks like you need a subscription to start using QuickBooks.” This issue appears to be related. We do not currently have a workaround for installations at this time.

            A link between Today’s issue and what i was saying a year ago? It’s just a coincidence, don’t worry 😉


          • They’ve resolved the problem, which didn’t affect all users (I never ran into the issue in any of my installations).

            Yes, they have moved to a subscription model. That happened a few years ago. Old news. And, yes, as with just about any subscription-only product, if you stop paying for the subscription, you lose the ability to run the products. Your file isn’t locked, you can take it to a ProAdvisor (for example) who has a current subscription and they can access the file. Not a file lock, it is a lock on running the product on your system.

            Yes, they have ties to a subscription server, which checks periodically for a valid license. Again, that has been known for some time now. And yes, they can monitor your file activity to a degree, it is something that you can opt out of (I’ve covered that in the past, don’t recall what year that was implemented).

            Slowness in Pro and Premier? Different issue. Enterprise uses a more advanced version of the database server than Pro and Premier, which accounts for a lot of the difference in response time. Again, that is something that is widely known in the ProAdvisor community.

            Price hikes for Enterprise? Possibly. I don’t see “monumental” changes there, but who knows? In other articles earlier this year I’ve predicted that Pro and Premier may move to full subscription pricing in the future. But I don’t see those kinds of changes coming in the very short term.

            QuickBooks Online is the future of the product for Intuit. Again, something that has been widely discussed.

    • Interesting point, about the Mac version. Intuit hasn’t clearly (at least, as far as I’m concerned) given us ALL of the reasons why they implemented this feature. There were some hints, though, in the initial notes about this, as well as some other clues. I suspect that a PART of the issue had to do with some security leaks, or at least less secure pathways, via the QuickBooks SDK. This is the method that people use to access data through add-on programs. If that was a factor, note that there is no SDK for QuickBooks for Mac. You can’t access the Mac version of the database through the SDK. In addition, one of the factors they look at is in adding security if the file is passed off to a third party (such as, an accountant). QuickBooks for Mac doesn’t have an “accountants copy” feature. So there are differences between the Mac and Windows versions that MIGHT come into play here.