Elevate policy giving Windows cannot access the specified device, path, or file.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Elevate policy giving Windows cannot access the specified device, path, or file.

L2 Linker

We have an elevate policy and the programs in it give a "Windows cannot access the specified device, path, or file" error. If I right click and choose run as admin the program opens fine.

 

versionIds_oct20__068Vy00001tjrETIAY.png

31 REPLIES 31

L2 Linker

"run as admin" checkbox is an interesting work-around. I might test that here, but have just been given the go-ahead to roll-back to the previous version.

 

Case is open here as well; haven't had an update from it in a few days.

 

Windows versions that have the issue: 23h2, 25h2.

 

I made another observation today: The initial 26.8 version we deployed allowed the user to run the app one time per login. I tested the latest 26.8 today, and the app never opens (unless launched using one of the alternate methods above).

 

I'd be open to scheduling a meeting to work the issue, although I don't know what we'd accomplish without support.

 

As always, thanks for your response.

L1 Bithead

I think us just documenting our issues here is plenty helpful! I noticed similar behavior with the 1 time elevate (confirmed with task manager to check if the process was elevated) but then later on the machine would have issues again.

 

Have you attempted imaging a fresh machine with no group policy, applying the required UAC settings, to see if you experience any issues. One hunch I had was that maybe a CIS Level1 policy was conflicting with Idira. I have not gotten around to testing yet.

 

Also whats the latest sub version of 26.8.x.x are you running with confirmed issues? So far for me its 26.8.2.xxxx

L2 Linker

I haven't tested without GPO, but that's an interesting idea. I probably can't test that today, but may be able to get to it later in the week.

 

26.8.0.36 is the version installed on impacted workstations. I tried updating mine to whatever the latest was as of last week, but that didn't resolve it. I've since rolled back to 26.6.2.3198 by uninstall/reinstall.

L2 Linker

Would you be willing to share which endpoint protection software you are using? I'm curious if we're running the same.

L2 Linker

We are using 26.8.2.143 and did not notice the issue till after we upgraded from 26.6.x. As the issue is being worked around by right clicking and running as admin and only effects one application used by a small subset of our users we have not done much more troubleshooting beyond what support asked us to try when we first created the ticket.

L0 Member

Is anyone getting anywhere with support on this issue? We are seeing this throughout our environment on anything that was upgraded to 26.8 and has an elevate policy.

L2 Linker

Support did work with me, but now states the issue is with my endpoint protection software. At this time, the issue hasn't been resolved for me.

 

Update on my observations:

  • Works fine with 26.6 and earlier
  • Works fine if endpoint protection software is removed
  • Works fine if something else launches the app (.bat file, modified shortcut, etc)
  • Works fine if user opens by "Right-click, run as admin"
  • An unknown situation allows for it to work once per windows session (sometimes) I think this appeared to be working, but wasn't actually elevated

 

I'm hoping my endpoint detection vendor is able to assist - I suspect a small change was made to the cyberark connector and a new exclusion is required.

 

Is anybody NOT having this issue?

 

(edited)

L2 Linker

Support was also not very helpful for me. We tried removing our other security software but that did not make a difference. Checked file/directory permissions. Tried removing and reinstalling the EPM agent. Nothing has helped. Issue does appear to only happen since upgrading to 26.8.

 

Our findings match ian.boje

L1 Bithead

Just got off the phone with Idira support. We found that with these elevate policies, if you restart explorer.exe in task manager. You can run the program with an "elevate policy" ONCE and in the vf_agent.exe -ShowProcInfo it'll show the .exe as having no policy applied with the parent process of explorer.exe. After you close it and attempt to run again, it will bomb with a file permissions error from windows. If you run the program from cmd/batchfile/etc it will launch but its because of child process inheritance from cmd. So our "elevate" .exe ends up getting a run normal trust policy from the cmd.exe parent process.

L2 Linker

Interesting. It looks like mine shows "Policy Action Elevate" when launched from a powershell window. Is your elevate policy set to only elevate if explorer.exe is the parent? It seems to match "Elevate" on mine:

 

Field_Content_versions_08nov__068Vy00001yE6NSIA0.png 

EDIT: Okay, now I see. The single attempt after login is likely not being elevated, as also demonstrated by restarting explorer.exe.

L1 Bithead

My guess is we have a trust policy for cmd.exe that allows it and its child processes to run normally. So our effected .exe file is getting that policy instead of elevate, which allows it to run.

L2 Linker

Just created a shortcut to launch vf_agent -ShowProcInfo; The humorous results:

 

Field_Content_versions_08nov__068Vy00001yFLKQIA4.png

L2 Linker

An update was sent to me from my endpoint software vendor's support. Is the application you are running a 32 bit app? Based on what they see, I'm wondering if we're encountering this: https://community.cyberark.com/s/article/KI00026982

L1 Bithead

Ian! I dm'd you in regards to the security software questions.

L4 Transporter

I was seeing this message for a few things such as Rundll32.exe on a training course within the test lab. so nothing is actually broken it's just a random error message, I used to see it at my previous gig last year and it did make me paranoid and I can't quite recall if it impacted a few other things it likely did and quite a few users so I got the same exact error but for gpmc.exe on a new epm test lab. Can you guys maybe run procmon capture from sysinternals.exe and process explorer and maybe even debugview.exe see if that can help narrow it down, likely Idira R&D are working on it but who knows...

keep an eye on IOPS , cpu/ram usage etc too maybe it only happens on slower devices?

  • 205 Views
  • 31 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!