ColdFusin 2021 Update 2 causes all installed packages to be lost

[Server Team]

I have installed ColdFusion 2021 Update 2 throught the admin UI on two systems now. One development and one testing. In both cases, after installing the update I was greeted with the following message...

After reinstalling the administrator UI as sugguested by the message, I login and can see that none of the other packages I had previously installed were still installed. I then had to manually install each of the packages again.

These systems were built using the 32-bit zip installer on Windows Server 2019. The server was installed into C:\ColdFusion and the instance is C:\ColdFusion\cfusion. Once installed, the packages were all installed using the cfpm.bat file and restoring the contents of an export taken previously. The settings were then all restored using the cfsetup.bat file. Maybe something with the install location of C:\ColdFusion or me using the cfsetup.bat or cfpm.bat to configure the systems originally cause the update to do it?

In any case. After the packages that were blowed away were re-added, all the settings appear to be fine.

Any insight would be helpful. Thanks.

[BKBK]

I noticed that, too, when I installed Update 2. I presumed that that is the intention. In a modular architecture, a fresh re-installation might cope with interconnectedness and complexity better than an update of individual modules.

In any case, you would expect the ColdFusion Team to document this. It could cause unnecessary alarm.

[Server Team]

Yeah, I would expect to see this documented in the release notes for the update. Because it is not there, I consider it a bug.

Applying Update 1 did NOT remove the administrator or adminapi. So, personally, I think someone dropped the ball with testing/QA on this update.

[HarmonThomas]

I had the same issue, all packages were uninstalled after installing Update 2. Also, I had to deploy the update from the command line because the update did not show up in the Admin UI. I hope someone from Adobe reads this and responds!

[Charlie Arehart]

Harmon (and BKBK), can you confirm whether you had installed CF using the zip install approach, like bcserverteam indicated was the case in the original post here?

And bcserverteam, you mention how update 1 had not caused this. Can you confirm that in the case where you applied update 2, whether you had applied update 1 on that instance before doing update 2? You may have, but perhaps you may not.

In both cases here, I'm just trying to help understand who does and does NOT experience this error. 

I can confirm that I have NOT experienced the error on any machines where I have applied update 2--but I have not installed those with the zip but with the full installer.  So I suspect this doesn't happen to folks who use that. But we'll see.

But I also notice in the update 2 technotes that there is a "bug" listed as fixed that talks about an issue that can arise if one applies update 2 without first having applied update 1. It's not clear if that being listed as a "bug fixed" means that WAS a problem which is now solved or not.

So again, these things are why I think it would help for us to be clear on such details, for those who experience this problem. Thanks.

[Server Team]

In the cases I had where all packages were removed after applying Update 2, Update 1 had been previously installed.

[BKBK]

I upgraded to Update 2 using the ColdFusion Administrator. 

[HarmonThomas]

Hi Charlie, I had Update 1 installed before installing Update 2 and I did not have any problems with packages being uninstalled. I installed Update 1 from the Administraor UI and I installed Update 2 by downloading the Jar file (hotfix-002-328618.jar) and installed it from the command line. I would have liked to installed Update 2 from the Administrator UI but Update 2 did not show up as an update to select to install, even though the Administrator UI indicated there was an update was available by the star with a 1 (see below). I also knew Update 2 was available because of a notifcation from Adobe.