-->
![Lnk files forensic Lnk files forensic](/uploads/1/1/2/1/112132557/631467480.jpg)
Somehow I went to open a shortcut and Windows couldn't find the target but instead of pointing the shortcut to the.exe it pointed the.lnk file handler to the.exe, so now all my.lnk files are trying to be opened by the borderlands game. What's going on? I'm guessing I can do it by resetting the.lnk entry in HKEYCLASSESROOT, but I don't know what to set it to. And even trying the 'open with' on a pdf file, it also is not on the options list, and navigating to the.lnk file (the shortcut in the start menu), that won't do an association either - First the link is not shown, and then in the chooser window selecting 'all file types', it shows up, but selecting it responds, 'This app cannot run on your PC'. I have the issue, but none of the answers actually say 'associate program XYZ' with the.lnk file type. I think my issue is that there is an entry in the file association table, so every 'shortcut' wants to open with the associated program.
An LNK file is a shortcut or 'link' used by Windows as a reference to an original file, folder, or application similar to an alias on the Macintosh platform. It contains the shortcut target type, location, and filename as well as the program that opens the target file and an optional shortcut key.
Specifies the Shell Link Binary File Format, which containsinformation that can be used to access another data object. The Shell LinkBinary File Format is the format of Windows files with the extension'LNK'.
This page and associated content may be updatedfrequently. We recommend you subscribe to the RSSfeed to receive update notifications.
Published Version
Date | Protocol Revision | Revision Class | Downloads |
---|---|---|---|
9/12/2018 | 5.0 | Major | PDF | DOCX | Diff |
Previous Versions
Date | Protocol Revision | Revision Class | Downloads |
---|---|---|---|
9/15/2017 | 4.0 | Major | PDF | DOCX | Errata | Diff |
6/1/2017 | 3.0 | None | PDF | DOCX | Diff |
7/14/2016 | 3.0 | None | PDF | DOCX | Diff |
10/16/2015 | 3.0 | None | PDF | DOCX |
6/30/2015 | 3.0 | Major | PDF | DOCX |
5/15/2014 | 2.0 | None | PDF | DOCX |
2/13/2014 | 2.0 | None | PDF | DOCX |
11/14/2013 | 2.0 | None | PDF | DOCX |
8/8/2013 | 2.0 | Major | PDF | DOCX |
1/31/2013 | 1.2 | None | |
10/25/2012 | 1.2 | None | |
7/12/2012 | 1.2 | None | |
3/30/2012 | 1.2 | None | |
12/16/2011 | 1.2 | None | |
9/23/2011 | 1.2 | None | |
6/17/2011 | 1.2 | Minor | |
5/6/2011 | 1.1 | None | |
3/25/2011 | 1.1 | None | |
2/11/2011 | 1.1 | None | |
1/7/2011 | 1.1 | None | |
11/19/2010 | 1.1 | None | |
10/8/2010 | 1.1 | None | |
8/27/2010 | 1.1 | Minor | |
7/16/2010 | 1.0 | New |
Preview Versions
From time to time, Microsoft maypublish a preview, or pre-release, version of an Open Specifications technicaldocument for community review and feedback. To submit feedback for a previewversion of a technical document, please follow any instructions specified forthat document. If no instructions are indicated for the document, pleaseprovide feedback by using the Open Specification Forums.
The preview period for a technical document varies.Additionally, not every technical document will be published for preview.
A preview version of this document may beavailable on the WindowsProtocols - Preview Documents page. After the preview period, themost current version of the document is available on this page.
Development Resources
Findresources for creating interoperable solutions for Microsoft software,services, hardware, and non-Microsoft products:
Plugfestsand Events, Test Tools,DevelopmentSupport, and Open SpecificationsDev Center.
.lnk File Association Registry Fix
Intellectual Property Rights Notice for Open Specifications Documentation
- Technical Documentation. Microsoft publishes Open Specificationsdocumentation (“this documentation”) for protocols, file formats, dataportability, computer languages, and standards support. Additionally, overviewdocuments cover inter-protocol relationships and interactions.
- Copyrights. This documentation is covered by Microsoftcopyrights. Regardless of any other terms that are contained in the terms ofuse for the Microsoft website that hosts this documentation, you can makecopies of it in order to develop implementations of the technologies that aredescribed in this documentation and can distribute portions of it in yourimplementations that use these technologies or in your documentation asnecessary to properly document the implementation. You can also distribute inyour implementation, with or without modification, any schemas, IDLs, or codesamples that are included in the documentation. This permission also applies toany documents that are referenced in the Open Specifications documentation.
- No Trade Secrets. Microsoft does not claim any tradesecret rights in this documentation.
- Patents. Microsoft has patents that might cover yourimplementations of the technologies described in the Open Specificationsdocumentation. Neither this notice nor Microsoft's delivery of this documentationgrants any licenses under those patents or any other Microsoft patents.However, a given Open Specifications document might be covered by the MicrosoftOpen SpecificationsPromise or the Microsoft CommunityPromise. If you would prefer a written license, or if thetechnologies described in this documentation are not covered by the OpenSpecifications Promise or Community Promise, as applicable, patent licenses areavailable by contacting [email protected].
- License Programs. To see all of the protocols in scopeunder a specific license program and the associated patents, visit the Patent Map.
- Trademarks. The names of companies and products containedin this documentation might be covered by trademarks or similar intellectualproperty rights. This notice does not grant any licenses under those rights.For a list of Microsoft trademarks, visit www.microsoft.com/trademarks.
- Fictitious Names. The example companies, organizations,products, domain names, email addresses, logos, people, places, and events thatare depicted in this documentation are fictitious. No association with any realcompany, organization, product, domain name, email address, logo, person,place, or event is intended or should be inferred.
Reservation of Rights. All otherrights are reserved, and this notice does not grant any rights other than asspecifically described above, whether by implication, estoppel, or otherwise.
![Lnk files forensic Lnk files forensic](/uploads/1/1/2/1/112132557/631467480.jpg)
Lnk File Association
Tools.The Open Specifications documentation does not require the use of Microsoftprogramming tools or programming environments in order for you to develop animplementation. If you have access to Microsoft programming tools andenvironments, you are free to take advantage of them. Certain OpenSpecifications documents are intended for use in conjunction with publiclyavailable standards specifications and network programming art and, as such,assume that the reader either is familiar with the aforementioned material orhas immediate access to it.
Support.For questions and support, please contact [email protected].
Restoring file associations for shortcuts, folders and user files, setting up default apps and resetting associations.File associations suggest comparing the file type to the program which will execute this file. Due to failures or Windows errors, such associations may be disrupted.Contents:
- To Recover File Associations in Windows 10
- File Associations For Ordinary Files
- Associations of Shortcuts, Folders and Executable Files
To Recover File Associations in Windows 10
File Associations For Ordinary Files
- Use the menu item «Open with». Right-click on the file, the association for which needs to be changed. From the list of suggested programs, select the application that suits your needs or look for another one.
- Launch Control Panel / Default programs / Set associations. To see which program opens this file type by default, click on the corresponding file extension. To change the default program, click on «Change program».
- Launch Settings / System / Default applications. At the bottom of the window that opens, select Choose default apps by file type.
Associations of Shortcuts, Folders and Executable Files
The methods described above are good when you deal with ordinary files (pictures, documents, audio files or videos etc). If folder, shortcut or exe.file associations are disrupted in Windows 10, you can correct such errors with the help of Registry Editor.Advanced users can do it manually. However, to save you the trouble of entering manually the corresponding values into the registry, you can also use ready-made .reg files which are meant to enter data into Windows registry.- To correct the EXE file associations;
- To correct the LNK file associations;
Download such files and run them, or right-click on the required file and choose “Merge”.Agree to the security warning by clicking “Run”.Confirm making changes to the registry by clicking on “Yes” in the next window.After that close the registry editor and restart the computer. As a result, associations for .exe and .lnk files should start working just as they did before.If you have activated automatic creation of system restore points before, then you could correct the error of file associations much quicker by using these restore points.Have you managed to recover your files associations? Leave your feedback and ask questions in your comments.