Server 20201.1000 SAC + LTSC

Sh*t happens. Thank the Internet gods for not having to use a 19,200 baud modem, anymore.

 

Code:

927af0c739a5543d6b26b07d2452beabc26fda7f *Windows10_InsiderPreview_ChinaOnly_x32_zh-cn_19042.iso
e382d8d9b8e909751cc3e0a5cbb771c2542e95c7 *Windows10_InsiderPreview_ChinaOnly_x64_zh-cn_19042.iso
2164a4792c1848451a602a5dd01ed637a5ac0067 *Windows10_InsiderPreview_Client_x32_en-us_19042.iso
49288c3e4e5969213d6c84cebc2f3002eba7adf4 *Windows10_InsiderPreview_Client_x64_en-us_19042.iso
98d963f74bac3b27a6d957bed0fcebfc49dc6f62 *Windows10_InsiderPreview_EnterpriseVL_x32_en-us_19042.iso
8903581e8ada6c632c21941a306a8d9cf34c2be3 *Windows10_InsiderPreview_EnterpriseVL_x64_en-us_19042.iso

 

Code:

afc29790c28cb11bfb75b1d37ddba43fc9471837 *Windows10_InsiderPreview_ChinaOnly_x32_zh-cn_20201.iso
bba22881969860b5517efd20a0d855101365f64c *Windows10_InsiderPreview_ChinaOnly_x64_zh-cn_20201.iso
cfb2fdecdd4ebc2ce2bc86d46d4f2c8a477363cc *Windows10_InsiderPreview_Client_x32_en-us_20201.iso
d83f73259d2a6f96651cc5eb60159685692a69fd *Windows10_InsiderPreview_Client_x64_en-us_20201.iso
cddaa3aa44eb502775ec8c866a19a7acece2b0ee *Windows10_InsiderPreview_EnterpriseVL_x32_en-us_20201.iso
1a484b857baa99ec9e3d028b5e42b0dba1fa248e *Windows10_InsiderPreview_EnterpriseVL_x64_en-us_20201.iso
1aab9893f5e9c7cae2a91b2712bf5224ea8fbc98 *Windows_InsiderPreview_ADK_en-us_20201.iso
4ead5e5ae1e671ac33f5777962bfb49f90fa94f1 *Windows_InsiderPreview_EWDK_en-us_20201.iso
1cc46eac4bd1e7fd2abe4871200f9e95eb2e46f3 *Windows_InsiderPreview_LangPack_20201.iso
9266354d4587c2fbc35921594cd4a86cd1ae0712 *Windows_InsiderPreview_SDK_en-us_20201.iso
be30138ec198e78dda7dbb9588994e1a1ba5774a *Windows_InsiderPreview_WDK_x86x64_en-us_20201.iso
f886a293cb67899c76c33707fd39fe293cd5f4d3 *Windows_Preinstallation_Environment_en-us_20201.iso

 

Code:

6e200ba8da8f783a3702038bff720c2884614647 *Windows_InsiderPreview_Server_en-us_20201.iso
245803045c5b0fb4576ca6cc3efd04ae321442a7 *Windows_InsiderPreview_Server_ja-jp_20201.iso
f02ba991583b746f99ac039a3f7d40b3d1ea4b01 *Windows_InsiderPreview_Server_VHDX_20201.vhdx
2d623d3cd901400495481bd94af5d04542ff2117 *Windows_InsiderPreview_Server_ZH-CN_20201.iso
f11263e5138ff45bc390435b3fcc3907d21ac0be *Windows_InsiderPreview_ServerCoreAppCompatibility_20201.iso
7a7a81b89fc11916ef4190ace95ab27cbfad2b29 *Windows_Server_InsiderPreview_LangPack_20201.iso

 

Code:

a301f9e4822c9236d3366233761451a6d69d6f50 *Windows_InsiderPreview_Server_vNext_en-us_20201.iso
2aadb8d6da7895b9a880ddade3e55faaf7ae3a1a *Windows_InsiderPreview_Server_vNext_pt-pt_20201.iso
c6c20a1354ff072325a0a4ef3402115fbd89a7b4 *Windows_InsiderPreview_Server_vNext_zh-cn_20201.iso
4f25b517f5fb5c2fea926d0db7669b9ee935a581 *Windows_InsiderPreview_Server_vNext_zh-tw_20201.iso
62111c20db1c358825d26cf6aab49d78f7843853 *Windows_InsiderPreview_ServerStandard_en-us_VHDX_20201.vhdx

 

Code:

Windows_InsiderPreview_Server_vNext_de-de_20201.iso
CRC32: DF80C267
CRC64: 591295D153F34A25
SHA256: C98DAD0E4ED4799DE6314D6149709829E25BA0E07AE17EBC8A4CB44EE6A39A4C
SHA1: 0EE56FFD8A0B5052FAA804FB6BB374CEE0B8C97D
BLAKE2sp: 5FD1125179429F6D264ACD93F498AC7DF0CD8A18847447AD3F63BF932502E992

 

Code:

Windows_InsiderPreview_Server_vNext_tr-tr_20201.iso
(4258 MiB)
CRC32: 18249487
CRC64: 2A751F82839ECBD8
SHA256: 03D93B0CE3E7F355AF4A17CA310E68715E2545C4A0DD623AD22130B681B4E804
SHA1: 7B6CFD23A7D84D7D8BF585ACFC7EA42483675BCD
BLAKE2sp: B6F6F6C6EB9403E4A7EBD4C284CA5F59A15F20B85B65E7844A934294D4C1D911

Windows_InsiderPreview_Server_vNext_es-es_20201.iso
(4373 MiB)
CRC32: 40F2D7F4
CRC64: AAF663F5186B0B32
SHA256: 1665C613F743E1F02295216A35D08BB8073A0639168B608DB9A40E81AC024725
SHA1: 105EB9BC834B6B95F1583599E39D9E617D913493
BLAKE2sp: 46BA9ED4C34A5D51E80AD8D2186B28245C78037EAD5D67BD9AE90340387BD6A6

 

Bit of a update to my update problem: issue was fixed by disabling driver updates, those did make updates fail. Now everything works as excepted. Installing updates is actually quite a bit faster compared to Server 2019 build 17763.

 

Anyone having issues with Intel i211 nic driver? I can't seem to get it to work. Even using the usual hack to add driver doesn't work on this build.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Enabled fTPM and Secure Boot in my gigabyte bios. And I was able to make a backup .wim file.

 

Yes it probably will be. LTSC client version is usually released at the same time as the server version.

 

sound icon in the tray is not showing
anyone else get this problem / bug too ?

 

I have the icon, but the Audio service is not started by default on Server.

 

which is totally useless as a browser. damn shame.

 

Drivers are notoriously difficult to install in Server builds. I dual boot so what I do is export my drivers with this command

Code:

dism /online /export-driver /destination:<driver folder>

then I install Server to another partition from a USB drive. On the first reboot I boot into my main OS and incorporate my drivers with this command

Code:

DISM /IMAGE:<partition of Server> /Add-Driver /Driver:<driver folder> /forceunsigned /recurse

then I reboot and continue with the installation.