And even if you're in a panic, it may take only about 10 minutes to read this whole post. See the link above.) Hope the info to follow is helpful for you.
For the more visual folks, I also addressed much of this in an hour-long presentation I gave at various events in recent years, the last being recorded on the CFMeetup (as linked to there).
And you really should check it even if the update seems to or reported itself to be "successful". :-) If it reports even one error or nonfatal error (and even it only reports warnings), then something was amiss with the update, and you can try to read through the remainder of the log to see if among the several hundred remaining lines it may explain what happened.
It's easy to do once you know how: If the table reports all successes, great. That can be challenging because in some updates, many of lines in the log may have the word "error" or "warning" in referring to files that were changed in the update.
In that case, it may just be that it tried to refresh before it was back up.
Just try refreshing the CF admin, or check if CF is indeed back up.
For those who may have jumped to this "solution" step, I discussed in the previous section how the built-in CF update process will only wait a set amount of time before proceeding to try to do the update.
But by stopping CF yourself, you can make sure it's really down (whether via Services or command-line alternatives, or if you choose just to kill the process).
The TLDR version: check the Cold Fusion update log (not logs in the normal CF "logs" folder.
It's just that sometimes when you stop CF at one point in time, it may go down faster than when the updater tried to stop it at a previous point in time.
The matter of why CF sometimes is slow to go down or come back up is really a topic for another blog post.
So the first thing to do after you update Cold Fusion (10 or greater) is to check the update install.
And I do NOT mean here the logs in the CF "logs" folder.