- 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.
03-11-2024 02:26 PM
Hello , We are on version 14.0 PSM and everything was working fine till yesterday. Today we observed that CAPSM.exe is crashing every time we initiate any connection. Whether it's RDP,WinScp, Web connection etc. I observed that Windows Team installed few KB's and found one KB5033910 and it's related to .Net4.8 & We searched on google & found that few people also suggested that other apps were crashed after applying this KB.
Just wanted to cross check - is KB5033910 really a culprit in our case?
We reset credential file and did all type of basic troubleshooting but no luck, someone suggested in previous KB of CyberArk <PSM Service crashed> to comment API address, we also did that but no luck. Before going for repair, we would like to check whether KB is causing an issue, we can try to uninstall the KB and check again or only repair is the option??
"Event Viewer Logs" -
PSMPP098E Call to PreDisconnect in Protocol Connection failed. Reason: PSMPP136E Failed to send request. Reason: PSMCU014E Failed to connect to the messaging channel. Reason: PSMCU003E Failed to connect to the named pipe server. Reason: PSMCU004E Failed to open the pipe. Error Code: [2].
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: CAPSM.exe
P2: 14.0.0.30
P3: 6578b431
P4: VCRUNTIME140.dll
P5: 14.32.31332.0
P6: 4fbfc837
P7: c0000005
P8: 0000341e
P9:
P10:
Faulting application name: CAPSM.exe, version: 14.0.0.30, time stamp: 0x6578b431
Faulting module name: VCRUNTIME140.dll, version: 14.32.31332.0, time stamp: 0x4fbfc837
Exception code: 0xc0000005
Fault offset: 0x0000341e
Faulting process id: 0x2584
Faulting application start time: 0x01da73f99d558d91
Faulting application path: C:\Program Files (x86)\CyberArk\PSM\CAPSM.exe
Faulting module path: C:\windows\SYSTEM32\VCRUNTIME140.dll
Report Id: efbf6c6e-0b41-4469-9557-a5a008ce4531
Faulting package full name:
Faulting package-relative application ID:
04-02-2024 11:02 PM
Thanks for script @Michal Masek?. Now I can see issue is fixed in new release 14.0.1 - Article Detail (site.com)
03-11-2024 02:45 PM
Probably one for CyberArk support unless someone has identified the culprit already.
I've had three similar crashes last week, but psms have been ok since. I have a case open to try and find root cause but sadly no response yet!
03-11-2024 02:49 PM
@Malcolm Murray Yeah, we will open a support case. Yes, we also faced similar crashes and opened case but those cases are now opened as Open bug and unfortunately no update on that KI 😞
03-11-2024 02:50 PM
Version 14 is nightmare specially PSM
03-12-2024 05:42 AM
Hello, I got the same problem today in customer's environment.
Occurred only on one of two PSMs so tried to compare installed updates. Those are WinServers 2019 so there is not KB5033910 (which in your case is for WinServer 2016) but there is a KB5033911 installed (the same update but for WinServer 2019) for both of them. Therefore I assume this update is not the culprit.
I found another difference when reviewing updates. PSM not affected by the issue had installed Servicing Stack 10.0.17763.5084 - but if I understand it correctly it is just an earlier compilation of OS and both PSMs has already installed a newer one - 10.0.17763.5441.
Also tried to overwrite faulting dll file with version from not affected PSM but got the same result. So going to gather logs with xRay tool and send a case to CyberArk Support now....
03-12-2024 05:46 AM
Hello @Korneliusz Lis - CyberArk provided us 2 updated files. (CAPSM.exe and PSMRecorder.exe )
Steps to replace :-
By replacing these 2 files, it resolved the issue for us.
Thanks !!!
03-12-2024 06:12 AM
You mean where are those 2 updated files from? Sent directly from CyberArk in your case?
Just thinking what are the differences because we have downloaded PSM v14 today and there is no newer version. Also the same zip was of course copied on both PSMs. It does not make sense for me - why installed from the same source got us two different results.
Copied those two files from working PSM to affected one but problem still occurs.
03-12-2024 06:17 AM
Yes CyberArk provided us these files directly on our case. <with named debug version of PSM version 14>
03-12-2024 02:04 PM
Issue was not related to KB. CyberArk confirmed it's a bug noticed after few days. There is not any official article or document for this but solution provided by R&D team of CyberArk.
03-13-2024 01:07 AM
Then I assume there will be official patch released.
Anyway, thank you for your answers and fast reaction! 🙂
03-26-2024 09:08 AM
Hi everyone,
I have solved this today with cyberark support, its easy to fix, you can use my PS script to fix it. it is easy to understand, just edit file paths if needed.
# Create the destination folder with the current date and time
$destinationFolder = "C:\scripts\temp-fix\" + (Get-Date -Format "dd-MM-yyyy-HH-mm")
New-Item -ItemType Directory -Path $destinationFolder
# Copy all files, folders, and subfolders from the source to the destination
$sourceFolder = "C:\Program Files (x86)\CyberArk\PSM\Recordings"
Copy-Item -Path "$sourceFolder\*" -Destination $destinationFolder -Recurse
# Delete all files, folders, and subfolders from the source
Get-ChildItem -Path $sourceFolder -Recurse | Remove-Item -Force -Recurse
# Start the CyberArk Privileged Session Manager service
Start-Service 'CyberArk Privileged Session Manager'If this issue will appear often before it is fixed by cyberark, you can use task scheduler with this script and use event id of cyberark crash event from event viewer as trigger for scheduled task to fix it automatically.
03-26-2024 09:08 AM
Hi everyone,
I have solved this today with cyberark support, its easy to fix, you can use my PS script to fix it. it is easy to understand, just edit file paths if needed.
# Create the destination folder with the current date and time
$destinationFolder = "C:\scripts\temp-fix\" + (Get-Date -Format "dd-MM-yyyy-HH-mm")
New-Item -ItemType Directory -Path $destinationFolder
# Copy all files, folders, and subfolders from the source to the destination
$sourceFolder = "C:\Program Files (x86)\CyberArk\PSM\Recordings"
Copy-Item -Path "$sourceFolder\*" -Destination $destinationFolder -Recurse
# Delete all files, folders, and subfolders from the source
Get-ChildItem -Path $sourceFolder -Recurse | Remove-Item -Force -Recurse
# Start the CyberArk Privileged Session Manager service
Start-Service 'CyberArk Privileged Session Manager'If this issue will appear often before it is fixed by cyberark, you can use task scheduler with this script and use event id of cyberark crash event from event viewer as trigger for scheduled task to fix it automatically.
03-26-2024 09:08 AM
Of course no guarantees, its my opinon, not official solution.
03-26-2024 09:08 AM
Of course no guarantees, its my opinon, not official solution.
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!

