Toad World® Forums

Problems with Toad 14.0 crashing

Well, there is a later version but I don't think it will solve your problem unless it's due to connection timeouts.

Please follow the steps detailed here to send me your user files folder.

Also some steps to repeat the problem (as best you can if you don't have exact steps). I know you said select and delete text, but is there any more to it?

I'll try to repeat the problem next week. I'll be out the rest of this week due to holidays



I'll do that as time permits, but can you tell me the prior stable version (ie. without this defect)?

Well, it's hard to say because we haven't identified the exact defect that you're having, but try version 13.3. Get the same bitness (32/64) as your current version of Toad so you can use the same Oracle client.

Different Toad versions can be installed side-by-side. So 13.3, 14.0 and beta can all be installed without problem. They each keep their own copy of settings, so you don't have to worry about any conflicts there.

Let me know if it happens in 13.3 or not.

1 Like

Also, Try this in 14.0, it may solve the problem:

  1. In Toad, Go to Options > General.
  2. Under “Application data directory” section click on “Open folder”
  3. Keep this folder open in Windows Explorer and Close Toad
  4. In Windows Explorer, go into the User Files folder. Toad.ini is in there.
  5. Double-click Toad.ini to edit with Notepad.
  6. Find the [SETTINGS] section and add these lines under it:
  7. Save Toad.ini and try Toad again.
1 Like

Toad, 64-bit, I can consistently create the "Toad Not Responding" issue:

  1. Go to Editor and select an invalid table "SELECT * From XXX"
  2. Press F9, it will display the "ORA-00942" pop up dialog
  3. Dismiss the dialog (Click OK)
  4. After it dismisses, press enter (The XXX table name is highlighted at this point), TOAD will lock up "Not Responding"

Doing those steps in prior versions, no issues. Bug?


Yes, I'd call that a bug. I tried to reproduce it but unfortunately, I could not.

I have a few ideas:

  1. Go to Options -> Editor -> Behavior. Uncheck "Display SQL errors in popup dialog". Does that help?

  2. Scroll up to my reply on Nov 20 and try those steps.

  3. Try the beta. Toad for Oracle 14.1 Beta (Do not uninstall your 14.0 version. The beta requires the latest official version to also be installed.)

If those don't fix it, I'd like to get a copy of your user files folder so I can try to reproduce it. But I am hopeful that it's already fixed in beta. We did solve a few lockup issues, but admittedly, this exact issue does not come to mind.

I did try "Uncheck "Display SQL errors in popup dialog" already, no luck. I was trying to find settings where it highlights text to see if I could change it to not highlight. But TOAD 13 no issues and it looks exactly the same as my example. The XXX will be highlighted, I hit enter and the XXX is deleted. This is in In 14 it seems like it is trying to do something with the XXX and gets hung up.

Oh, it gets hung after you hit Enter (at first I thought you were hitting enter to make the dialog go away). OK, yes, I can reproduce that and I believe that one is fixed in beta.

I can also easily reproduce the issue with these commands (, 64-bit).
But in my case I am not getting any dialog box, where to click OK (P3 - dismiss the dialog)
Having that said, I will press enter and crashes.

So quite a lot of (3 known to me) "toad crashing" issues with this version (, 64-bit) :confused:


@raul.kaubi Are you able to use the beta?

I don't have time at the moment to try beta, but sounds like you are pretty confident it is fixed so I will just wait for the next official update, thanks!

The next official version is due out sometime around March.

Although I highly recommend taking the time to install and use the beta. The majority of the changes in it are bug fixes.

I just installed beta, version.

Couldn't reproduce any of these crashes:

  • In editor word wrap enabled with long oneliner sql
  • In editor selecting text and using spacebar to delete it
  • In editor running sql with invalid table, F9 and then enter


Excellent. Thank you for the feedback.

You may have noticed, there is a Change Log in the comments section below the beta download links.

I just upgraded to 14.0 and have had nothing but issues with Toad hanging. Had to force restarts at least 3 times so far this morning.

Enough is enough! Clearly this version is not fit for purpose so will be reverting back to 13.3. That will teach me for upgrading to a newer version when it is first released.

I think more testing of products before releasing is require to avoid customer disappointment like this.

1 Like

Hi @paul.hill

Sorry 14.0 caused lock ups. I believe those are fixed in the current beta, and they seem to be fixed for @raul.kaubi too.

I hear you about quality. My goal has been to get Toad as solid as possible. I know users are tired of problems, and I want to fix them. We do perform a lot of testing, but it's impossible to predict everything that could cause a problem. I can tell you that I've been primarily focused on bug fixes for the past few versions.

Please try the beta. Toad for Oracle 14.1 Beta. You have to keep 14.0 installed to run the beta, but you can also keep 13.3 installed too. They each keep their own copy of settings, and run completely independent of each other.


Hi John,

Thanks for your email.

I understand Toad is a huge application and there are many pieces of functionality that could potentially cause issues, but on all three occasions this morning I was editing and running SQL in the editor. It really doesn’t get much simpler than this and this should be bread and butter for Toad.

I’m not interested in using a Beta as I don’t have enough spare time to “test” Toad. To be productive I need a tool that just “works”, so I have reverted back to 13.3 and I won’t be planning to upgrade again for some time.



Hi Paul,

Thanks for the feedback. I hope you'll give 14.1 a shot when it officially comes out.


Hi John

Think I've found another bug. Fresh install and new workstation.

Day one, I started editing a long SQL statement with multiple sub selects and unions. On folding the inner sub selects so I could see all of and work on the outer group by's etc. On mouse wheel scroll, toad would die. Have experienced editing test SQL code and package implementation.

Fold code, mouse scroll, toad dies.

Would appreciate to know, if you can reproduce, if this is fixed in beta before I decide on beta or installing older 13.3


I have been experiencing the same issues and found that disabling the "Auto Replace" prevents Toad from crashing in this scenario. Instead when you press enter, it just deletes the invalid table name.