Read Lnk File
-->
LNK File Format 101. LNK is a file extension for a shortcut file used by Microsoft Windows to point to an executable file. Then, have you ever clicked those files? Have you received any alert from your main Norton (or other antivirus) prod. When you click a.lnk file shortcut, it launches the program that is associated with the.exe file that the shortcut refers to. The.lnk files will appear on your computer desktop as an icon with a small, curled arrow. These files can be very useful when you want quick access to an application that you use frequently. Instead of navigating to the program from your start menu, you can simply click the.lnk file on your desktop and the application will launch for you automatically. I'm trying to read the target file/directory of a shortcut (.lnk) file from Python. Is there a headache-free way to do it? The.lnk spec PDF is way over my head. I don't mind using Windows-only APIs. My ultimate goal is to find the '(My) Videos' folder on Windows XP and Vista. A link file has an extension of 'lnk'. A url file has an extension of 'url' and a website file has an extension of 'website'. The shell cannot read web files (filename.website) because it is a text file. The Shell.Application object cannot read these files. Both URL nd LNK files are created and read suing WScript.Shell.
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 |
Read Lnk File Cmd
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.
C# - .NET Read Binary Contents Of .lnk File - Stack Overflow
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.
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 iplg@microsoft.com.
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.
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.
OneDrive Syncing Desktop Files, Turned Them Into .lnk Files ...
Support.For questions and support, please contact dochelp@microsoft.com.