XYplorer Beta Club

Didn't want to clutter up the other thread with my off-topic stuff, so here I go again:

Running XY portable from drive D: on Win7 x64 with regular (limited) user rights.
Every time I trigger an install.exe from within XY, it makes XY crash as soon as I confirm the elevated rights dialog.
This has been the case with previous XY versions as well. It also happens (not as "reliably" though) with portable apps that require elevated rights.

No damage done, XY simply expires in the background (often I facilitate this by clicking Cancel in the error dialog presented by XY), then I start the same file from anywhere else without further ado.

Hey, I just noticed, it does not happen when I right-click the very same file and pick admin rights beforehand. The same dialog comes up, I confirm and it proceeds without problems. I can reproduce both behaviors when starting up this portable tool from within XY:
http://www.nirsoft.net/utils/search_filter_view.html

It does not happen here (win8.1). Hm.

Don't waste time on it. Let's leave it on record and wait for other users to confirm it or not.
I'll try it on other machines and report back.

The problem is very persistent, so I've been collecting more evidence. It's not restricted to corporate environments, but happens on private machines, too. IF - and this seems to be related (not 100% sure) - if they also run any kind of tool that handles user rights.

What's weird:

• XY is not customized by those tools (to always fire up with certain privileges)
• it does not happen, when XY was started with elevated admin rights
• all other file managers I tried are not affected at all, even though they run portable, too, and even though they're not listed either in those "substitute" run-as tools

You should be able to reproduce it with freeware like SuRun, or Sudo.

Does it also happen when you turn auto-refresh off in XY?

Alas, yes. Doesn't make a difference. Exact same thing. XY encounters a problem, says GoodBye, clears the view to bring up the application I started from within XY. Same thing for portable and installed software.

Does it also happen with XY's own installer?

I don't get to that point. XY tells me it's already running. And that I have to close down any running instances before I proceed.

Just to rule out misunderstandings because of my - somewhat unfortunate - topic title - the problem is not limited to installations. It also happens with portable exe-files that require elevated user rights.

It definitely does not happen here, which leaves me no chance to hunt this bug.

Hm, that means I always have to pester the guys from IT to grant me admin rights to start with. I already know where that winds up ("get another file manager"). Or I live with the crashes - so far XY has always gone down the drain all by itself - it never takes anything else with it, even the called tools continue their interrupted start-up just fine. But it sure takes some nerve to sit it out and wait for the system to unfreeze and respond again.

What happens if you run the target exe with cmd prompt?
Select the file and enter !"<curitem>" in addressbar. Or in the old way, open cmd prompt in the location and type in the exe filename.

SammaySarkar wrote:What happens if you run the target exe with cmd prompt?
Select the file and enter !"<curitem>" in addressbar.

That works, a bit scary (console window in the background), but XY stays alive.
Have to try it in corporate environments, too.

The main problem, however, is not that I wouldn't have workarounds - usually I pass my current paths to the dual pane of another file manager and take it from there. It's rather that I don't always think of it when I am caught up in other things. Nor do I always know in advance what tool will require elevate user rights.

Stef123 wrote:No damage done, XY simply expires in the background (often I facilitate this by clicking Cancel in the error dialog presented by XY), then I start the same file from anywhere else without further ado.

Oh, there is an error dialog in XY? What does it show?

Here's the one from my Win7 laptop:

Ah, this one.

Does it come
- right after the elevation prompt pops up? (if you can somehow detect thissince it fills the whole screen)
- after you cancel the elevation prompt?
- after you OK the elevation prompt?