Done a few upgrades with Postgres and not had an issue with it.  Maybe a support case can help determine the issue and inform others here?

Interesting case, it is supposed to stop all services automatically before start installing the upgrade.

This seems not to stop services completely during the installation process.

exactly.

I didn't delve into it unfortunately I was in a hurry to update the production environment.
I have more infrastructure to update today I updated 3 of them,
next week I have at least 6 more. but all with SQL express.
let's see if the case comes up again.

stay tuned.

@Link State One of my customers had the same issue when I installed the new version. But it’s using SQL Express, not PostgreSQL. I tried to reboot the server and ran install again (I ensured all services were up and running). The issue is gone. just FYI.

Nice to see a workaround in case this comes up for me when I upgrade. Thanks @Link State 

I haven’t run into this but it does feel like something here manually stopping services/processes may resolve the issue if rebooting the server prior to the update doesn’t.

hi @dloseke  & @CarySun  in my case even with the vbr server reboot ,i had the same behavior i had to kill the services.

Hi @Link State - just following up on your post here. It seems you answered your own query possibly? If so, or if any provided comments helped, go ahead and mark one as ‘Best Answer’ so others who experience the same issue may benefit. 

Thanks.

lol marked wrong post  @safiya can you correct? thx

Doh  

Or @Madi.Cristil