A broken shortcut is a pointer whose target can no longer be resolved. The application, document, network location, or drive letter may have changed even though the .lnk file still exists. This guide shows how to diagnose one shortcut, repair it when the target still exists, and safely clean up many invalid shortcuts without treating every failure as malware.
.lnk file normally removes the pointer, not the application or document it references. Always verify the file type and target first.Broken shortcut or suspicious shortcut?
| Signal | Ordinary broken shortcut | Potentially suspicious shortcut |
|---|---|---|
| Context | An app was uninstalled, a file moved, or a network share is offline | Many USB folders suddenly became shortcuts or the item appeared unexpectedly |
| Target | A familiar file or program path that no longer exists | A command interpreter, script host, unknown executable, or temporary location |
| Behavior | Windows reports that the target was changed or moved | The shortcut returns after deletion or attempts to launch another process |
| Action | Repair, recreate, or remove the shortcut | Do not open it; scan and preserve evidence before removal |
Why Windows shortcuts break
- Uninstalled software: the uninstaller removed the executable but left a Desktop or Start menu link.
- Moved or renamed files: the target path stored in the shortcut is no longer correct.
- Changed drive letters: an external drive that used to be
E:may now beF:. - Unavailable network paths: the server, VPN, mapped drive, or credentials are temporarily unavailable.
- Cloud placeholders: OneDrive or another sync provider may not have the file available on this device.
- Missing working directory or arguments: some applications need a specific Start in folder or command-line option.
- Profile changes: a shortcut can contain a path to an old Windows user profile.
Step 1: inspect the shortcut before changing it
- Right-click the shortcut and choose Properties.
- On the Shortcut tab, review Target, Start in, and any arguments.
- Confirm whether the target path exists in File Explorer.
- Check whether a network share, VPN, cloud account, or removable drive must be connected first.
- If the target is unfamiliar or launches a command interpreter, stop and follow the suspicious .LNK inspection guide.
Do not paste an unfamiliar target or argument string into a terminal. A shortcut can contain a command that is harmless when expected and dangerous when disguised.
Step 2: repair a shortcut whose target still exists
If you know the correct target, select Browse in the shortcut’s Properties window and choose the real executable or document. Confirm the working directory and arguments before selecting Apply. Test the repaired shortcut only after you have verified the target.
For an application, the more reliable repair is often to reinstall or repair the application from its official publisher. That recreates the Start menu registration, icons, working directory, and required arguments together.
Step 3: recreate a simple shortcut
When the old shortcut contains no special arguments, recreate it from the known target:
- Locate the real file or application in File Explorer.
- Right-click it and choose Show more options.
- Select Send to > Desktop (create shortcut), or use Create shortcut where available.
- Compare the new target with the old one before removing the broken shortcut.
For Microsoft Store applications, pin the app from Start instead of trying to build a shortcut to a protected application package path.
Step 4: check the common shortcut locations
- Your Desktop and the Public Desktop.
- Your per-user Start menu Programs folder.
- The all-users Start menu Programs folder.
- Taskbar and Start pins.
- Project folders containing links to moved documents.
- Removable drives whose letter or folder structure changed.
A taskbar pin may remain broken after an application update. Unpin it, launch the verified application from Start, and pin the current executable again.
Step 5: scan many shortcuts safely
Manual repair is best for a few important shortcuts. A scanner is useful after a large software cleanup, profile migration, or drive reorganization. Shortcut Remover can enumerate shortcut files, show their targets and risk signals, and separate invalid entries for review.
- Back up important shortcut folders or create a restore point.
- Select the smallest folder or drive that covers the problem.
- Use a full scan only when you need recursive coverage.
- Check the reported directories, files, shortcuts, access errors, and skipped reparse points.
- Filter results, inspect targets, and remove only shortcuts whose targets are definitely obsolete.
- Use quarantine rather than permanent deletion when you are uncertain.
Deleting thousands of tiny shortcut files does not meaningfully free disk space or guarantee a faster PC. The real benefit is a cleaner interface, fewer dead links, and clearer security review.
Download Shortcut Remover 8.0.0 Learn to filter scan results
When a target exists but the shortcut still fails
Check permissions, working directory, arguments, architecture, and environment variables. A shortcut that points to a network location may fail outside the corporate network. A cloud file may show in Explorer but remain online-only. A target on a removable drive may need a stable drive letter.
Do not “fix” the problem by downloading random replacement executables or DLL files. Obtain application files only from the original publisher or a trusted organization repository.
Frequently asked questions
Does deleting a broken shortcut uninstall the program?
No. A normal shortcut is a pointer. Deleting it does not uninstall the target application.
Why do removed shortcuts return?
An application updater, login script, Group Policy, synchronization tool, or malware may recreate them. Identify the source instead of repeatedly deleting the symptom.
Can Windows automatically repair every broken shortcut?
No. Windows cannot reliably guess where an arbitrary file moved or which arguments an application requires.
Should I remove a shortcut on an offline network drive?
Not until you confirm the target was permanently removed. A temporarily unavailable network path is not necessarily broken.
Related guides: cleaning shortcuts left by uninstalled programs, viewing shortcut targets and arguments, and distinguishing broken shortcuts from shortcut-virus behavior.