Windows System Information file - Revision history

Havoc Crow: +cat (XML based file formats)

2025-08-15T14:57:29Z

+cat (XML based file formats)

Havoc Crow: added Win 7 info

2025-08-02T03:22:04Z

added Win 7 info

Havoc Crow: /* Format */ grammar

2025-07-30T12:56:51Z

‎Format: grammar

Havoc Crow: describe format

2025-07-30T12:55:28Z

describe format

Havoc Crow: Created page with "{{FormatInfo |formattype=electronic |subcat=System files |extensions={{ext|nfo}} }} The System Information application in Windows (also known as `msinfo32.exe`) dis..."

2025-07-30T12:37:20Z

Created page with "{{FormatInfo |formattype=electronic |subcat=System files |extensions={{ext|nfo}} }} The System Information application in Windows (also known as <code>msinfo32.exe</code>) dis..."

New page

{{FormatInfo
|formattype=electronic
|subcat=System files
|extensions={{ext|nfo}}
}}
The System Information application in Windows (also known as <code>msinfo32.exe</code>) displays detailed technical information about the system. It allows users to export this data to a '''System Information file''', which by default uses the <code>.nfo</code> extension. System Information files can be reopened in the same application for later viewing. These files can be used for technical diagnostics and troubleshooting.

In Windows 10, the file is encoded in [[plain text]] and structured using [[XML]] syntax.

← Older revision		Revision as of 14:57, 15 August 2025
Line 51:		Line 51:
	== External links ==		== External links ==
	* [https://stackoverflow.com/questions/34070729/parse-a-nfo-file-with-python Stack Overflow: Parse a *.nfo file with python]		* [https://stackoverflow.com/questions/34070729/parse-a-nfo-file-with-python Stack Overflow: Parse a *.nfo file with python]
		+
		+	[[Category:XML based file formats]]

@@ Line 8: / Line 8: @@
 == Format ==
-In Windows 10, an .nfo file is encoded in [[plain text]] and structured using [[XML]] syntax. There doesn't seem to be an official specification, but it has a very simple structure. The data is organized into nested categories and subcategories (same as those displayed in the System Information app), each containing one or more entries represented as rows of data with named columns. These column names correspond to the headers displayed in the System Information app.
+An .nfo file is encoded in [[plain text]] and structured using [[XML]] syntax. There doesn't seem to be an official specification, but it has a very simple structure. The data is organized into nested categories and subcategories (same as those displayed in the System Information app), each containing one or more entries represented as rows of data with named columns. These column names correspond to the headers displayed in the System Information app.
-Here's an example using placeholder values:
+Here's an example file structure, using placeholder values:
 <pre>
 <?xml version="1.0"?>
@@ Line 46: / Line 46: @@
 The category names and column names vary depending on the system language. The file is generated without no indentation, and [https://superuser.com/questions/1855000/is-msinfo32-able-to-read-nfo-files-containing-indentation adding indentation seems to cause slight glitches in file parsing.]
 == External links ==
 * [https://stackoverflow.com/questions/34070729/parse-a-nfo-file-with-python Stack Overflow: Parse a *.nfo file with python]

@@ Line 8: / Line 8: @@
 == Format ==
-In Windows 10, a .nfo file is encoded in [[plain text]] and structured using [[XML]] syntax. There doesn't seem to be an official specification, but it has a very simple structure. The data is organized into nested categories and subcategories (same as those displayed in the System Information app), each containing one or more entries represented as rows of data with named columns. These column names correspond to the headers displayed in the System Information app.
+In Windows 10, an .nfo file is encoded in [[plain text]] and structured using [[XML]] syntax. There doesn't seem to be an official specification, but it has a very simple structure. The data is organized into nested categories and subcategories (same as those displayed in the System Information app), each containing one or more entries represented as rows of data with named columns. These column names correspond to the headers displayed in the System Information app.
 Here's an example using placeholder values: