QuickBooks 2013 R7 Bug STILL A PROBLEM

Written by Charlie Russell

Can't get rid of this bug!If you are using a third-party add-on program that works with QuickBooks Desktop versions, there is an ongoing problem that may cause QuickBooks to crash when you try to use your add-on product. I’ve talked about the QuickBooks 2013 R7 bug fix before, but there is a lot more to this than I originally realized. Here is what I see at this point, and how to fix the issue.

Update 7/1/2013: Intuit has released the R8 update to US users – this RESOLVES THE PROBLEMS that we list here. See this article: https://www.accountexnetwork.com/blog/2013/07/quickbooks-2013-r8-released/

What Is The Problem?

If you are using a third-party add-on product that accesses the Windows Desktop version of QuickBooks, the R7 update to the program may stop your add-on product from running properly. Odds are you will see QuickBooks crash with an unrecoverable error when the add-on product tries to do certain operations. Some add-on products won’t do this, it depends on what QuickBooks data structures they are working with. You may see this error window:

QuickBooks 2013 R7 Crash

This is a major problem, as many businesses rely on QuickBooks add-on products for their daily operations.

Releases, Releases, What is in YOUR Wallet?

What “release” are you running? Open your QuickBooks file, then press the F2 key to open the “product information” window. In the top line you will see your “release” information. For example:

R7 130606A

This tells me that I’m running QuickBooks Accountant 2013, and that I have Release R7P+(U130606A). That is a lot of info.

The “R7P” portion tells you that you are running the R7 release. QuickBooks starts off with the R1 release when Intuit issues a new year of product, and as they fix bugs they generally bump up the release number. See my article on the QuickBooks 2013 R7 release to see what they fixed this time.

The rest of the line, the “U(130606A)” portion, has to do with “critical fixes”. I talked about this feature in my earlier article on critical fix releases. This is a way for Intuit to get a patch out to us quickly without going through the more formal “R-level” update. It is a new feature in QuickBooks 2013, and we haven’t had a real test of it until now. Note that you might not see this notation at all.

What is confusing to me is that this number does NOT necessarily indicate that you HAVE a critical fix installed!

Prior to last week, you would see the notation “U(121026B)”. All that means is that your copy of QuickBooks has made a connection to the Intuit update server. If your program hasn’t connected, you probably won’t see any notation like this at all.

This week, you will probably see “U(130606A)” like I show above. That means that Intuit has made a “critical fix” available, dated June 6 2013 (the “130606” part). If you see this, then QuickBooks has downloaded this critical fix to your system, but it hasn’t necessarily installed it. All this means is that the connection was made, and that some files have probably been downloaded, but the patch might not have been applied.

Another confusing issue – this notation may show up but it might not apply to you. For example, this latest critical fix resolves a problem in the R7 release. But, you may see this notation if you have an earlier release, like R6.

R6 with 130606A notation

This shows that the file is at R6, but it has the 130606 notation, which only applies to R7. Has anything changed? Supposedly not. The critical fix is there, waiting for an update to R7.

I’m totally confused by this. The notation shows, but might not apply to me. The notation says something is downloaded (maybe), but not necessarily installed. How do I know if this has been installed, and what it does?

Critical Fixes Don’t Always Get Installed

Let’s set aside the issue of the notation showing on releases that it doesn’t relate to, lets just talk about knowing if it has been installed or not.

On a conceptual level, if you see the notation about a critical fix, and that applies to your current release, you should expect that the patch is installed. With this particular update (R7 and 130606) I was telling people that “if you see R7P+(U130606A) you have the fix”. Then I started getting a lot of calls about my CCRSoftware add-on products. People had this release notation, but they still could not use the add-on products. What gives?

It seems that critical fixes won’t always apply. According to Intuit, if you are running Windows Vista or later and have UAC enabled, you have to run QuickBooks in the Run as Administrator mode to get the fix to apply properly. Few people run QB this way normally.

  1. Right click on your QuickBooks icon and select Run as Administrator.
    Run as Administrator
  2. Select Help then Update QuickBooks.
  3. Select the Update Now tab.
  4. Scroll down and select Critical Fixes
  5. Click Get Updates.
  6. When the program is done, exit QuickBooks
  7. Restart QuickBooks as you normally would. The patch should apply. Update 6/12/2013Make sure that when you run QuickBooks this time that you do NOT use the run as administrator option, because that could interfere with the proper operation of QuickBooks add-on products. You will ONLY do that in step 1 above, the one time.

