Add "Remarks" headings for error references in range [LNK1000, LNK1220]

Rageking8 · web-flow · commit 1a601e97054e · 2025-09-20T22:36:51.000+08:00
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1000.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1000.md
@@ -10,6 +10,8 @@ ms.assetid: 86421b9a-460a-4285-8dce-9b8257d78122
 
 > unknown error; consult documentation for technical support options
 
+## Remarks
+
 Note the circumstances of the error, then try to isolate the problem and create a reproducible test case. For information on how to investigate and report these errors, see [How to report a problem with the Visual C++ toolset or documentation](../../overview/how-to-report-a-problem-with-the-visual-cpp-toolset.md).
 
 You may get this error if you mix standard header files (for example, Windows.h) and your own files. Include a precompiled header, if any, first, then the standard headers, followed by your own header files.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1103.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1103.md
@@ -10,6 +10,8 @@ ms.assetid: c8e9bc54-6a71-471c-899e-6f98122ee3c4
 
 > debugging information corrupt; recompile module
 
+## Remarks
+
 This error can be caused because the compilation was terminated before a valid object file was created.
 
 Recompile the given object file. If recompiling does not correct the problem, note the circumstances of the error, try to isolate the problem, and create a reproducible test case. Then consult the technical-support help file, or the technical-support section in one of your manuals.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1104.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1104.md
@@ -10,6 +10,8 @@ ms.assetid: 9ca6f929-0efc-4055-8354-3cf5b4e636dc
 
 > cannot open file '*filename*'
 
+## Remarks
+
 This error is reported when the linker fails to open a file, either for reading or for writing. The two most common causes of the issue are:
 
 - your program is already running or is loaded in the debugger, and
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1106.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1106.md
@@ -10,6 +10,8 @@ ms.assetid: 528f7e65-04be-4966-b8af-9276837c7cda
 
 > invalid file or disk full: cannot seek to location
 
+## Remarks
+
 The tool could not read or write to `location` in a memory-mapped file.
 
 ### To fix by checking the following possible causes
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1107.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1107.md
@@ -9,10 +9,10 @@ helpviewer_keywords: ["LNK1107"]
 
 > invalid or corrupt file: cannot read at location *address*
 
-The tool couldn't read the file. The file may be corrupt, or have an unexpected file type.
-
 ## Remarks
 
+The tool couldn't read the file. The file may be corrupt, or have an unexpected file type.
+
 LNK1107 can occur if a file passed to the linker or related tools is corrupt. To resolve this issue, rebuild the file.
 
 LNK1107 can also occur if your build process puts an unexpected file type in the list of files passed to the tool. The linker and related tools expect to work on specific file types. For example, the linker can use object files, library files, compiled resources, and manifests to create an executable. It can't create an executable by using source files or DLLs. To resolve this issue, verify that your build process passes only the expected file types to the tool. For example, pass *`.obj`*, *`.lib`*, and *`.res`* files, not *`.cpp`*, *`.h`*, *`.dll`*, or *`.rc`* files.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1113.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1113.md
@@ -10,6 +10,8 @@ ms.assetid: 269ff166-b143-48e9-bdf7-db6a0db59fe4
 
 > invalid machine type type
 
+## Remarks
+
 The machine type specified in the object header is not valid.
 
 This error can be caused if the file is corrupt. Rebuild the object.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1120.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1120.md
@@ -10,6 +10,8 @@ ms.assetid: 56aa7d36-921f-4daf-b44d-cca0d4fb1b51
 
 > *number* unresolved externals
 
