when i wrote that the links were still pointing to 19041.1, but i decided to remove those from UUP dump so no one would even think of linking to a 19041.1 build.
Seems I got the same result, any solution on the way? Check wia dism says-- Deployment Image Servicing and Management tool Version: 10.0.19041.746 Details for image : N:\Sources\install.wim Index : 1 Name : Windows 10 Home Description : Windows 10 Home Size : 14.186.484.368 bytes WIM Bootable : No Architecture : x64 Hal : <undefined> Version : 10.0.19041 ServicePack Build : 1 ServicePack Level : 0 Edition : Core Installation : Client ProductType : WinNT ProductSuite : Terminal Server System Root : WINDOWS Directories : 18707 Files : 85649 Created : 07-12-2019 - 16:44:48 Modified : 19-02-2021 - 12:55:17 Languages : da-DK (Default) The operation completed successfully. C:\Windows\system32>
seems like you set "AddUpdates=0", the issue with the new SSU was fixed by @abbodi1406 yesterday night.
I havent touched the script and never do, always run script as it is, any way I will try DL from new, will return if problem. The x86 was correct 19041.844.210209-1708.VB_RELEASE_SVC_PROD3_CLIENTMULTI_X86FRE_DA-DK So I make new script DL for x64 and see result, btw, I pick all version but uncheck the n version, all other stay as standard. The script it self I never edit in. Update Both x64 x86 now after new script is maked 19041.844.210209-1708.VB
Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.331.1390.0) This has been at 0% downloaded for quite some time. Is this update broken for anyone else?
Last year, between August 2020 and October 2020, I applied 3 consecutive EPs to 19041 to get 19042. In every case, Windows Update stopped working until the final release day for 20H2 of 10/20/2020. I was able to get updates from the catalog, UUPDump, and elsewhere. But NEVER from MSFT until the official release day. On 10/20/2020, it was if a switch had been flipped and I was suddenly able to get Windows Updates. Now I'm seeing something similar. I get no updates from 19043, but when I roll back, I get updates from 19042. So I am suspicious that there is such a thing as pre-release EPs. Perhaps there is a version and update channel mismatch. 'Not sure. EDIT: Last year, when I rolled back from 19042 to 19041, I'd get updates. But when I was on 19042, they would just stop. Now I am see the same phenomena, it's between 19043 and 19042.
@donmiller they create different entries/packs for the same update for each version for a reason WU works based on metadata and detectoids e.g. Update for Removal of Adobe Flash Player for Windows 10 Version 2004 for x64-based systems (KB4577586) Update for Removal of Adobe Flash Player for Windows 10 Version 20H2 for x64-based systems (KB4577586) since 19043 is not generally available, they didn't create specific updates for it
Yes, those updates don't show up in 19043 Windows Update (WU). KB4023057 (WU Reset) is offered on 19042, but not on 19043. So there are some differences. But last year (2020), I couldn't get any updates on 19042 WU until the day it was officially released. I'd roll back, get updates and then reapply the 19042 EP.
Yes I remember having the same issues wonder if the same problems with windows update will happen on 19043.844
Hi guys!!! In Original images from Microsoft MSDN Microsoft Windows 10.0.19042.804 [RU] Version 20H2 (Updated February 2021) - integrated into boot.wim instead of windows10.0-kb4586858-DU for SafeOS (for boot.wim & winre.wim only), windows10.0- kb4562830 (Enablement Package, includes Edge Chromium). Can anyone explain.