- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
06-02-2022 07:13 AM
Hello everyone! We have windows server 2019 vaults and when we add a new local account for administration purposes the new accounts can't use the start button nor the search bar, has anyone encounter this error? We followed the steps from this articles, but it seems it only works for 2016 windows servers.
https://community.cyberark.com/s/article/KI00015028
https://community.cyberark.com/s/article/Unable-to-click-on-Start-button-Windows-2016-hardened-Vault-server
Any help will be much appreciated, thank you
06-02-2022 07:44 AM
Hello,
Can you please try this, (this is slightly different to the articles you mentioned, there is also the camsvc service to change for Windows 2019) :
1. Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
2. For services "AppXSvc" & "ClipSVC" & "camsvc", change the Start value from 4 to 2
3. Restart the Vault machine
This is a known bug from CyberArk (reference 00017864).
Thanks,
06-02-2022 07:44 AM
Hello,
Can you please try this, (this is slightly different to the articles you mentioned, there is also the camsvc service to change for Windows 2019) :
1. Open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
2. For services "AppXSvc" & "ClipSVC" & "camsvc", change the Start value from 4 to 2
3. Restart the Vault machine
This is a known bug from CyberArk (reference 00017864).
Thanks,
06-02-2022 07:55 AM
Hi @Clement Imbert thank you very much, I was all day for the solution. This should be something that cyberark should put somewhere more accesible. Do you mind telling how can I access to the bug reference?
06-02-2022 07:58 AM
Hi @Candelaria Orellana
Did the steps above resolve the issue ?
I am from CyberArk and this known issue is currently not public. I am going to check internally if it should be (maybe it is a human mistake).
If the status is changed to public, it should then be visible here :
Thanks,
06-02-2022 08:02 AM
Hi @Clement Imbert yes, the steps worked. It should be public since the only solutions that i found as public are only for windows server 2016 and not windows server 2019.
06-02-2022 08:03 AM
Thank you for confirming ! I have created a ticket internally to review the bug and see if it can be made public.
06-20-2022 02:10 AM
hello @Clement Imbert could you provide me a link to this CyberArk (reference 00017864)? I'm not able to finding it
06-20-2022 02:12 AM
hello,
Normally, you should now be able to see
KI#00017864: Windows missing functionality for newly added user on hardened 2019 (force.com)
Thanks,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

