Windows 10 ESD Repository

No, my own HYPER-V VM secret KMS server @home (created with slave77s S-M-R-T JATDevice) for personal use and friends.

 

Why do you preferr to run a virtual kms server instead of kmspico or microsoft toolkit's ez activator (which emulate a kms server on the local machine)?

 

No local virus/malware-scanner can produce a false alert.
You have no extra software on client.
You don't have to use workarounds for 127.0.0.1 restriction.

 

He is using it, but on VM. (He has his own favourite.)

 

He sent me an extensive motivation via pm.

I only asked why he preferred it over a local kms emulator, nothing more, nothing less

For me the use of it for his friends' systems whas an interesting use of a vm kms server (i'm going to try it out, in the past it whas a 1.5GB vm install so i didn't bother).

 

Maybe they liked the 586 (aka Pentium).

 

ProductName REG_SZ Windows 10 Pro

 

You need to login to view this posts content.

 

can u post german home x86 links ?

and "N" Versions of pro/home

 

You need to login to view this posts content.

 

Here, the procedure for converting an unencrypted esd file in an iso image using only Windows ADK 10:

Code:

1) md "<Windows_Files_Path>"
2) md "<iso_Path>"
3) md "<esd_File_Path>"
4) move "<esd_File_Name>.esd" "<esd_File_Path>\"
5) dism /Get-WimInfo /WimFile:"<esd_File_Path>\<esd_File_Name>.esd"
6) dism /Apply-Image /ImageFile:"<esd_File_Path>\<esd_File_Name>.esd" /Index:1 /ApplyDir:"<Windows_Files_Path>" /CheckIntegrity
7) dism /Export-Image /SourceImageFile
:"<esd_File_Path>\<esd_File_Name>.esd" /SourceIndex
:2 /DestinationImageFile
:"<Windows_Files_Path>\sources\boot.wim" /Compress:max /CheckIntegrity
8) dism /Export-image /SourceImageFile:"<esd_File_Path>\<esd_File_Name>.esd" /SourceIndex:3 /DestinationImageFile:"<Windows_Files_Path>\sources\boot.wim" /Compress:max /CheckIntegrity
9) dism /Export-image /SourceImageFile:"<esd_File_Path>\<esd_File_Name>.esd" /SourceIndex:4 /DestinationImageFile:"<Windows_Files_Path>\sources\install.wim" /Compress:max /CheckIntegrity
or
10) dism /Export-image /SourceImageFile:"<esd_File_Path>\<esd_File_Name>.esd" /SourceIndex:4 /DestinationImageFile:"<Windows_Files_Path>\sources\install.esd" /Compress:Recovery /CheckIntegrity
11) oscdimg -o -u2 -udfver102 -l"<Label_Name>" -tmm/dd/yyyy,hh:mm:ss -bootdata:2#p0,e,b"<Windows_Files_Path>\boot\etfsboot.com"#pEF,e,b"<Windows_Files_Path>\efi\microsoft\boot\efisys.bin"
            "<Windows_Files_Path>" "<iso_Path>\<iso_Name>.iso"
12) isoburn /Q <Drive_Letter>: "<iso_Path>\<iso_Name>.iso"

Thanks

Bye

 

You need to add /Bootable to 8) command

 

I have Windows 10.

When I download a new build from Windows Update, Windows download an ESD encrypted file, it decrypts, it saves in the <Primary_partition_letter>:\$Windows.~BT\sources\install.esd file and then it goes automatically to its installation.

How do I prevent this automatic installation leaving however the <Primary_partition_letter>:\$Windows.~BT\sources\install.esd decrypted file?

Thanks

Bye

 

Why should I add this option because the "Microsoft Windows Setup" volume image contains no boot code?

Thanks

Bye

 

I am no coder or programmer but shouldn't the boot.wim be bootable? Please correct me if i'm wrong, just learning.

 

I tried this iso and it boots the same. Why?

Thanks

Bye

 

You need to login to view this posts content.

 

Code:

Index : 1
Name : Windows Setup Media
Description : Windows Setup Media
Size : 258,997,645 bytes

Index : 2
Name : Microsoft Windows PE (x64)
Description : Microsoft Windows PE (x64)
Size : 1,435,435,838 bytes

Index : 3
Name : Microsoft Windows Setup (x64)
Description : Microsoft Windows Setup (x64)
Size : 1,584,986,830 bytes

Index : 4
Name : Windows 10 Pro Technical Preview
Description : Windows 10 Pro Technical Preview
Size : 13,857,789,279 bytes

Index : 5
Name : Windows 10 Technical Preview
Description : Windows 10 Technical Preview
Size : 13,789,790,615 bytes

The operation completed successfully.

Technical Preview?

 

Oh noooooo!!!