ClearLNK

Whether you have recently upgraded your operating system, installed or remove drivers you no longer use or are dealing with a malware infection, there are times where your file association become erroneous and results in having all your programs featuring an LNK extension.
ClearLNK is a utility that enables you to address this issue by deleting the arguments of the object that are faulty and fixing the icon of the shortcut.

It can cure or delete the non-functional shortcut

The program does not require advanced installation or configuration and you can use it as soon as you download it to your computer. The idea behind the application is to provide you with a direct way to fix shortcuts that are broken due to a wide variety of reasons, including harmful software.
Generally speaking, addressing this issue entails identifying the faulty registry responsible for this and recovering it via the System Restore function. The app spare you all this hassle and allows you to clean shortcuts by dragging and dropping them over the app. It is important to note that the shortcuts that cannot be fixed are going to be deleted.

Provides you with two options for cleaning the shortcuts

As previously mentioned, one method of using the utility implies dragging and dropping a list of broken LNK files over the shortcut. However, you will be happy to learn that you can also copy the list of shortcuts directly or from clipboard to the window and then hit the Cure button.
Regardless of the method, you should bear in mind that the application creates a log folder where all cleaning sessions are stored along with the date where they occur.
Take note that the program can solely fix incorrect objects of browser and application shortcuts. Consequentially, URLs, websites, PIF, APPREF-MS, application, browsers and ICO files are going to be wiped.

A handy tool for cleaning infected and non-functional shortcuts

In the eventuality that you are trying to start applications from their desktop shortcuts without any success, then you can try to address the registry error responsible using ClearLNK.