I'm having this error while converting this file "17134.1.180410-1804.rs4_release_clientbusiness_vol_x86fre_en-us" Spoiler: Spoiler ============================================================ Checking ESD Info... ============================================================ ============================================================ Creating Setup Media Layout... ============================================================ ============================================================ Creating boot.wim... ============================================================ Using LZX compression with 8 threads Archiving file data: 578 MiB of 578 MiB (100%) done Using LZX compression with 8 threads Archiving file data: 86 MiB of 86 MiB (100%) done ============================================================ Creating install.wim... ============================================================ Using LZX compression with 8 threads Archiving file data: 5122 MiB of 5122 MiB (100%) done ERROR: error writing to standard output: No error Errors were reported during export. Press any key to continue . . .
Two of four have the same issue, although all of their hashes are ok, and the free space is 125GB on Dthe one I'm using) and 16GB on C: Edit: It worked. It turned out that it needed more space on C drive. Thanks @Enthousiast for your hint.
Funny! I'm from Argentina and we use it a lot there, like a joke, when you finally achieve something, like "oh habemus dinner!"
Not correct. I actually went from 14393 Pro to LTSB while preserving my Settings and Programs . https://forums.mydigitallife.net/threads/windows-10-enterprise-ltsc-2018.76325/page-2#post-1431861
Almost clear but what kind of activation/license you had on the 14393 Pro before the upgrade and on the LTSB after upgrade ?
Exactly, the only downside for me when KMSing is that i have to activate every 180 or something unlike the digital entitlement where it's permanent
When you use a KMS solution with autorenewal (almost all kms solutions offer it as option or by default), you don't have to do anything.
Good idea actually, but today i want to see if can get a HWID on Pro WS, wondering why only builds from 16251 <> 16288 accept the retail key? and if i use one of those builds and activate it with the generic key and then update to the latest version will i still be on the insider preview (Pro-WS) or not? cause 16251 <> 16288 are insider builds
The HWID works for all available builds of an edition, doesn't matter whether it's Insider or any RTM.
Are the 17134.1.180410-1804.rs4_release ESDs from 1st page the RTM builds? The post was last edited on Thursday, that's why I'm asking. And I installed 17134.1 from UUP in another PC, do I need to install this build as well?