Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    pxe windows repair

    1

    Orchestrate PXE-based Windows repair and recovery environments via iPXE, WinPE, and Linux rescue tools.

    $6

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    pxe windows repair

    pxe windows repair

    Example session with this skill installed

    A Windows PC on my LAN won't boot and I don't have a USB drive. I have Tiny PXE Server on my laptop. Help me set up a rescue boot using SystemRescue.

    • Read your context and instructions
    • Compiled the pxe windows repair

    I will configure the PXE server environment and provide the rescue sequence to access the filesystem.

    PXE Rescue Configuration

    To boot SystemRescue via Tiny PXE Server, update your config.ini and use the following iPXE script.

    1. Tiny PXE Server Config (config.ini)

    [Settings]
proxydhcp=1
start=1
filename=netboot.xyz.kpxe
httpd=1
binl=0
dns=1
[arch]
00007=ipxe-x86_64.efi
00009=ipxe-x86_64.efi

    2. Rescue Script (rescue.ipxe)

    #!ipxe
set srv_ip 192.168.1.5
set port 8080
kernel http://${srv_ip}:${port}/sysresccd/vmlinuz archisobasedir=sysresccd archisolabel=SYSRCD1000 ip=dhcp
initrd http://${srv_ip}:${port}/sysresccd/initramfs.img
boot

    3. Execution Steps

    StepActionCommand/Detail
    FirewallOpen PortsUDP 69 (TFTP), UDP 4011 (ProxyDHCP), TCP 8080 (HTTP)
    AccessEnable SSHsystemctl start sshd
    NetworkFlush Firewallnft flush ruleset (Mandatory for inbound SSH)
    RepairFix NTFSntfsfix -d /dev/nvme0n1p3
    TransferData Backupmount -o ro /dev/nvme0n1p3 /mnt/windows && rsync -avP /mnt/windows/Users/ user@nas:/backup/

    Next steps

    • Verify the laptop and patient PC are on the same subnet (no VLAN isolation).
    • Check the patient PC's BIOS boot order to ensure PXE/Network Boot is the primary priority.
    • If the drive doesn't appear in Linux, check dmesg for controller errors.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Automate Tiny PXE Server configuration for ProxyDHCP environments.Generate iPXE scripts for network-based Windows installation and repair.Fix NTFS filesystem corruption using Linux rescue tools over the network.Inject storage drivers into WinPE images to resolve missing disk issues.

    About this skill

    The problem

    Remote or local Windows machines often suffer from boot failures where the physical disk is unreachable or the OS is corrupted, but the hardware's PXE ROM remains functional. Manually configuring network boot environments is error-prone due to specific DHCP proxy requirements and sensitive iPXE script syntax.

    What it does

    • Generates precise config.ini files for Tiny PXE Server, including ProxyDHCP and architecture-specific EFI mappings.
    • Constructs valid iPXE boot scripts using wimboot to chain load Windows PE and installation media over HTTP.
    • Provides step-by-step CLI recovery commands for WinPE environments, including driver injection and network share mounting.
    • Scripts Linux-based rescue sequences using SystemRescue to bypass Windows filesystem locks and perform SMART diagnostics via SSH.

    Frameworks & tools

    Tiny PXE Server, iPXE, wimboot, SystemRescue, WinPE, Diskpart, and ntfs-3g.

    Why this beats prompting it yourself

    General LLMs often suggest invalid iPXE commands like pause or fail to account for the mandatory nft firewall flushing required in modern rescue distros. This skill uses a proven sequence of hardware-level diagnostics and specific port requirements for UDP 69 and 4011 to ensure the network boot actually triggers.

    Use cases

    • Recovering data from a Windows laptop with a broken screen or keyboard using network takeover.
    • Reinstalling Windows on multiple fleet machines without physical USB media.
    • Repairing corrupted NTFS master file tables ($MFT) when Windows Recovery Environment fails to load.
    • Injecting missing Intel RST/VMD drivers into a boot image to recognize NVMe drives.

    Known limitations

    Requires a functional LAN connection and PXE-enabled BIOS on the target machine. WinRM and PowerShell are not supported in the standard WinPE 19041 environment.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 6 days ago

    • Passed all security checks, Safe to install

    Listed6 days ago

    What's inside

    Frequently Asked Questions