I'm not sure if I am missing a feature (though I RTFM'ed) or if what I'm asking is impossible or if it has not been implemented: I installed some software from the Microsoft Store - and that created a folder for the app in C:\Users\{me}\AppData\Local\Microsoft\WindowsApps\ which contains a .exe with 0 bytes and Type "Application (symlink)".
How can I find out the location this symlink links to?
Dealing with symlinks
Dealing with symlinks
______________________________________________
Happy user ;-)
Happy user ;-)
Re: Dealing with symlinks
Info panel Meta tab, Ctrl+3 by default.
Re: Dealing with symlinks
Thanks - but that's not it.
Wouldn't it be nice if we had a scripting command that would give the target of symlinks (or junctions or even simple .lnk etc.)= ______________________________________________
Happy user ;-)
Happy user ;-)
Re: Dealing with symlinks
Those aren't normal symlinks then, and there is plenty scripting commands to deal with normal symlink/junction/link targets, so not sure what you are talking about there, and what I suggested originally would work for normal symlinks.
Re: Dealing with symlinks
Hmm, according to the properties tab it is a symlink:
So if you suggest there are plenty commands, could you pls. recommend one that would reveal the target of symlink (or goto it)?
I admittedly don't know much about these, so I can't judge if it is normal or not. But there clearly is something magical about it - coz' it launches the app when I dbl-click that empty file.So if you suggest there are plenty commands, could you pls. recommend one that would reveal the target of symlink (or goto it)?
______________________________________________
Happy user ;-)
Happy user ;-)
Re: Dealing with symlinks
It is probably just being identified as a symlink because it has the L attribute, but who knows what Microsoft does behind the scenes with that UWP stuff. For a normal symlink, for example
echo <prop LinkTarget>;
and you can use the property() cmd to lookup junction/symlinks targets etc.Re: Dealing with symlinks
Thanks! I tried
So I went ahead and tried the LinkShell Extension and it can't deal with that file, too.
Bloody Microsoft, not playing by the rules, it seems.
echo <prop LinkTarget>;
which gave an empty msg and text property("#ResolveJunctionsAll", "C:\Users\mbaas\AppData\Local\Microsoft\WindowsApps\MartinPikryl.WinSCP_tvv458r3h9r5m\WinSCP.exe");
just echos the filename.So I went ahead and tried the LinkShell Extension and it can't deal with that file, too.
Bloody Microsoft, not playing by the rules, it seems.
______________________________________________
Happy user ;-)
Happy user ;-)
Re: Dealing with symlinks
In Total Commander there is a plugin which shows all type of links and their target.
For this case the object Type is identified as "Other MS" and the funny fact is that the target is the path to the 0 byte exe.
C:\Users\myname\AppData\Local\Microsoft\WindowsApps\name-of_the_exe
For this case the object Type is identified as "Other MS" and the funny fact is that the target is the path to the 0 byte exe.
C:\Users\myname\AppData\Local\Microsoft\WindowsApps\name-of_the_exe
Windows 11 Home x64 Version 23H2 (OS Build 22631.3447)
Portable XYplorer (actual version, including betas)
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
Portable XYplorer (actual version, including betas)
Everything 1.5.0.1372a (x64), Everything Toolbar 1.3.3, Listary Pro 6.3.0.73
Re: Dealing with symlinks
Ok, I guess I have the answer: it' an "App execution Alias"! (see here)
______________________________________________
Happy user ;-)
Happy user ;-)