DD Images for Multiple Windows Systems Suitable for UEFI Booting

In recent times, some products have been produced that are suitable for UEFI The Windows system DD images, from oldest to newest in order of system release time, are:
1. Windows Server 2012 R2 Datacenter
2. Windows Server 2016 Datacenter (build: 14393.5006)
3. Windows Server 2019 Datacenter (build: 17763.2686)
4. Windows Server 2022 Datacenter (build: 20348.587)
5. Windows 10 Enterprise LTSC (build: 19044.1288)
6. Windows 11 Pro for Workstations 21H2 (build: 22000.194)
18 files in total. It is divided into the above 6 systems and 3 languages: Chinese, English and Japanese.
warn:These DD images are not suitable for ordinary VPS or dedicated servers started by Legacy BIOS. They are only suitable for UEFI Start a VPS or dedicated server.

Mirroring has the following characteristics

1. The following drivers are integrated.
1) KVM driver (virtio 0.1.208-1):
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.208-1/virtio-win-0.1.208.iso

2) XEN driver (AWS PV Driver 8.4.0):
https://s3.amazonaws.com/ec2-windows-drivers-downloads/AWSPV/Latest/AWSPVDriver.zip
Why use the XEN driver of Amazon AWS? The reason is that the drivers officially provided by XEN are unsigned, and adding them directly to the system will cause errors.

3) Intel network card driver (26.2):
https://downloadmirror.intel.com/25016/eng/Wired_driver_26.2_x64.zip
reference:https://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10

2. Direct unattended installation without VNC interaction. After DD is completed, you can log in to the desktop remotely.
3. Made based on the VOL version, so the system can be activated using KMS.
4. Close the Ctrl + Alt + Del shortcut key login method
5. Close the server manager and auto-start it at boot.
6. Turn off IE security enhancement configuration
7. Turn on Windows Remote Desktop
8. Other system optimizations based on Dism++, such as removing the shortcut arrows, etc.
9. Enable the firewall by default and confirm that port 3389 is allowed in the firewall.
10. For security reasons, default sharing is turned off.
11. Based on security considerations,Suggest changesThe default port 3389 for remote connections. Therefore, a bat script was created to modify the RDP port with one click. Please click here to download. After unzipping, run the bat script with administrator rights, enter the port number and press Enter to execute, and then restart the computer to take effect.

Installation method

1. Installation process on VPS

It is recommended that the memory should start at 4GB and the hard disk should start at 30GB. Use the root user to ssh in and execute the following command, and then wait quietly.
The installation speed depends on the speed of the network image download. Basically, after waiting for 10-60 minutes, open VNC again and you will see the familiar Windows login interface.

wget -qO InstallNET.sh https://github.com/teddysun/across/raw/master/InstallNET.sh && bash InstallNET.sh -dd "DD download URL"

Note: The InstallNET.sh script is developed by Vicer, reference URL:https://moeclub.org
The one-click DD script has been updated on March 21, 2022
Updated content:
1) Fixed the error message Error! Not Found grub. that would appear in DD under CentOS 7.
2) Added DD installation package compatible with xz compression format.
URL:https://github.com/teddysun/across/raw/master/InstallNET.sh

2. Installation process on a server with rescue mode
Use the root user to ssh into the rescue mode (rescue) and execute the following command and wait for the command to complete. Then exit ssh login. Change to boot from the hard disk (Hard disk) and restart.

wget -O- "DD download URL" | xzcat | dd of=/dev/sda

Default username and password for remote desktop
Username: administrator
password:

Notice:Please log in to the remote desktop after the installation is complete, perform automatic Windows updates and change the Administrator’s password immediately.

Windows Server 2012 R2 Datacenter image file name, size, SHA-1 and MD5 information are as follows
1. cn_win2012r2_uefi.xz, 2.89GB, 43a8f0769a58c0fabcc8b0010a953076d0d9287a, 303c8f3b5f0d4ec55e2faf93022e92c4
2. en_win2012r2_uefi.xz, 2.46GB, a301176a6cd5de9aa8b6ee99c9dd570184da43e1, 87788c747d9b7e5d80584b410e544a70
3. ja_win2012r2_uefi.xz, 2.89GB, 309c0a86774b128e4c00fdd3ead0dca4f1065c19, 22249e9b34062509b57d15d44bc55f44

Windows Server 2016 Datacenter (build: 14393.5006) image file name, size, SHA-1 and MD5 information are as follows
1. cn_win2016_uefi.xz, 3.49GB, 48987ae08b5b32d90be832c8244c233abe085ea8, 61a355ad0cc4ffdaedf8666a975bc4fa
2. en_win2016_uefi.xz, 3.27GB, f0050a53f7a86864cef42f434d87d23c993d2de8, 873250d73fb89b9578c235e6f49a2bcd
3.ja_win2016_uefi.xz, 3.42GB, e8af54b548e970a9749362ed6168f25a27e10b65, 03d4b27e7932cb8179997406eb1d49e6

Windows Server 2019 Datacenter (build: 17763.2686) image file name, size, SHA-1 and MD5 information are as follows
1. cn_win2019_uefi.xz, 3.76GB, 1ffe5bee396969e6e1f1999ea460568f20a46358, 6d6a9af477cd29bcb1cc429730586b5e
2. en_win2019_uefi.xz, 3.62GB, a0bc2415796c607ea7493fd982f7135986970bbc, 66cbc7e6343ffbcbaaaba3f5a4e75c35
3.ja_win2019_uefi.xz, 3.72GB, 4a137f850169b363966e3e7760564d77976edb3f, 367b0d7e65cb41e2d2757fd45d437cbb

