> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/hacking-tools/windows/windows-enumeration.md).
# Windows Enumeration
Windows local enumeration commands for users, privileges, groups, services, processes, network state, and system context.
### Metasploit Windows Enumeration
To find privilege escalation exploits based on kernel vulnerabilities, we can use **multi/recon/local/\_exploit/\_suggester** in Metasploit, a module that analyzes kernel version to identify potential exploits.
```bash
use multi/recon/local_exploit_suggester
```
### Manual Windows Enumeration
{% embed url="" %}
Start by listing the system information with the `systeminfo` command:
```bash
systeminfo
```
* Copy all the results to a file called **win.txt**.
Use the **windows-exploit-suggester** script to find exploits matching the system version:
```bash
./windows-exploit-suggester.py --update
```
```bash
./windows-exploit-suggester.py --database 2025-03-29-mssb.xls --systeminfo win.txt
```
* This will generate a list of potential exploits for the target machine.
### PowerShell Script Enumeration
> JAWS is a PowerShell script designed to help penetration testers (and CTF participants) quickly identify potential privilege escalation vectors on Windows systems. It is written in PowerShell 2.0 and should therefore work on all versions of Windows since Windows 7.
{% embed url="" %}
Order:
{% code overflow="wrap" %}
```
CMD C:/temp> powershell.exe -ExecutionPolicy Bypass -File ./jaws-enum.ps1 -OutputFilename JAWS-Enum.txt
```
{% endcode %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/hacking-tools/windows/windows-enumeration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
.png?alt=media)
.png?alt=media)