How to resolve broken shortcuts?

[Helmet6993]

HI. I'm using Alpha1.5.
I've already setup shortcut links in the column and used a wildcard search to find all my .lnk file.
I'm basically launching to test each shortcut and then opening path to replace the broken .lnk with a new .lnk.
But I have 1000 shortcuts so this is time-consuming.

1. How do I quickly paste in the correct link into the data that shows under the shortcut target column?

2. Is there a more efficient way to resolve broken shortcuts?

[void]

To show lnk files where the target doesn't exist:

Code: Select all

*.lnk !exists($shortcut-target:)

Formulas

How do I quickly paste in the correct link into the data that shows under the shortcut target column?

Right click the lnk file and click Properties.
Fix the target here.
Everything doesn't support editing properties directly. yet...

[Helmet6993]

Code: Select all

*.lnk !exists($shortcut-target:)

Formulas

Thanks, I used this and I tried the links it showed, but they were working.

[void]

!exists($shortcut-target:)

will only work for shortcut-targets that exist in your index.

Are the targets outside your indexed filenames?

[Helmet6993]

!exists($shortcut-target:)

will only work for shortcut-targets that exist in your index.

Are the targets outside your indexed filenames?

I don't understand what to put in the bracketed target.
The Drive containing all my shortcuts and most of the target drives they link to is also indexed.

[void]

Nothing, leave it as literally:

!exists($shortcut-target:)

Everything will automatically replace $shortcut-target: with the target from the lnk file.

[Helmet6993]

Nothing, leave it as literally:

!exists($shortcut-target:)

Everything will automatically replace $shortcut-target: with the target from the lnk file.

I still don't understand the intent behind the search term.
For example, if my broken MysteryApp.lnk points to My$t3ry App 5.2.exe, then what will happen once I enter that search, and what will I need to do immediately afterwards?

[void]

!exists($shortcut-target:)

will show lnk files where the target doesn't exist.

You can then manually fix these lnks.

[Helmet6993]

!exists($shortcut-target:)

will show lnk files where the target doesn't exist.

You can then manually fix these lnks.

Okay thanks. amongst the broken *.lnk files with typical directory-based targets, there are also working *.lnks with atypical targets, which has caused confusion:

*.lnk files with atypical targets include the following formats;

search-ms:displayname=%20Search%20programs%20and%20files&crumb=System.Generic.String%3A(advanced%20shar)&crumb=location:%3A%3A{DAF95313-E44D-46AF-BE1B-CBACEA2C3065}\Manage advanced sharing settings

shell:::{AD1405D2-30CF-4877-8468-1EE1C52C759F}\Apps\B9ECED6F.ASUSPCAssistant_qmba6cd70vzyy!App

[void]

Consider ignoring those types of targets with the following search:

Code: Select all

*.lnk !shortcut-target:search-ms: !shortcut-target:"shell:" !exists($shortcut-target:)

[Helmet6993]

Consider ignoring those types of targets with the following search:

Code: Select all

*.lnk !shortcut-target:search-ms: !shortcut-target:"shell:" !exists($shortcut-target:)

There was 1-2 working .lnk directory-based shortcuts that defied the formula, but other than than it was a lot cleaner!
TYSM!