Windows Server 2022 Datacenter (build: 20348.587) image file name, size, SHA-1 and MD5 information are as follows
1. zh-cn_win2022_uefi.xz, 3.00GB, 9c639c5c84ab2ca16175acb46fddf57e8e18b4cd, e74e9118b2c1b579130f26705b03a1c3
2. en-us_win2022_uefi.xz, 2.88GB, c36f5c9de68e70c093bc47cd97d1c7c382790e56, 372c162df6eaadde7ce12017bc35cfa7
3.ja-jp_win2022_uefi.xz, 2.93GB, 72699c39a6e59cee15806ff8753af23bbe22d3ed, 492913533bb796b6fcd7c7b89ced247c

Windows 10 Enterprise LTSC (build: 19044.1288) image file name, size, SHA-1 and MD5 information are as follows
1. zh-cn_win10_ltsc_uefi.xz, 3.17GB, 04c9c31ec136666ea44390e80b2acd40d0decdcf, 917eec4fb43c0e5a93da4df4b206305a
2. en-us_win10_ltsc_uefi.xz, 3.03GB, 7a34c12fbe339967de33cd7176fd4f9e96b42e60, d65356383b576ca177640054b691e124
3. ja-jp_win10_ltsc_uefi.xz, 3.14GB, ea581e5922fdad054f466333efd845b91d85265d, 9e4320f72698c9225fdbf70cb34abbd4

Windows 11 Pro for Workstations 21H2 (build: 22000.194) image file name, size, SHA-1 and MD5 information are as follows
1. zh-cn_win11_uefi.xz, 3.06GB, 28118f3f582c5bbbf60708c503d937238fde13b8, 6196ee55a92199550e5d1f79c6f68424
2. en-us_win11_uefi.xz, 2.96GB, 7931879b9f3a2c747d1e512384550414b97490f4, 760c1e64bde2536a4e5c58ccf5ec3857
3. ja-jp_win11_uefi.xz, 3.54GB, 0a9fdb2c4881ea6ad0166276d64c8ea24e73fcf6, e1177ab44a7a09eebcfd7cd32400feba

Download link(DD download URL)

Windows Server 2012 R2 Datacenter mirror link address:
https://dl.lamp.sh/vhd/cn_win2012r2_uefi.xz
https://dl.lamp.sh/vhd/en_win2012r2_uefi.xz
https://dl.lamp.sh/vhd/ja_win2012r2_uefi.xz

Windows Server 2016 Datacenter (build: 14393.5006) Mirror link address:
https://dl.lamp.sh/vhd/cn_win2016_uefi.xz
https://dl.lamp.sh/vhd/en_win2016_uefi.xz
https://dl.lamp.sh/vhd/ja_win2016_uefi.xz

Windows Server 2019 Datacenter (build: 17763.2686) Mirror link address:
https://dl.lamp.sh/vhd/cn_win2019_uefi.xz
https://dl.lamp.sh/vhd/en_win2019_uefi.xz
https://dl.lamp.sh/vhd/ja_win2019_uefi.xz

Windows Server 2022 Datacenter (build: 20348.587) Mirror link address:
https://dl.lamp.sh/vhd/zh-cn_win2022_uefi.xz
https://dl.lamp.sh/vhd/en-us_win2022_uefi.xz
https://dl.lamp.sh/vhd/ja-jp_win2022_uefi.xz

Windows 10 Enterprise LTSC (build: 19044.1288) Mirror link address:
https://dl.lamp.sh/vhd/zh-cn_win10_ltsc_uefi.xz
https://dl.lamp.sh/vhd/en-us_win10_ltsc_uefi.xz
https://dl.lamp.sh/vhd/ja-jp_win10_ltsc_uefi.xz

Windows 11 Pro for Workstations 21H2 (build: 22000.194) Mirror link address:
https://dl.lamp.sh/vhd/zh-cn_win11_uefi.xz
https://dl.lamp.sh/vhd/en-us_win11_uefi.xz
https://dl.lamp.sh/vhd/ja-jp_win11_uefi.xz

Browse the catalog:
https://dl.lamp.sh/vhd

Some notes and notes

1. When using the one-click DD script to install, if you can see the installation process in VNC, as shown below, please wait… When prompted, do not think that there is a problem. It is downloading and DDing the system. This is a normal phenomenon. Wait until it is completed. Can.

2. After the DD system is completed, after connecting through remote desktop (mstsc) for the first time, the following network prompt will pop up on the right side of the desktop, please select[Yes]
1) Chinese version

2) English version

3) Japanese version

3. Test screenshots of Hetzner AX101 DD:
Generally, you need to contact Hetzner customer service to allow the server to boot from UEFI.

4. PVE virtualization VPS test screenshot:
1)Windows Server 2016

2)Windows Server 2019

3)Windows 11

1. These images are only made for learning purposes. If you need to use them for a long time, please use a genuine Windows key to activate the system.
2. All the images are produced by the original MSDN. I can guarantee that I do not include any private goods. If you do not trust me, please do not use it.
3. After successful DD on the server, you need to manually expand the disk.
4. Using Windows DD images may violate the TOS of some merchants. If you are punished by the merchant for using the image I made, I am not responsible.
5. The system’s disk partition format uses UEFI, so the DD is locatedsystem diskCapacity greater than 2TB can also be used normally.

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button