Windows PE Archives

Winsage

January 4, 2026

How to Install Windows Configuration Designer Using Winget Command

The Windows Configuration Designer is a tool from Microsoft that allows users to create provisioning packages for automating the setup of Windows devices. These packages, saved as .ppkg files, can pre-configure settings such as network configurations, user accounts, and device names. The tool is not pre-installed on Windows systems and is primarily intended for IT administrators. It can be downloaded from the Microsoft Store or installed via the command-line tool winget, which requires the package name to be enclosed in double quotes for proper recognition. The installation process involves opening a terminal as an administrator, checking for winget availability, and executing the installation command. The download size is approximately 30 to 50 MB, and installation typically completes in under a minute. Users can verify the installation by searching for the application or using winget commands. Alternative installation methods include using the Microsoft Store or the Windows Assessment and Deployment Kit (ADK). The tool is free and does not require a Microsoft account for winget installations.

Winsage

September 29, 2025

I used DISM to create a Windows installer with all my apps, and here’s how it works

To back up a Windows 11 image, start with a fresh installation and use the Sysprep tool to generalize the system, avoiding Microsoft Store apps to prevent Sysprep failure. Prepare two external drives: one for storing the Windows image (minimum 8GB) and another bootable drive configured with Windows Preinstallation Environment (Windows PE). Download the Windows Assessment and Deployment Kit (ADK) and the Windows PE add-on to create the bootable USB drive. Enter Audit Mode by pressing Ctrl+Shift+F3 at the out-of-box experience screen, disable app updates, and install desired applications for the entire system. Use Sysprep to enter Out of Box Experience (OOBE), check Generalize, and select Shutdown. Boot from the Windows PE drive, use diskpart to identify drive letters, and capture the image with the DISM command. To apply the image on a new PC, create a diskpart script for partitioning and a batch script for applying the image. Boot the new PC from the Windows PE drive, run the diskpart script to create partitions, and execute the batch script to apply the image. This method is efficient for deploying consistent applications across multiple PCs.

Winsage

September 17, 2025

How to use DISM command tool to repair Windows 10 image

The Deployment Image Servicing and Management (DISM) tool is a command-line utility in Windows 10 used for preparing, modifying, and repairing system images, including the Windows Recovery Environment, Windows Setup, and Windows PE. It can address various system issues, and when system files are missing or corrupted, the System File Checker (SFC) can replace them using the recovery image. If local image files are compromised, the SFC command may fail, and using the "install.wim" image file with DISM can repair the image, allowing SFC to function without a complete OS reinstallation. DISM includes commands such as "CheckHealth," "ScanHealth," and "RestoreHealth" for repairing system images. The "CheckHealth" command identifies corruptions without repairing them, while "ScanHealth" performs a comprehensive scan for underlying issues. The "RestoreHealth" command scans and repairs common problems, connecting to Windows Update to download and replace damaged files if needed. If DISM encounters difficulties, an "install.wim" or "install.esd" file can be used as an alternative source for repairs. The Media Creation Tool can download a fresh Windows 10 ISO file if necessary. Specific commands can be executed to repair the image using these files, and troubleshooting common errors may involve checking for source file locations or ensuring a stable internet connection. Once the image is restored, the SFC command can be run to repair the installation of Windows 10. The SFC tool checks and repairs system files using local image files, with logs saved for further review. DISM does not delete files, and its execution time can vary based on system speed and the extent of corruption.

Winsage

April 5, 2025

Introducing Windows on arm. And by arm, we mean wrist

Gustave Monce, a PhD student from Bordeaux, is working on a project to run Windows on the Google Pixel Watch 3, referred to as "Windows on ARM." Initially announced on April Fools' Day, Monce clarified that the project is serious and involves UEFI on the Pixel Watch 3 with the capability to boot Windows and Linux. He has previously developed DuoWOA, enabling Windows 11 to run on Microsoft's Surface Duo, and is also working on LumiaWOA for the Nokia Lumia 950 and 950XL. The smartwatch project utilizes an Arm64 build of Windows PE, allowing the Pixel Watch 3 to boot a WinPE image via UEFI, though the final installation steps remain undocumented. Monce describes the project as real and goofy, acknowledging its current limitations while inviting others to explore the code.

Winsage

April 2, 2025

Windows OS On A Pixel Watch! PHD Student Achieves The Impossible! News24 –

A PhD student named Gustave Monce, along with a small team, successfully ran the Windows operating system on a Pixel Watch through the WOA project. The process involved examining a rooted boot image, modifying the stock UEFI, altering the ACPI table, and patching various files to enable the watch to run Windows PE. Despite the extensive work, the project faced challenges due to the Pixel Watch's internal architecture, which was designed for its native OS. Additionally, old iPads can be repurposed as e-readers by downloading e-book reader applications or, for a more ambitious project, by booting them with a Raspberry Pi or another Linux-based operating system.

Winsage

April 2, 2025

Someone just booted Windows on a Pixel Watch, and it actually (kind of) works

PhD student Gustave Monce has successfully run Windows for Arm on the Pixel Watch 3, utilizing its quad-core Snapdragon processor and 456×456 OLED display. He modified Qualcomm’s UEFI-based XBL bootloader to boot the Windows Preinstallation Environment (PE). Despite challenges from the release of Android 15, which disrupted his code-loading process, Monce adapted the stock kernel image to restore booting into Windows PE with limited functionality. He has achieved basic USB support for mass storage, highlighting the potential of modern mobile hardware.