Is there an ESD Windows 10 Client Business Volume Edition x64 [Version 20H2 Build 19042.572] with version Pro Workstation in spanish? Thanks in advance
haha I don't understand M$FT said that IE will be "retired" soon and at the same time are "updating" group policies for IE itself in build 2004 LOL...
Yes, will be retired *soon*, but until its time is over, it must run well. Otherwise, Enterprises will spank MS' blank...
that has always been a possibility, but I rather not add more of this stuff : u,x86,da-dk,d;2a892143d6eaa1dcadc8720eb890a1db7a03b28d,2249489774,d;ef137301727174a08df1fb84743469139bc4e925,2467425384, Or setup a sccm. MCT/Windows10Upgrade has been a good source so far, but now we've reached a point where ms does not care of any version that does not bundle the new edge digital signature of the xml is irrelevant, long ago I've added ltsb esd's; and it does get checked when actually creating the iso (setuphost / setupprep / etc).
I actually ment products.cab digital signature, MCT don't care about it ithink i.e. create new xml for 1909/2004 with latest links, and host the cab on github
Aboddi do you have an updated static download windowsupdate.com link for windowsupdatebox.exe? Looks the latest for 20H2 is signed Nov 5th. Tried the good ol windowsupdatebox_[sha1checksum].exe url in same path as the esd that's worked with all past releases, but no luck this time.
I think what abbodi1406 means is that an official Win10 build has files with signed timestamps. This allows booting with Secure Boot Enabled in the UEFI BIOS. For example: Spoiler
@ericgl We are actually talking about digital signature of windowsupdatebox.exe itself file modified date can be changed, but the signing timestamp don't