When updating existing Windows Service, password is not masked

When I install a windows service with octopus, the password gets masked. But when I have an existing windows service set up, the password is visible in the task log (see screenshot):

The x service already exists; it will be stopped and reconfigured

Stopping the x service

sc.exe config "x" binPath= "\"C:\Octopus\Applications\x\14.1.8-dev\x.exe\"" DisplayName= "X" start= "auto" obj= "domain\user" password= "my secret, unmasked password"

[SC] ChangeServiceConfig SUCCESS

I just realized that I did not mask my username in the screenshot, could you please remove the attachment? Cheers

Thanks for the report Ben. I’ve deleted the attachment.

This looks like a problem with the way we’re capturing PowerShell output. I’ll try to replicate this locally.


Issue: https://github.com/OctopusDeploy/Issues/issues/449

Cheers, I added the completely masked screenshot again.

Morning guys,
sorry, this may have been fixed at some stage. But I just released a windows service this morning again with version and the password was shown again (see attachment).

Hi Ben,

Thanks for reporting this!

I have reopened the old issue which you can track here:

To see if we can resolve this for you.

Thanks for the screenshots and updating us that this issue is still happening.


Apologies Ben, I’ve shifted the issue to https://github.com/OctopusDeploy/Issues/issues/996 - it would be tremendously bad luck, but it seems as though you might have hit a second bug in the same area (or perhaps there were two independent causes at play the first time).

We’ll need to take a fresh shot at reproducing this, so we’ll post more details via the ticket. Thanks!

Hi Ben,

We have fixed this issue and it is in the latest build of Octopus Deploy.
The download link and release notes can be found here:

Happy Deployments!