+## Remarks
+
 Error LNK1120 reports the number of [unresolved external symbol](linker-tools-error-lnk2001.md#what-is-an-unresolved-external-symbol) errors in the current link.
 
 Each unresolved external symbol first gets reported by a [LNK2001](linker-tools-error-lnk2001.md) or [LNK2019](linker-tools-error-lnk2019.md) error. The LNK1120 message comes last, and shows the unresolved symbol error count.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1123.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1123.md
@@ -9,6 +9,8 @@ helpviewer_keywords: ["LNK1123"]
 
 > failure during conversion to COFF: file invalid or corrupt
 
+## Remarks
+
 Input files must have the Common Object File Format (COFF) format. If an input file is not COFF, the linker automatically tries to convert 32-bit OMF objects to COFF, or runs CVTRES.EXE to convert resource files. This message indicates that the linker could not convert the file. This can also occur when using an incompatible version of CVTRES.EXE from another installation of Visual Studio, the Windows Development Kit, or .NET Framework.
 
 > [!NOTE]
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1127.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1127.md
@@ -10,4 +10,6 @@ ms.assetid: 45404700-1420-4f24-97e1-efb7252ffd8f
 
 > library is corrupt
 
+## Remarks
+
 The library file is corrupt. Rebuild the library.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1136.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1136.md
@@ -10,6 +10,8 @@ ms.assetid: 40c6d909-eb3f-4045-a0fc-4caa2f6db506
 
 > invalid or corrupt file
 
+## Remarks
+
 The input file either has a corrupt header or is zero size or abnormally small.
 
 LNK1136 may also be caused if the file was incorrectly specified as an additional dependency.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1140.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1140.md
@@ -10,6 +10,8 @@ ms.assetid: 468d7651-a7cd-47b9-aead-5bb2fab56121
 
 > too many modules for program database; link with /PDB:NONE
 
+## Remarks
+
 The project contains more than 4096 modules.
 
 ### To fix by using the following possible solutions
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1141.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1141.md
@@ -10,6 +10,8 @@ ms.assetid: 83b78606-6dd3-43a7-88e2-152f5359cbd8
 
 > failure during build of exports file
 
+## Remarks
+
 [LINK](../../build/reference/linking.md) could not build the exports (.exp) file.
 
 Causes of this error include system problems such as insufficient memory and syntax errors in options or module-definition statements.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1143.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1143.md
@@ -10,6 +10,8 @@ ms.assetid: 5dc6b634-d142-4448-b5ea-48e8fb10c10a
 
 > invalid or corrupt file: no symbol for COMDAT section number
 
+## Remarks
+
 This error can be caused if the object file is corrupt.
 
 Rebuild the file.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1152.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1152.md
@@ -10,4 +10,6 @@ ms.assetid: 2523b61a-1359-4612-9c16-7d1f705f32e6
 
 > cannot resolve one or more undecorated symbols
 
+## Remarks
+
 This error is preceded by one warning [LNK4022](../../error-messages/tool-errors/linker-tools-warning-lnk4022.md) for each undecorated symbol that could not be resolved and by at least two warnings [LNK4002](../../error-messages/tool-errors/linker-tools-warning-lnk4002.md) for the duplicate symbols found for the undecorated symbol.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1158.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1158.md
@@ -10,6 +10,8 @@ ms.assetid: 45febf16-d9e1-42db-af91-532e2717fd6a
 
 > cannot run 'filename'
 
+## Remarks
+
 The given executable file called by [LINK](../../build/reference/linking.md) is not in the directory that contains LINK nor in a directory specified in the PATH environment variable.
 
 For example, you will get this error if you try to use the PGOPTIMIZE parameter to the [/LTCG](../../build/reference/ltcg-link-time-code-generation.md) linker option on a machine with a 32-bit operating system.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1164.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1164.md
@@ -10,6 +10,8 @@ ms.assetid: da89765c-affa-4f88-b170-6d6b19a577cf
 
 > section section alignment (number) greater than /ALIGN value
 
+## Remarks
+
 The alignment size for the given section in the object file exceeds the value specified with the [/ALIGN](../../build/reference/align-section-alignment.md) option. The **/ALIGN** value must be a power of 2 and must equal or exceed the section alignment given in the object file.
 
 Either recompile with a smaller section alignment or increase the **/ALIGN** value.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1166.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1166.md
@@ -10,6 +10,8 @@ ms.assetid: d69548a8-0efb-44e1-90b7-b27636a4b575
 
 > cannot adjust code at offset=offset, va=value
 
+## Remarks
+
 LINK was unable to pad the code as required.
 
 Certain instructions are not allowed to cross page boundaries on some processors. LINK attempts to add pads to correct this situation. In this case, LINK could not work around the problem.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1168.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1168.md
@@ -10,6 +10,8 @@ ms.assetid: 97ead151-fd99-46fe-9a1d-7e84dc0b8cc8
 
 > cannot open filename for writing
 
+## Remarks
+
 The linker can't write to `filename`. The file may be in use and its file handle locked by another process, or you may not have write permission for the file, or for the directory or network share it is located in. This error is often caused by a transient condition—for example, a lock held by an anti-virus program, a file search indexing process, or a delay in releasing a lock held by the Visual Studio build system.
 
 To fix this issue, verify that the `filename` file handle is not locked, and that you have write permission for the file. If it is an executable, verify that it is not already running.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1169.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1169.md
@@ -10,6 +10,8 @@ ms.assetid: e079d518-f184-48cd-8b38-969bf137af54
 
 > one or more multiply defined symbols found
 
+## Remarks
+
 The build failed due to multiple definitions of one or more symbols. This error is preceded by error [LNK2005](../../error-messages/tool-errors/linker-tools-error-lnk2005.md).
 
 The [/FORCE](../../build/reference/force-force-file-output.md) or **/FORCE:MULTIPLE** option overrides this error.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1170.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1170.md
@@ -10,6 +10,8 @@ ms.assetid: e079d518-f184-48cd-8b38-969bf137af54
 
 > line in command file contains *maximum-length* or more characters
 
+## Remarks
+
 The build failed because a line in a command response file was too long. A line in an automatically generated response file may be too long for many reasons. For example, this error may occur if the number of object file names is too high. Or, if the combined lengths of the paths included in object file names is too long.
 
 The appropriate fix for this issue depends on the cause. For example, if it's caused by long paths in object file names, you may try to shorten the directory names in the path. Or, move the project tree into a directory closer to the root of the drive. You may want to break up how response files are generated and consumed by your build system, for instance, by generating some code as static libraries.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1179.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1179.md
@@ -10,6 +10,8 @@ ms.assetid: 4b1536d7-0d3d-4f29-a9c1-6fa5cf6cb665
 
 > invalid or corrupt file: duplicate COMDAT 'filename'
 
+## Remarks
+
 An object module contains two or more COMDATs with the same name.
 
 This error can be caused by using [/H](../../build/reference/h-restrict-length-of-external-names.md), which limits the length of external names, and [/Gy](../../build/reference/gy-enable-function-level-linking.md), which packages functions in COMDATs.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1181.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1181.md
@@ -10,6 +10,8 @@ ms.assetid: 984b0db6-e331-4284-b2a7-a212fe96c486
 
 > cannot open input file 'filename'
 
+## Remarks
+
 The linker could not find `filename` because it does not exist or the path was not found.
 
 Some common causes for error LNK1181 include:
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1188.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1188.md
@@ -10,4 +10,6 @@ ms.assetid: 4af574b0-5b41-4580-9a37-52a634add995
 
 > BADFIXUPSECTION:: invalid fixup target 'symbol'; possible zero length section
 
+## Remarks
+
 During a VxD link, the target of a relocation did not have a section. With LINK386 (an older version), an OMF GROUP record (generated by a MASM GROUP directive) may have been used to combine the zero length section with another non-zero length section. COFF format does not support the GROUP directive and zero-length sections. When LINK automatically converts this type of OMF objects to COFF, this error may occur.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1189.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1189.md
@@ -10,6 +10,8 @@ ms.assetid: 40c45302-6967-497e-9a6e-c2ca039fc1ed
 
 > LIBTOOMANYMEMBERS:: library limit of number objects exceeded
 
+## Remarks
+
 The limit of 65535 objects or members in a library has been exceeded.
 
 To fix this issue, split your library into two or more libraries with fewer objects or members.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1196.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1196.md
@@ -10,4 +10,6 @@ ms.assetid: d0c6859b-85aa-45cc-9f5f-fc1f7070ab5a
 
 > invalid or corrupt import object: unknown version
 
+## Remarks
+
 The import library is corrupted. Rebuild the library.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1200.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1200.md
@@ -10,6 +10,8 @@ ms.assetid: 55771145-915e-4006-ac6c-ac702041eb2f
 
 > error reading program database 'filename'
 
+## Remarks
+
 The program database (PDB) could not be read.
 
 This error can be caused by file corruption.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1201.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1201.md
@@ -10,6 +10,8 @@ ms.assetid: 64c3f496-a428-4b54-981e-faa82ef9c8a1
 
 > error writing to program database 'filename'; check for insufficient disk space, invalid path, or insufficient privilege
 
+## Remarks
+
 LINK could not write to the program database (PDB) for the output file.
 
 ### To fix by checking the following possible causes
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1211.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1211.md
@@ -10,6 +10,8 @@ ms.assetid: 607400eb-4180-4892-817f-eedfa628af61
 
 > precompiled type information not found; '*filename*' not linked or overwritten
 
+## Remarks
+
 The *filename* object file, compiled by using [/Yc](../../build/reference/yc-create-precompiled-header-file.md), was not specified in the LINK command or was overwritten.
 
 If you are creating a debug library that uses precompiled headers and if you specify **/Yc** and [/Z7](../../build/reference/z7-zi-zi-debug-information-format.md), Visual C++ generates a precompiled object file that contains debug information. The error occurs only when you store the precompiled object file in a library, use the library to build an executable image, and the object files that are referenced have no transitive references to any of the functions the precompiled object file defines.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1215.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1215.md
@@ -10,6 +10,8 @@ ms.assetid: 0774d8e6-f0c1-4efb-8723-7e1be6863d81
 
 > metadata operation failed (HRESULT) : error
 
+## Remarks
+
 The linker received an error from the .NET runtime while attempting to do a metadata update through the .NET runtime.
 
 `HRESULT` is the HRESULT from the .NET runtime method. `error` is the .NET-supplied text.
diff --git a/docs/error-messages/tool-errors/linker-tools-error-lnk1218.md b/docs/error-messages/tool-errors/linker-tools-error-lnk1218.md
@@ -10,6 +10,8 @@ ms.assetid: bf599350-be03-4344-be43-91e29c4f1556
 
 > warning treated as error; no output file generated
 
+## Remarks
+
 When you link with **/WX**, any linker warnings will be treated as errors, and no output file will be created.
 
 See [/WX (Treat Linker Warnings as Errors)](../../build/reference/wx-treat-linker-warnings-as-errors.md) for more information.
