Releases: jeremyd2019/winautoconfig
20241115
- disable WSearch service
- load new json-format task manager settings
- virtio drivers updated to 0.1.262-2
For other Windows images, mount both the Windows image and winarmconfig.iso
on a Windows machine, or in WinPE (either 32-bit x86 or ARM64, not AMD64 because Microsoft doesn't support using AMD64 DISM against ARM64, and WinPE lacks WoW). Change drive/directory to the root of the ISO, and run deploy.cmd X:\
where X:\
is where the ARM64 Windows image is mounted. This will deploy the requisite files, and inject the drivers into the Windows install.
20220926
- Updated virtio drivers to 0.1.221-1.
- Didn't make a new qcow2 file, since I was unable to get an official VHDX of 22621 (22H2) so any such file for that would only be useful to me.
For other Windows images, mount both the Windows image and winarmconfig.iso
on a Windows machine, or in WinPE (either 32-bit x86 or ARM64, not AMD64 because Microsoft doesn't support using AMD64 DISM against ARM64, and WinPE lacks WoW). Change drive/directory to the root of the ISO, and run deploy.cmd X:\
where X:\
is where the ARM64 Windows image is mounted. This will deploy the requisite files, and inject the drivers into the Windows install.
20220405-22000.132
- Removed call to gpupdate since it started hanging a few Patch Tuesdays ago, and the manual application of group policy seems to work anyway.
- Added pre-loading of task manager settings (default to 'details' view, sort by %CPU descending, and CPU graph to 'logical processors').
- Updated virtio drivers to 0.1.215-2.
The win11_132_mod.qcow2
files is for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
For other Windows images, mount both the Windows image and winarmconfig.iso
on a Windows machine, or in WinPE (either 32-bit x86 or ARM64, not AMD64 because Microsoft doesn't support using AMD64 DISM against ARM64, and WinPE lacks WoW). Change drive/directory to the root of the ISO, and run deploy.cmd X:\
where X:\
is where the ARM64 Windows image is mounted. This will deploy the requisite files, and inject the drivers into the Windows install.
20220111-22000.132
The win11_132_mod.qcow2
files is for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
For other Windows images, mount both the Windows image and winarmconfig.iso
on a Windows machine, or in WinPE (either 32-bit x86 or ARM64, not AMD64 because Microsoft doesn't support using AMD64 DISM against ARM64, and WinPE lacks WoW). Change drive/directory to the root of the ISO, and run deploy.cmd X:\
where X:\
is where the ARM64 Windows image is mounted. This will deploy the requisite files, and inject the drivers into the Windows install.
20211222-22000.132
The win11_132_mod.qcow2
files is for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
For other Windows images, mount both the Windows image and winarmconfig.iso
on a Windows machine, or in WinPE (either 32-bit x86 or ARM64, not AMD64 because Microsoft doesn't support using AMD64 DISM against ARM64, and WinPE lacks WoW). Change drive/directory to the root of the ISO, and run deploy.cmd X:\
where X:\
is where the ARM64 Windows image is mounted. This will deploy the requisite files, and inject the drivers into the Windows install.
20211130-22000.132
Files for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
20211127-22000.132
Files for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
20211124-22000.132
Files for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
20211122-22000.132
Files for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).
20210909-22000.132
Files for 22000.132 ARM64 VHDX from https://www.microsoft.com/en-us/software-download/windowsinsiderpreviewARM64 (named Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX, sha256sum 7cd920ed5b863d2593572e95eabf5c9625d8e46f6300edda646cd46d23a634ec).
I converted this by
qemu-img convert -p -c -f vhdx Windows10_InsiderPreview_Client_ARM64_en-us_22000.VHDX -O qcow2 win11_132_official.qcow2
Then you can put the win11_132_mod.qcow2
in the same directory. This contains the differences on top of the official image for the customizations (Unattend.xml and drivers pre-applied).