Wow – that is a lot of work, and you don’t know when you should do this because you don’t get notified of the availability of the critical update, and you don’t know what release it applies to!

You can check to see if the patch applied by going to this folder (note that the “QuickBooks 2013” portion of the path will be “QuickBooks Enterprise Solutions 13.0” if you are using Enterprise):

  • 32 bit systems: C:\Program Files\Intuit\QuickBooks 2013\CriticalFixes
  • 64 bit systems: C:\Program Files (x86)\Intuit\QuickBooks 2013\CriticalFixes

If you see a file with a “DLL” file type there, the fix should have been applied. If you see a file with a “DAT” file type, and a size of 0KB, the fix might not have applied and you should try the process again.

Critical fix is NOT applied

Update 6/12/2013: One point of clarification on this screen shot – this is looking at the program folder where you MIGHT find the “critical fix”, or a file related to that, which would be downloaded by Intuit into your system as a part of the “critical fix” process.

This Critical Fix Might Not Work – How To Fix It

Update 7/1/2013: Intuit has released the R8 update for QuickBooks (see https://www.accountexnetwork.com/blog/2013/07/quickbooks-2013-r8-released/) – IN MY EXPERIENCE THIS TOTALLY RESOLVES THIS PROBLEM so I am removing the DLL fix that is listed below.

Going back to the specific problem – R7 breaks QuickBooks so that add-on products won’t work. Does the 130606 critical fix take care of it? Not necessarily.

As I mentioned, the fix might not apply if you don’t use the run as administrator process. However, there are reports of situations where even if you do this, the problem remains. There may be an error in the patch that is delivered this way (I haven’t confirmed this myself, it is what I was told by a knowledgeable person).  Update 6/12/2013: It looks like the file that is downloaded as a part of the critical fix process does NOT correct all problems with the interface with add-on programs. The version that we provide below is a later revision that covers more bases.

So, here is a manual patch to fix the R7 problem, as provided to me by Intuit.

Update 6/12/2013: The screen shot below is showing the location where you would MANUALLY move a file that you can download from this article. It is a different location, and file, than described earlier for the location of the critical fix.

Update 6/14/2013: Please note that if you perform this manual patch, you may find that in a FUTURE update of your QuickBooks installation you will either have to remove this file or completely reinstall QuickBooks 2013. It is not clear at this time what will happen, as we haven’t seen that next release yet. The manual update bypasses one update mechanism and that might cause the next to not work correctly. Intuit is recommending against doing this update. HOWEVER – I will note that AT THIS TIME, this manual update is the ONLY way to stop the unrecoverable error for many situations.

Update 6/19/2013: Intuit has started pushing out the R7 update to Canadian and UK users. UNFORTUNATELY the DLL fix we list below will not work for the Canadian and UK versions of QuickBooks. We don’t have a solution provided by Intuit for these installations, other than to get help from Intuit (or a Canadian/UK ProAdvisor) to roll back to the R6 version.

  1. Close QuickBooks and any third-party add-on programs that access your QuickBooks data.
  2. Locate the file named sdkqbimpl.dll in your computer system. This will be in the “Intuit” folder in “Program Files” (or “Program Files (x86)” in 64 bit computers), in the folder for the version of QuickBooks that you are using. My example below is for Enterprise – if you are using Pro or Premier the name will be “QuickBooks 2013”.  Make sure you get the 2013 version of the program. NOTE that this may be a “hidden folder” in Windows – see your computer support person for information on how to view “hidden folders” in Windows.
    Locating the DLL
  3. Rename the sdkqbimpl.dll file to something like Oldsdkqbimpl.dll.
  4. Download this updated file (it is a large one) by clicking on this link: sdkqbimpl.zip.
  5. Unzip the file to get the new sdkqbimpl.dll file  – you will need a password, which is    Intuit01
  6. Move the new DLL file to the location where you found the older file. Update 6/12/2013: Please note that this is NOT THE SAME LOCATION as described for the critical fix process earlier in this document. It is important that you pick the proper location for this file for this correction to be effective.
  7. Restart QuickBooks. Update 6/12/2013: Make sure that when you run QuickBooks after installing this update that you do NOT use the run as administrator option, because that could interfere with the proper operation of QuickBooks add-on products.

In every case that I’ve heard of so far, this process fixes this particular problem.

There May Be Other Problems!

The fix we are talking about here addresses one particular problem – QuickBooks crashing with error 00000 37760. There may be other issues that look similar that interfere with third-party add-ons floating around, but I haven’t pinned that down yet. Many people are seeing a message “QBXML components have not been installed” when running an add-on with QuickBooks 2013. It is not clear what is going on here, and the fixes that Intuit has listed in their website are not working.

At this time, indications are that THIS error is occurring with versions EARLIER than R7. It is thought that upgrading to R7 will fix the problem (not confirmed). Of course, once you go to R7 you introduce the “crash” problem. Luckily, that is the one that is fixed by the procedure above.

At this time all of this is very vague. There is a lot of confusion about this, since we seem to have multiple problems showing up all at the same time.

What Is The Latest Critical Fix?

Intuit has created KB article INF23122 which has information about the critical fix feature, and it will list the current value (they are calling these “ULIP”, for “ultra light patch”).

Unfortunately, at this time, the KB article doesn’t tell us what exactly the critical fix FIXED. That would be helpful information!

“Critical Fix” Is A Good Idea, But…

The original concept of the “critical fix” process is a good one, allowing Intuit to get out a fix to a problem very quickly. This particular issue is the first real test of this in a “production” environment. The R7 patch introduced a significant problem, and Intuit responded VERY quickly to this issue and got a patch going.  However, it looks like some additional work is needed in their delivery system. Hopefully they’ll resolve some of these issues before they try it again.

  • We need a way to positively know that the fix was applied. It is too hard to tell now. Just seeing the notation doesn’t mean that a fix relates to your installation, or that it has been installed.
  • We should not have to run as administrator and manually apply the patch. Having to do that defeats the entire purpose of this. It should happen automatically
  • We need to be notified of these updates, and be told what they are fixing. I hate having to stumble on a fix just by periodically looking for a revision number change, and I hate not knowing what was changed. In this particular case I was informed ahead of time, and I really do appreciate Intuit’s help with this, but that might not be the case in future critical fix situations.
  • Finally, it should be obvious that the fix needs to fix a problem and not create more. It looks like this fix might not have really fixed the issue, and some people think that the process introduced some new errors, but that is speculative at this point.

All of this creates a conundrum. I usually recommend that you turn off automatic updates so that you can control how updates are managed (as I describe in this article). However, if you do that, you don’t get these critical fixes automatically, you have to manually start them. Then again, are these critical fix updates introducing new problems? I’m still thinking that we want automatic updates OFF so that we can control what is going on, but it is a policy that I’m re-evaluating.

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.


  • Thanks Charlie for keeping us up to date on this. What a problem. Intuit is not having a good year with releases whether that be with Pro/Premier or POS. Frustrating. Completely agree with your points that we need to know more about if/when/what is being applied. Why not make the problem easier to understand which fosters confidence in whether the solution is resolved or not.

  • […] Update on 6/20/2013: The DLL download in this article fixes the problem for every CCRSoftware customer who has tried it (and told us). For a more detailed explanation of this “critical fix” and the process that Intuit is using, see this article: https://www.sleeter.com/blog/2013/06/quickbooks-2017-r3-bug-still-a-problem/ […]

  • Groan, “I’m totally confused by this” me too Charlie 🙁
    Hate to think what the level of understanding is out there in user land.
    I expect we’ll start to see related support calls.

    • John, I’ve been spending most of the day answering phone calls and emails about this issue from my customers. And I’m talking to a group of SDK developers who are all seeing this problem, AND the one that might be related.

      • Charles, do you know if the Quotewerks integration will work with QuickBooks online. We use QuickBooks pro and have reached out 14,000 item list maximums and its now stopped us from importing.

        • Tracey, their website only lists the desktop versions of QuickBooks, so I’ll guess not. But you should check with them.

          In the US, QuickBooks Enterprise allows a larger list than 14,500. Unfortunately, you are in the UK, and I heard that the UK version of Enterprise is being discontinued?

          There are ways to reduce your item list, but they take a lot of work and/or effort.

  • I jokingly commented in your original article about the R7update release that I hoped all the ‘they did to fix problems’ didn’t create more problems…….’no I do not have a crystal ball….’.

    But in this case not only did the release update have problems, but the fix to the update even had problems and now it appears that even the ‘fix’ to the ‘fix’ has some problems as well.

    Somewhere ‘the ball’ is getting dropped when fixes to fix fixes to fix updates to fix problems seem almost endless….where has their programming ‘quality control’ gone? Oh, they must still be trying to fix the problems they were trying to fix when they realized that they had broken their QB-QC. It is at times like this that I start to think that Intuit is acting more and more like our broken ‘government’.


    • In Intuit’s defense, they did run a beta test for R7 prior to the final release. I can’t say, however, if this was reported and ignored, or just not reported. I have to say that I didn’t test my own add-on apps with the beta release. That takes more work to set up (and that is my issue, not theirs).

      Also, a small grain of defense – this is the first time they’ve had a big “critical fix” release like this, so some aspects of the process are new and not tested in the real world. I know that they did some beta testing of this feature, I don’t know if that test covered all the bases or not.

      Some of the problems that are outlined here, with the “run as admin” stuff, didn’t show up on my own system the first time that I ran through this, although I was in such a hurry to get this fixed I could have overlooked something.

      And, the final fix, the new DLL, was presented to me the same day as I reported the problem to Intuit – with one of their staff members working with me late into the evening that day. The DLL patch itself fixed the problem and I was able to get it to my customers in less than 24 hours after the initial report, which is very good.

      It is just unfortunate that the original problem in R7 was such a major problem for some people. Too bad the first “critical fix” couldn’t have been something of lesser import. But then, if it was, it wouldn’t have been a “critical” fix.

      The real key here is to see how this process is handled in the future, now that they see how it worked.

  • Thanks for the awesome information Charlie. I am grateful to be getting this information BEFORE it becomes a problem for me or my clients. Luckily I have not upgraded any QBES clients to 13 yet and this is one more reason I am glad I haven’t!

  • Thank you for this information. So far, QuickBooks 2013 seems to have ongoing, continual, critical problems. Add those to the interface issues that have not been addressed, or only partially addressed, and it appears that this is not a reliable version for users. I also agree with you regarding the lack of information on release updates. When the releases are sent out, it would be very useful to have a list of just what they are “fixing”.

    • Tina, we do get a fairly good list of the fixes (and, I list those details in this blog). The problem is, sometimes they make mistakes, and the “fix” also breaks other things.

    • Kirsten, I’m not sure what you mean by “brought in old, old data”. I’ve not seen things along those lines. It may be that your file, before the update, had some corrupted data in it. Updates do sometimes cause issues if the QB database has some problems to start with.

  • I’m seeing an additional error after applying the patch.

    The patch did fix QB crashing, but now any EmpoyleeMod with PayrollItems returns statusCode 1000, error message “There has been an internal error when processing the request.”

    Still haven’t found the problem – curious if anyone else has seen this (have verified that these same messages are working on a pre-R7 version)

      • Thanks for the repsonse! This was done in both ways (on different sites), with the same result. We did verify the patch was applied by looking at timestamps and the CriticalFixes directory (in fact, before the patch, QB was crashing every time).

        I had posted on the IDN forums as well – it was suggested that the updates may have been made even with the error returned. This turned out to be the case (that the employee earnings entries were updated at least in some cases). We are modifying our code to temporarily ignore the statusCode 1000 errors on employee earnings/payroll items mods for now.

        I’ll post another message if I end up finding the ultimate cause of this (it was working fine before R7 and the critical fix).


        • Matt, there appear to be multiple problems with R7 beyond the ones that the DLL update fix. It is harder to pin them down, for me, as they are in areas that I don’t use with my own software.

          And, other bugs in R7 not related to add-on products. For example, R7 no longer sorts timecard entries by date when adding them to an invoice.

          Note that if you have R6 or older, there may be some OTHER SDK related problems, fixed by going to R7. So we may be in a bad spot here…

  • I tried the Critical Fix and it did not work in QB 2013 Accountants Edition. Now I cannot do any updates with getting an Unrecoverable Error Code: 02685 05616. The manual update did not work because the file you mentioned is not on my hard drive. Any Suggestions.

  • Hi, I have QB Pro 2013 and have Release R6P+U(130606A). I ran the QB as administrator to do the update for critical fixes (I made sure the critical fixes was checked). I went to the path C:\Program Files (x86)\Intuit\QuickBooks 2013\, but did not see a CriticalFixes folder. Does that mean a critical fix was not applied? How can I fix this?

    • I can’t say why you don’t have that folder, Sandy, but my understanding is that it SHOULD be there. You can use the manual procedure in the “how to fix it” section above, that will work.

  • Question: I just upgraded to 2013 Retail last week. I am in Windows XP. I was very nervous to do so as there is a ton of negative feedback out there, but with the lack of support Intuit had for 2010 I had no choice. I tried to install R7 yesterday and couldn’t (thank goodness!) I read your article today about the bugs in it and my question is this- I am in R5 with no notation of a critical fix. Should I update to R6 or just wait until they figure out how to really fix their issues?
    Thanks, Kim

    • The problem is, Kim, “how do you upgrade to just R6”? If you use automatic updates or click the “update QuickBooks” button, you will get R7. You don’t get an option to upgrade to R6 only.

      You can work with a consultant who may be able to help you (try the “find a consultant” button in the top of this blog page), some will know how to get you to just R6.

      Take a look at this article for the bug fixes in R6 to see if you need those fixes: https://www.sleeter.com/blog/2013/03/quickbooks-2013-r6-2/

      And, if you are using Intuit Payroll, you have to think about the fixes in R7 to see if you need those.

      It isn’t a simple thing…

      • Thank you Charlie. I guess my concern was generated by a statement I think you made about the R7 eventually being an automatic update. We are a very small company with no support unless we pay for it and I don’t’ want to turn off automatic updates per your suggestion not to do so if we don’t have support. I’m thinking that with all the problems they are having with the R7 they won’t push it as an automatic update until they have solved the problems and maybe my concern is for nothing…. This has got us all so riled up! I’m not even having issues but what I’ve read here scares me and I want to do everything to avoid them. So- I guess I will just stay put and keep reading your updates.

        • Kim, I believe that it HAS been pushed as an automatic update, since I am now getting hundreds of email messages from people that are seeing the problem.

          As far as turning off automatic updates, that works as long as you are working with a knowledgeable ProAdvisor who can keep you up to date as to what updates are available, so you can make the decision. Without support like that, you can’t turn auto updates off, probably. Alternately – I always post a blog article about any updates from Intuit when they come out…

          • It was done to us as an automatic update! Now our Clip program will not interface with QB and transfer the invoices to QB anymore. That’s a big problem to have to manually put the info in twice.

  • Hi Charlie, If you are using the Accountant version of QB 2013, how do you turn off Automatic Updates. On my copy the “No” option is grayed out.

    • Ah, yes, Rick, thank you for reminding me of that feature. I’ve written about it before (complained about it) – as you see, YOU CAN’T TURN THAT OFF if you are using the Accountant version!

      But, you don’t have to actually INSTALL any updates – when you get R7 automatically, the next time you run QB it will tell you that there is an update to install, “Just Say No”.

      Best I can offer…

      • I’ve been doing that, but my question is when do I say yes and how do I know I should?

        if they push a corrected R7, and QB has already downloaded the present buggy one, will QB download the new one over writting the old?

        My premier accountant is the same as Sandy’s, no critical fix folder, yet my F2 says R6P+U(130606A)

        • Rustler, I don’t have a good answer for you.

          In all my test situations, if I select the “critical fix” option in the Update window, and click the manual update button, they folder is created. Several people have said they don’t see the folder, but I’m not sure what the exact workflow is.

          If you need an add-on product and it isn’t working with your R7 update, do the manual patch I list above. With my own customers, this has always fixed that particular issue. It doesn’t for some, but that looks to be add-ons that use the Web Connector, I think (not sure on this).

          The notation of 130606A doesn’t guarantee that the folder is created. It doesn’t guarantee anything as far as I can see.

          How do you decide WHEN? Tough to answer in general. You can watch for updates by monitoring their update website periodically, or you can watch this blog for notifications. Then you look at the list of bugs that are fixed, and decide if you need any. If you think you do, then you wait a week or so to see if there are any complaints. If not, then you back everything up, and do the install, and cross your fingers.

          With this release, Payroll users are finding they MUST install the update, or payroll stops working. Stuck between a rock and a hard place…

          I generally avoid telling people if they should update or not, because I don’t know their specific situation. I can’t say “do not update to R7”, because I don’t know if you use Payroll and need the update, for example. Those kinds of things make it hard for me to say “go or no go” in these situations. With payroll, you generally have to do the update. But for some people, this update is a disaster.

          “push a corrected R7” – they generally don’t re-do an R-level update. They have to either use the critical fix mechanism (which is not working quite right) or make a new R-level update. They won’t push out multiple versions of the same R-level release, as far as I’ve ever seen. But, I guess they could.

          Isn’t it fun?

          • I don’t need R7 as far as I am concerned, I am only using 13 as a test file to answer questions, I hate it and am sticking with 2012. But I would like to keep it current, I’ll think on it some I guess

            fun – well yes in a perverse kind of way, the programmers messed up POS v10 last year, now they moved on to 2013. Can’t wait to see what is next, only thing left is online, or payroll itself.

  • I installed the ‘fix’ to no avail. All was done correctly and verified by Intuit Qbes support. They told me to reinstall R6 for now.

    • Tom, what kind of problem are you having? Is it an integration with an add-on app? If so, which app, does it use the “web connector”, and what environment are you in?

      I’ve been hearing that apps that use the “web connector” are still having problems, possibly, but I haven’t been able to confirm that. I’ve heard that SOME people in SOME hosted environments have had continuing problems, but again I can’t confirm that yet. Also, while the patch fixes some of the bugs, there are possibly some others still floating around. So, any info you can provide would be appreciated.

      Lots of people are finding that this patch fixes their problems, but there are many variables involved.

  • I sympathize with all the users that have experienced these issues. We have had some of our users indicate that the patch did not work however when we have logged into their computer to apply this patch for them it worked flawlessly. I know this situation is very stressful for those under deadlines but just take a deep breath and read the instructions carefully and it will work for you.

    So far this patch has worked for all of our users to fix the issue that is described in this article.

  • I have not been able to use QB since the R7 update because the hourly billing part is malfunctioning – it does not have the time in chronological order or any other order. When I went back to R6 the assisted payroll connection would not let me run without being in R7. This has been a nightmare.

    • Carolynn, that is a major problem.

      The only solution I can offer is that my own company’s (CCRSoftware) add-on product, CCRQInvoice, has a feature that can sort invoices by the service date. It doesn’t work for every situation – I recommend that you download the trial, make a backup copy of your database, and test it on one invoice to see if it works for you.

      The trial works for 30 days, so if it works for your situation you have 30 days for free. If Intuit hasn’t fixed the problem by then, you have to choose if you want to purchase the product (just $75) or continue to live with the problem.

      I don’t have a better solution at this time. I don’t know if Intuit will be fixing this issue soon or not.

  • Good question John – are we or are we not supposed to apply the manual dll patch?

    This entire R7 update is a nightmare – there are so many bugs, issues, what have you that are popping up that it’s overwhelming!

    I have one machine that claims it currently has the R7 critical patch but when I attempt to go download the critical update again it and QB crashes.

    Another machine with R6 will not get the automatic update, so I went to uninstall and install the full QB version that has R7 built in – and I can’t even uninstall the software!

    Some people say the manual dll patch works, others say it doesn’t fix anything.

    It’s very distressing and customers are VERY angry!

    • John, I can only speculate about them pulling the DLL patch in the developer forum – I think it is because (1) they pushed the critical fix that should have resolve the issue, and (2) another ULIP (critical fix) is being readied.

      Nancy, in my experience, the DLL patch method works IF people follow the instructions carefully and have the ability to get it to the right folder, for most QBSDK apps. The problems that I see reported (but I con’t confirm) are that the critical patch isn’t necessarily working (not the DLL download) and that maybe apps that use the Web Connector aren’t resolved. Also, I don’t know if the patched DLL fixes ALL of the QBSDK issues – I just know that it fixes the issues that MY software was running into.

  • I have been getting the following error message since installing QB Enterprise 2013, through all of the releases including R7:
    Quickbooks has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available.
    Level 2 support has not been able to help as of yet. It crashes on multiple companies daily.

    • Matt, that is probably the problem I describe here, if you are using an add-on product of some sort. The DLL patch listed above should resolve that. But it is related to using an add-on product.

  • Note for the UK and Canadian users, I believe that you will be getting the R7 patch on June 13th (but I’m not sure). I also don’t know what the patch will include – if it will be the same one the US people get, or if it will be one that has a fix, or what.

    • Hi Charlie

      I installed the UK version patch yesterday so that I am on ES13.0 R7P+U(130201A) and guess what – same issue with third party apps. There is no critical fix to download and install. Do you have any ideas please? Thanks.

      • Mike, I don’t have an answer for UK versions, unfortunately. Best I can say is “hold on for the next update”. The code for the UK and Canadian versions is a bit different than that for the US version.

  • A note: Intuit has a KB article on this issue at http://support.quickbooks.intuit.com/Support/Articles/SLN74717

    Even though it says “Sync Manager”, this is the same issue I talk about in this article for add-on products.

    If you subscribe to that KB article by entering your email address, you’ll get a notice from them when they have a fix. They also are hoping to get a feeling for how many people this affects (they won’t get that, many people won’t get the notice to subscribe there).

  • It says to put the DLL file in c:\program files\Intuit\QuickBooks Enterprise Solutions 13.0. I’m running QB Pro 2013 – I don’t have that folder anywhere on the computer where QB is installed. I tried putting the updated DLL in c:\program files\Intuit\QuickBooks 2013 but the error persists.

    • Andrea: The instructions point out that if you have Pro or Premier thta there is a different folder – the one that you chose.

      Make sure that you have the new DLL there, if yo don’t have administrative permissions for the folder it might not allow you to add the file.

  • Charlie, I expect I just missed the blog article if you did one, but is there a way to roll back out of an auto-update. Like now, say you have R7 but with the problems is there a way to roll back to R6?

    • Jim, if you have a complete installer that was downloaded from R6, you can uninstall QB entirely and reinstall from that. If you have an installer for ANY older release (perhaps from a CD, which usually is R1) and the web patch file for R6, you can uninstall R7 and reinstall the older version, and patch to R6.

      The problem is getting hold of copies of those. If you don’t keep things around, you can contact a responsible/knowledgeable ProAdvisor who might have access to that and can get it.

      I haven’t posted this, because sometimes rolling back to a prior version has some issues in specific situations, and I don’t like to broadcast a general fix (with links to files) in this blog when I’m not talking to a specific client to understand their situation. I would hate for someone to try to roll things back and then find that they have run into a problem.

  • Weird thing for me – I get the unrecoverable QB error when QuickBooks is not even open. It just pops up sometimes. I applied the manual fix…we’ll see what happens.
    Thanks Charlie for all you do!


    • Lisa, if you have Sync Manager active (for some kinds of third party apps, using IPP) then that can happen. Sync Manager makes some calls in the background to the SDK, and so it can run into issues. I don’t know if that is what is going on in your case, but the same fix should resolve that if this is what is going on.

  • I owe you my first born. Thank you for taking the time to lay out a solution to the quickbooks upgrade problem. We were held hostage in a technical hellhole. I followed your steps and eventually was able to fix the problem and we can now upload our web orders. YOU ROCK!

    • Jean, I’ll settle for your second born…

      Keep an eye on this blog, I expect further updates from Intuit at some point, and if I can figure out what is going on with that, I’ll write an updated article…

    • Which “this”? The unrecoverable error? There are several bugs in QB that may cause an “unrecoverable error” – but the one that has the error code in the screen shot I show, crops up when an add-on (or manager for an add-on, like Intuit’s Sync Manager) tries to do certain operations with the file.

      R7 has other issues, like not sorting time entries in invoices, not saving item “notes”, maybe some others that haven’t been pinned down yet.

  • Latest news: Please note that if you perform the manual patch, you may find that in a FUTURE update of your QuickBooks installation you will either have to remove this file or completely reinstall QuickBooks 2013. It is not clear at this time what will happen, as we haven’t seen that next release yet. The manual update bypasses one update mechanism and that might cause the next to not work correctly. Intuit is recommending against doing this update. HOWEVER – I will note that AT THIS TIME, this manual update is the ONLY way to stop the unrecoverable error for many situations.

  • Charlie,

    Thanks for your invaluable updates and due diligence. I have a client who is upgrading from 2010 to 2013 and R7 had already rolled out, so that’s what we got when we downloaded the software. The client isn’t using any QuickBooks or 3rd-party add-ons, so I think they will be OK.

    MY QUESTION –> In a client-server environment with shared downloads, are the critical patches included in the shared download? Or is there something additional I need to do at each workstation to make sure the critical patches “push through”? What about my other clients with client-server installations? How do these get installed?

    I’m looking forward/hoping for specific answers at the Scaling New Heights conference next week!

    • Joan, I haven’t tested this scenario, but I would assume that the critical fix is not in the downloads – it has to be updated through the critical fix process. Again, I haven’t tested this. As far as shared downloads, another good question and something I haven’t tested, but I would assume (often a bad thing to do) that these will be handled.

  • This worked perfectly for fixing the integration with Quotewerks. I had to use the manual DLL replacement.

  • I’m experiencing the invoice/date not in chronological order issue. I installed the patch as you directed but it’s still doing it. What did I do wrong?

    • Karissa, you didn’t do anything wrong. My apologies for not making this clear – the DLL patch only resolves the issue with add-on programs. The sorting issue isn’t fixed, we’ll have to hope that they will have a patch out that will take care of that soon.

      • Oh – ok – I’m not very technologically savvy, as you can tell! I’ll tell you, date sort problem is very annoying.

  • Does anyone else have a problem with multiple currency, when I try to download the rates I get a message that I’m not attached to the internet. I’ve run updates and checked the internet settings that say I am connected? Help!

  • I have performed all the steps and QB is still crashing during sync with a third party. Any other suggestions? I’m getting nervous because the end of the month is coming and my invoicing relies on my third party.

  • […] Posted on June 27, 2013 by Alex Flores As is the case with any implementation/integration, once all the planning and assessments are done you will eventually need to install software. It’s always essential to confirm that the client meets all the minimum requirements http://support.quickbooks.intuit.com/support/articles/INF21187 in order for the software to install properly. Every now and then, even if requirements are met and networks are properly configured you will run into issues that will need troubleshooting. In the case with this project we had an issue integrating the third party software due to a QBE 13.0 bug which gave us a “qbxml components are not installed” error. After reading up on potential bugs it looked as if updating the software to the R7 release would remedy the issue except for one important detail, the R7 release causes other SDK issues. Luckily Charlie Russel wrote a very informative article discussing this and a workaround, I would recommend reading it here https://www.sleeter.com/blog/2013/06/quickbooks-2013-r7-bug-still-a-problem/ […]

    • You can’t do it with a web patch.

      You have to uninstall your current version (R7) and then reinstall with the full R6 downloader. I haven’t looked at their full version download to know if that contains R6 or not.

  • Keep an eye out because I am afraid this Bug goes deeper……. I was getting error messages when I would try to open my Quick Books but then I would go back out and come in again. It would open fine. Then the office started noticing invoices were not in my system that had been printed and even the company’s name and address that she had entered was gone and saved when entering the invoice gone!!! Since then we have noticed some checks are even gone. No common area. IT IS CRAZY! My accountant now is rebuilding my entire books. 🙁 I had not updated my version but will now for sure!

    • Shelly, this particular bug only relates to add-on products, and it is fixed in subsequent updates. That doesn’t mean that there can’t be some OTHER issue in the release that is affecting you. However, the kind of problems you are talking about might not be due to a bug in any particular release. There are a lot of other things to watch for, data corruption problems can have many causes. We’d have to look at the error messages in your qbwin.log file after a file rebuild…

Leave a Comment