# Technical Documentation: winsiderss/systeminformer > ℹ️ **Provenance:** Multi-Tier Ingestion · [CodeWiki Reference](https://codewiki.google/github.com/winsiderss/systeminformer) ### Overview (`README.md`)

System Informer

A free, powerful, multi-purpose tool that helps you monitor system resources, debug software and detect malware.
Brought to you by Winsider Seminars & Solutions, Inc.

## System requirements Windows 10 or higher, 32-bit or 64-bit. ## Features * A detailed overview of system activity with highlighting. * Graphs and statistics allow you quickly to track down resource hogs and runaway processes. * Can't edit or delete a file? Discover which processes are using that file. * See what programs have active network connections, and close them if necessary. * Get real-time information on disk access. * View detailed stack traces with kernel-mode, WOW64 and .NET support. * Go beyond services.msc: create, edit and control services. * Small, portable and no installation required. * 100% [Free Software](https://www.gnu.org/philosophy/free-sw.en.html) ([MIT](https://opensource.org/licenses/MIT)) ## Building the project Requires Visual Studio (2022 or later). After cloning the repo run `build_init.cmd` located in the `build` directory, this doesn't not run again unless there are updates to the tools or third party libraries. Execute `build_release.cmd` located in the `build` directory to compile the project or load the `SystemInformer.sln` and `Plugins.sln` solutions if you prefer building the project using Visual Studio. You can download the free [Visual Studio Community Edition](https://www.visualstudio.com/vs/community/) to build the System Informer source code. See the [build readme](./build/README.md) for more information or if you're having trouble building. ## Enhancements/Bugs Please use the [GitHub issue tracker](https://github.com/winsiderss/systeminformer/issues) for reporting problems or suggesting new features. ## Settings If you are running System Informer from a USB drive, you may want to save System Informer's settings there as well. To do this, create a blank file named "SystemInformer.exe.settings.xml" in the same directory as SystemInformer.exe. You can do this using Windows Explorer: 1. Make sure "Hide extensions for known file types" is unticked in Tools > Folder options > View. 2. Right-click in the folder and choose New > Text Document. 3. Rename the file to SystemInformer.exe.settings.xml (delete the ".txt" extension). --- ### Overview (`KSystemInformer/README.md`) # System Informer Kernel - optimizes retrieval of information from the system - enables broader inspection into the system - informs of system activity in realtime - assists in removal of malware ## Security [Security Policies and Procedures](../SECURITY.md) Because the information exposed through the driver enables, by design, broader access into the system. Access is strictly limited to verified callers. Access is restricted based on the state of the calling process. This involves signing, privilege, and other state checks. If the client does not meet the state requirements they are denied access. Any binaries built with the intention of loading into System Informer must have a `.sig` from the key pair integrated into the build process and driver. Or be signed by Microsoft or an anti-malware vendor. Loading of unsigned modules will restrict access to the driver. Third-party plugins are supported, however when they are loaded access to the driver will be restricted as they are not signed. The driver tracks verified clients, restricts access by other actors on the system, and denies access if the process is tampered with. The intention is to discourage exploitation of the client when the driver is active. If tampering or exploitation is detected the client is denied access. ## Development Developers may suppress protections and state requirements by disabling secure boot (if applicable) then enabling debug and test signing mode. Doing this will permit the client process to be debugged and enables use of test signing keys. ``` bcdedit /debug on bcdedit /set testsigning on ``` Developers may generate their own key pair for use in their environment. 1. execute `tools\CustomSignTool\bin\Release64\CustomSignTool.exe createkeypair kph.key public.key` 2. copy `kph.key` into `tools\CustomSignTool\resources` 3. copy the bytes for `public.key` into the `KphpPublicKeys` array in [verify.c](verify.c) - `KphKeyTypeProd` does not require debug and test signing enablement - `KphKeyTypeTest` requires debug and test signing enablement 4. regenerate dynamic data `tools\CustomBuildTool\bin\Release\amd64\CustomBuildTool.exe -dyndata` 5. rebuild the kernel _and_ user components It's important to regenerate the dynamic data and build the kernel and user components after creating and placing the new key pair. The driver uses the public key to validate the dynamic data and user mode binaries. Neglecting to do this will result in failures to load or connect to the driver. Once these steps are completed builds of System Informer components will generate a `.sig` file next to the output binaries. And the developer built driver will use the specified key when doing verification checks. Any plugins not built through the regular build process must also have their own `.sig`. --- ### Overview (`build/README.md`) # Building System Informer General rule of thumb is to run `build_init.cmd` then `build_release.cmd` after cloning the repo. After running `build_init.cmd` you generally don't need to run it again unless there are updates to the tools or third party libraries. If you're having trouble, when in doubt, run `build_init.cmd`. You may also build the solutions directly in Visual Studio. For a Clang undefined behavior sanitizer build of the user-mode Debug targets, run `build_ubsan.cmd` from this directory. It requires CMake, Ninja, and `clang-cl` in a Visual Studio installation. The script configures and builds an isolated `build-debug-ubsan-clang-msvc-64` tree, with binaries in `bin-cmake-ubsan`. Pass `generate` or `build` to run only one step. Kernel targets are not part of the CMake build. UBSan uses trap mode: a detected violation stops the process without requiring the Clang UBSan reporting runtime. ## Errors, Problems, Gotchas This section contains common errors, problems, and gotchas when building System Informer. If you're having trouble building then the information here is likely to resolve your problem. ### LINK : fatal error C1047 (thirdparty.lib) TL;DR - run `build_thirdparty.cmd` This error occurs because `thirdparty.lib` was built using a different compiler than the one in the environment. To resolve this in your environment run `build_thirdparty.cmd`. ### Built plugins not loading with kernel driver enabled It is possible to load built plugins with the driver enabled, but there is an intentional security mitigation to protect the driver from abuse. Please refer to the [kernel driver readme](../KSystemInformer/README.md) for more information. You may also disable the advanced setting for image load denial, but access to the driver will be restricted with unsigned plugins loaded. --- ### Overview (`phnt/README.md`) This collection of Native API header files has been maintained since 2009 for the Process Hacker project, and is the most up-to-date set of Native API definitions that I know of. I have gathered these definitions from official Microsoft header files and symbol files, as well as a lot of reverse engineering and guessing. See `phnt.h` for more information. ## Usage First make sure that your program is using the latest Windows SDK. These header files are designed to be used by user-mode programs. Instead of `#include `, place ``` #include #include ``` at the top of your program. The first line provides access to the Win32 API as well as the `NTSTATUS` values. The second line provides access to the entire Native API. By default, only definitions present in Windows XP are included into your program. To change this, use one of the following: ``` #define PHNT_VERSION PHNT_WINDOWS_XP // Windows XP #define PHNT_VERSION PHNT_WINDOWS_SERVER_2003 // Windows Server 2003 #define PHNT_VERSION PHNT_WINDOWS_VISTA // Windows Vista #define PHNT_VERSION PHNT_WINDOWS_7 // Windows 7 #define PHNT_VERSION PHNT_WINDOWS_8 // Windows 8 #define PHNT_VERSION PHNT_WINDOWS_8_1 // Windows 8.1 #define PHNT_VERSION PHNT_WINDOWS_10 // Windows 10 #define PHNT_VERSION PHNT_WINDOWS_11 // Windows 11 ``` --- ### Overview (`tools/thirdparty/SymCrypt/README.md`) # Introduction SymCrypt is the core cryptographic function library currently used by Windows. ## History The library was started in late 2006 with the first sources committed in Feb 2007. Initially the goal was limited to implement symmetric cryptographic operations, hence the name. Starting with Windows 8, it has been the primary crypto library for symmetric algorithms. In 2015 we started the work of adding asymmetric algorithms to SymCrypt. Since the 1703 release of Windows 10, SymCrypt has been the primary crypto library for all algorithms in Windows. ## Goals Like any engineering project, SymCrypt is a compromise between conflicting requirements: - Provide safe implementations of the cryptographic algorithms needed by Microsoft products. - Run on all CPU architectures supported by Windows. - Good performance. - Minimize maintenance cost. - Support FIPS 140 certification of products using SymCrypt. - Provide high assurance in the proper functionality of the library. # Cloning the Repo In some of our Linux modules, SymCrypt uses [Jitterentropy](https://github.com/smuellerDD/jitterentropy-library) as a source of FIPS-certifiable entropy. To build these modules, you will need to ensure that the jitterentropy-library submodule is also cloned. You can do this by running `git submodule update --init` after cloning. The `unittest/SymCryptDependencies` submodule provides the RSA32 and msbignum implementations which are used as benchmarks in the unit tests when compiled on Windows. Due to licensing restrictions, we cannot release these libraries publicly, so this submodule will only be cloneable by Microsoft employees with access to our private Azure DevOps repository. If you are external to Microsoft, you can ignore this submodule. It is only used in the unit tests and does not change the behavior of the SymCrypt product code. # Building The easiest way to get started building SymCrypt is to use the Python build script, `scripts/build.py`. You can run it with the `--help` argument to get help about which arguments are required and what each one does. For detailed build instructions, including alternative ways to build, see [BUILD.md](BUILD.md). # Testing The SymCrypt unit test runs extensive functional tests on the SymCrypt library. On Windows it also compares results against on other implementations such as the Windows APIs CNG and CAPI, and the older crypto libraries rsa32 and msbignum, if they are available. It also provides detailed performance information. After a successful build, you can use the `scripts/test.py` helper script to run the unit tests. # Versioning and Servicing As of version 101.0.0, SymCrypt uses the version scheme defined by the [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) specification. This means: - Major version changes introduce ABI and/or API breaking changes (including behavior changes) - Minor version changes introduce backwards compatible additional functionality or improvements, and/or bug fixes - Patch version changes introduce backwards compatible bug fixes The initial open source release started at version 100 for compatibility with our previous internal versioning scheme. Regarding servicing, our strong recommendation is that distro vendors and application developers regularly update to the latest version of SymCrypt and SymCrypt engine for both security fixes and functionality/performance improvements. We take care to maintain a stable API and ABI for SymCrypt and have a suite of strong regression tests, and staying on the current version prevents the need for complex and potential riskier backports. # Security Bugs If you believe you have found a problem that affects the security of this code, please do **NOT** create an issue or pull request, but instead email your comments to secure@microsoft.com. See [SECURITY.md](SECURITY.md) for more info. # Contribute We love to receive comments and suggestions. Unfortunately we cannot accept external code contributions except in specific circumstances from vetted partners with whom we have a pre-arranged agreement. Cryptographic code is considered highly sensitive by many of our large customers. We have some very big customers who put great value in the assurance of the crypto code used in their organization. By restricting the coding to a handful of employees we can greatly reduce the (perceived) risk of malicious contributions. This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. --- ### Tools Thirdparty 7zip DOC License (`tools/thirdparty/7zip/DOC/License.txt`) 7-Zip source code ~~~~~~~~~~~~~~~~~ License for use and distribution ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 7-Zip Copyright (C) 1999-2026 Igor Pavlov. The licenses for files are: - CPP/7zip/Compress/Rar* files: the "GNU LGPL" with "unRAR license restriction" - CPP/7zip/Compress/LzfseDecoder.cpp: the "BSD 3-clause License" - C/ZstdDec.c: the "BSD 3-clause License" - C/Xxh64.c: the "BSD 2-clause License" - Some files are "public domain" files, if "public domain" status is stated in source file. - the "GNU LGPL" for all other files. If there is no license information in some source file, that file is under the "GNU LGPL". The "GNU LGPL" with "unRAR license restriction" means that you must follow both "GNU LGPL" rules and "unRAR license restriction" rules. GNU LGPL information -------------------- This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, you can get a copy of the GNU Lesser General Public License from http://www.gnu.org/ BSD 3-clause License in 7-Zip code ---------------------------------- The "BSD 3-clause License" is used for the following code in 7z.dll 1) LZFSE data decompression. CPP/7zip/Compress/LzfseDecoder.cpp. That code was derived from the code in the "LZFSE compression library" developed by Apple Inc, that also uses the "BSD 3-clause License". 2) ZSTD data decompression. C/ZstdDec.c that code was developed using original zstd decoder code as reference code. The original zstd decoder code was developed by Facebook Inc, that also uses the "BSD 3-clause License". Copyright (c) 2015-2016, Apple Inc. All rights reserved. Copyright (c) Facebook, Inc. All rights reserved. Copyright (c) 2023-2026 Igor Pavlov. Text of the "BSD 3-clause License" ---------------------------------- Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. --- BSD 2-clause License in 7-Zip code ---------------------------------- The "BSD 2-clause License" is used for the XXH64 code in 7-Zip. C/Xxh64.c XXH64 code in 7-Zip was derived from the original XXH64 code developed by Yann Collet. Copyright (c) 2012-2021 Yann Collet. Copyright (c) 2023-2026 Igor Pavlov. Text of the "BSD 2-clause License" ---------------------------------- Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. --- unRAR license restriction ------------------------- The decompression engine for RAR archives was developed using source code of unRAR program. All copyrights to original unRAR code are owned by Alexander Roshal. The license for original unRAR code has the following restriction: The unRAR sources cannot be used to re-create the RAR compression algorithm, which is proprietary. Distribution of modified unRAR sources in separate form or as a part of other software is permitted, provided that it is clearly stated in the documentation and source comments that the code may not be used to develop a RAR (WinRAR) compatible archiver. -- --- ### Tools Thirdparty 7zip DOC Copying (`tools/thirdparty/7zip/DOC/copying.txt`) GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run. GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library. 4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. , 1 April 1990 Ty Coon, President of Vice That's all there is to it! --- ### Tools Thirdparty 7zip DOC Readme (`tools/thirdparty/7zip/DOC/readme.txt`) 7-Zip 26.04 Sources ------------------- 7-Zip is a file archiver for Windows. 7-Zip Copyright (C) 1999-2026 Igor Pavlov. License Info ------------ 7-Zip is free software distributed under the GNU LGPL (except for unRar code). Also some code is licensed under the "BSD 3-clause License". Read "License.txt" for more information about license. Notes about unRAR license: Please check main restriction from unRar license: 2. The unRAR sources may be used in any software to handle RAR archives without limitations free of charge, but cannot be used to re-create the RAR compression algorithm, which is proprietary. Distribution of modified unRAR sources in separate form or as a part of other software is permitted, provided that it is clearly stated in the documentation and source comments that the code may not be used to develop a RAR (WinRAR) compatible archiver. In brief it means: 1) You can compile and use compiled files under GNU LGPL rules, since unRAR license almost has no restrictions for compiled files. You can link these compiled files to LGPL programs. 2) You can fix bugs in source code and use compiled fixed version. 3) You can not use unRAR sources to re-create the RAR compression algorithm. LZMA SDK -------- This package also contains some files from LZMA SDK You can download LZMA SDK from: http://www.7-zip.org/sdk.html LZMA SDK is written and placed in the public domain by Igor Pavlov. How to compile in Windows ------------------------- To compile the sources to Windows binaries you need Visual Studio compiler and/or Windows SDK. You can use latest Windows Studio 2017/2019/2022 to compile binaries for x86, x64, arm64 and arm platforms. Also you can use old compilers for some platforms: x86 : Visual C++ 6.0 with Platform SDK x64 : Windows Server 2003 R2 Platform SDK ia64 (itanium) : Windows Server 2003 R2 Platform SDK arm for Windows CE : Standard SDK for Windows CE 5.0 If you use MSVC6, specify also Platform SDK directories at top of directories lists: Tools / Options / Directories - Include files - Library files Also you need Microsoft Macro Assembler: - ml.exe for x86 - ml64.exe for x64 You can use ml.exe from Windows SDK for Windows Vista or some later versions. There are two ways to compile 7-Zip binaries: 1) via makefile in command line. 2) via dsp file in Visual Studio. The dsp file compiling can be used for development and debug purposes. All final 7-Zip binaries are compiled via makefiles, that provide best optimization options. How to compile with makefile in Windows --------------------------------------- Some macronames can be defined for compiling with makefile: PLATFORM with possible values: x64, x86, arm64, arm, ia64 OLD_COMPILER for old VC compiler, like MSCV 6.0. MY_DYNAMIC_LINK for dynamic linking to the run-time library (msvcrt.dll). The default makefile option is static linking to the run-time library. To compile all 7-Zip files for x64 with Visual Studio 2022, use the following command sequence: cd SRC\CPP\7zip %comspec% /k "C:\Program Files\VS2022\VC\Auxiliary\Build\vcvars64.bat" nmake You can use another "vcvars*.bat" files from "VS2022\VC\Auxiliary\Build" directory to compile for other platforms: vcvars64.bat vcvarsamd64_arm64.bat vcvarsamd64_x86.bat Also you can compile single binary from directory with related project. For example, to compile 7za.exe, use the following command sequence: cd SRC\CPP\7zip\Bundles\Alone\ nmake Compiling 7-Zip for Unix/Linux ------------------------------ There are several options to compile 7-Zip with different compilers: gcc and clang. Also 7-Zip code contains two versions for some parts of code: in C and in Assembler. So if you compile the version with Assembler code, you will get faster 7-Zip binary. 7-Zip's assembler code uses the following syntax for different platforms: 1) x86 and x86-64 (AMD64): MASM syntax. Now there are 3 programs that supports MASM syntax in Linux. ' 'Asmc Macro Assembler, JWasm, and UASM. Note that JWasm now doesn't support some cpu instructions used in 7-Zip. So you must install Asmc Macro Assembler in Linux or UASM, if you want to compile fastest version of 7-Zip x86 and x86-64: https://github.com/nidud/asmc https://github.com/Terraspace/UASM 2) arm64: GNU assembler for ARM64 with preprocessor. That systax is supported by GCC and CLANG for ARM64. There are different binaries that can be compiled from 7-Zip source. There are 2 main files in folder for compiling: makefile - that can be used for compiling Windows version of 7-Zip with nmake command makefile.gcc - that can be used for compiling Linux/macOS versions of 7-Zip or Windows version with MINGW (GCC) with make command. At first you must change the current folder to folder that contains `makefile.gcc`: cd CPP/7zip/Bundles/Alone2 Then you can compile `makefile.gcc` with the command: make -j -f makefile.gcc Also there are additional "*.mak" files in folder "CPP/7zip/" that can be used to compile 7-Zip binaries with optimized code and optimizing options. To compile with GCC without assembler: cd CPP/7zip/Bundles/Alone2 make -j -f ../../cmpl_gcc.mak To compile with CLANG without assembler: make -j -f ../../cmpl_clang.mak To compile 7-Zip for x86-64 with asmc assembler: make -j -f ../../cmpl_gcc_x64.mak To compile 7-Zip for arm64 with assembler: make -j -f ../../cmpl_gcc_arm64.mak To compile 7-Zip for arm64 for macOS: make -j -f ../../cmpl_mac_arm64.mak Also you can change some compiler options in the "mak" files: cmpl_gcc.mak var_gcc.mak warn_gcc.mak makefile.gcc supports some variables that can change compile options USE_JWASM=1 use JWasm assembler instead of Asmc. Note that JWasm doesn't support AES instructions. So AES code from C version AesOpt.c will be used instead of assembler code from AesOpt.asm. If you want to use UASM for x86-64 compiling, you can change 7zip_gcc.mak, or send IS_X64=1 USE_ASM=1 MY_ASM="$UASM" to make command calling: UASM="$PWD/GccUnixR/uasm" cd "7zip-src/CPP/7zip/Bundles/Alone2" make -f makefile.gcc -j IS_X64=1 USE_ASM=1 MY_ASM="$UASM" DISABLE_RAR=1 removes whole RAR related code from compilation. DISABLE_RAR_COMPRESS=1 removes "not fully free" code of RAR decompression codecs from compilation. RAR decompression codecs in 7-Zip code has some additional license restrictions, that can be treated as not fully compatible with free-software licenses. DISABLE_RAR_COMPRESS=1 allows to exclude such "not-fully-free" RAR code from compilation. if DISABLE_RAR_COMPRESS=1 is specified, 7-zip will not be able to decompress files from rar archives, but 7-zip still will be able to open rar archives to get list of files or to extract files that are stored without compression. if DISABLE_RAR=1 is specified, 7-zip will not be able to work with RAR archives. 7-Zip and p7zip =============== Now there are two different ports of 7-Zip for Linux/macOS: 1) p7zip - another port of 7-Zip for Linux, made by an independent developer. The latest version of p7zip now is 16.02, and that p7zip 16.02 is outdated now. http://sourceforge.net/projects/p7zip/ 2) 7-Zip for Linux/macOS - this package - it's new code with all changes from latest 7-Zip for Windows. These two ports are not identical. Note also that some Linux specific things can be implemented better in p7zip than in new 7-Zip for Linux. Notes: ------ 7-Zip consists of COM modules (DLL files). But 7-Zip doesn't use standard COM interfaces for creating objects. Look at 7zip\UI\Client7z folder for example of using DLL files of 7-Zip. Some DLL files can use other DLL files from 7-Zip. If you don't like it, you must use standalone version of DLL. To compile standalone version of DLL you must include all used parts to project and define some defs. For example, 7zip\Bundles\Format7z is a standalone version of 7z.dll that works with 7z format. So you can use such DLL in your project without additional DLL files. Description of 7-Zip sources package ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ DOC Documentation --- readme.txt - Readme file src-history.txt - Sources history 7zC.txt - 7z ANSI-C Decoder description 7zFormat.txt - 7z format description Methods.txt - Compression method IDs lzma.txt - LZMA compression description License.txt - license information copying.txt - GNU LGPL license unRarLicense.txt - License for unRAR part of source code 7zip.wxs - installer script for WIX 7zip.hhp - html help project file Asm - Source code in Assembler : optimized code for CRC, SHA, AES, LZMA decoding. C - Source code in C CPP - Source code in C++ Common common files for C++ projects Windows common files for Windows related code 7zip Common Common modules for 7-zip Archive files related to archiving Bundle Modules that are bundles of other modules (files) Alone 7za.exe: Standalone version of 7-Zip console that supports only 7z/xz/cab/zip/gzip/bzip2/tar. Alone2 7zz.exe: Standalone version of 7-Zip console that supports all formats. Alone7z 7zr.exe: Standalone version of 7-Zip console that supports only 7z (reduced version) Fm Standalone version of 7-Zip File Manager Format7z 7za.dll: .7z support Format7zExtract 7zxa.dll: .7z support, extracting only Format7zR 7zr.dll: .7z support, reduced version Format7zExtractR 7zxr.dll: .7z support, reduced version, extracting only Format7zF 7z.dll: all formats LzmaCon lzma.exe: LZMA compression/decompression SFXCon 7zCon.sfx: Console 7z SFX module SFXWin 7z.sfx: Windows 7z SFX module SFXSetup 7zS.sfx: Windows 7z SFX module for Installers Compress files for compression / decompression Crypto files for encryption / decryption UI Agent Intermediary modules for FAR plugin and Explorer plugin Client7z Test application for 7za.dll Common Common UI files Console 7z.exe : Console version Explorer 7-zip.dll: 7-Zip Shell extension Far plugin for Far Manager FileManager 7zFM.exe: 7-Zip File Manager GUI 7zG.exe: 7-Zip GUI version --- Igor Pavlov http://www.7-zip.org --- --- METRICS --- - Files Extracted: 8 - Estimated Token Budget: ~14783 tokens - Canonical Reference: https://codewiki.google/github.com/winsiderss/systeminformer