Coldfusion Developer InstallAnywhere

Given that it ran after a few hours, I'd argue strongly that something is amiss--but not with CF, as again this terrible delay is not normal behavior for the cf installer.

Instead, my first guess would be that you may have one OR  MORE anti-virus solutions that are scanning the file writes AND perhaps reads of all processing of that installer. These days, av tools do that, not just scanning what's "downloaded". And the installer first extracts many files before it runs, then it lays down thousands of files in cf's folder as it runs. If all that is scanned...and if more than one scanner is scanning it, things can back up. I've definitely seen it take dozens of minutes--but never a few hours.

And there may be other impacting factors, such as:

• was the drive onto which you installed cf a regular one (ssd or hard drive)? Or some sort of nas/san/share? That could impose network io that could add slowness
• were you installing cf in a VM? If so, did you perhaps have a snapshot running? In some VM hypervisors, running on a snapshot incurs a costly penalty the larger the snapshot gets
• There may be still other impacts that you or others could think of

And I realize it may be none of the above, for you. I leave this as much for others who may find the thread in the future. 

Would love to hear if you might try something and run the installer again.

Of course, you may "leave well enough alone" since it completed, but if you have ongoing perf issues, all the above could impact that also and be worth resolving.

For example, a quick test you can do now is to simply restart cf. How long does it take to go down and come up. If all's well and normal, it could complete that in less than 30 seconds, or perhaps a minute on some servers. How long does a cf restart take for you? If more than even a couple of minutes, I'd think you have this larger issue to resolve. 

(Before anyone points out that CF CAN take longer to go down or come up, I'm referring to "normally", when cf is not under load and is otherwise running fine before stopping it. There can be occasions where people feel they must kill the cf process for it to go down. Similarly, some find "cf won't start", and sometimes cf startup could be impacted by other processes that may be running, including processes that continue after an is update and reboot, for example.)

To all that, Andrew, you mention this is Windows 10. Does Task Manager's performance and processes tabs show not just cpu and memory but also network and disk? If so, it could be useful to watch those to see if they rise tremendously during cf shutdown/startup, whether due to cf or something else.

I've seen people have file change detection tools, file sync tools, and all manner of other things sometimes slowing processing.. but cf startup/shutdown (and installation) might stress things far more than your normal processing, so that you might not have otherwise noticed such an "other" thing having an impact on your machine.

Just food for thought. I help people solve such problems daily, and while answers are more obvious when I can SEE what's going on with them, I share these as examples of the kinds of things I've seen have an impact like you have experienced.

Let us know if you find or try anything, like a simple restart, or if instead you might opt to feel this is "case closed" now that CF installed. 

If you find you can't recover, you could install via the new zip installation feature introduced with CF2021. It's offered the same place as the full (installanywhere) installer. After unzipping it, run the cfinstall.bat file (Linux folks would use cfinstall.sh).

This does NOT install those related services, but if you're not needing them that won't trouble you. Those who do can find them on the cf downloads page as separate installers: 

https://helpx.adobe.com/coldfusion/kb/coldfusion-downloads.html

That cfinstall script would offer to implement a service for cf, btw. 

Let us know if this gets you going.

As for what happened with the other installer, see the install log which should be in the root of the cf folder. Let us know if it has errors you don't sort out. 

Look around for a little window (maybe modal) that you didn't see earlier. I've had that happen a couple of times before.

Dave Watts, Eidolon LLC