to all:
but the md5 is correct... ? so there is no "hack/crack" right ?
back to subject:
so what is the different between them ?
Where did you get the md5 number from? All the md5 number means is that the ISO file that you have matches the ISO file on the server that you got it from. Unless you got the md5 number directly from Microsoft, the fact that it matches means nothing in regards to whether you have a hacked Windows 10 contained in the ISO file or not. If someone hacked Windows 10 to either put a virus in it or install an illegitimate activation scheme, and they packaged it up into an ISO file and posted it with an md5 number - you download the ISO file and the md5 number matches, that just means that you got the same hacked Windows 10 as they posted.
We can't tell you what the differences are in the ISO files because they are not Microsoft ISO files. The Microsoft ISO file contains the following editions of Windows 10:
Code:
F:\sources>dism /get-wiminfo /wimfile:install.esd
Deployment Image Servicing and Management tool
Version: 10.0.19041.1
Details for image : install.esd
Index : 1
Name : Windows 10 Home
Description : Windows 10 Home
Size : 14,825,959,665 bytes
Index : 2
Name : Windows 10 Home N
Description : Windows 10 Home N
Size : 14,047,871,738 bytes
Index : 3
Name : Windows 10 Home Single Language
Description : Windows 10 Home Single Language
Size : 14,828,533,138 bytes
Index : 4
Name : Windows 10 Education
Description : Windows 10 Education
Size : 15,074,470,965 bytes
Index : 5
Name : Windows 10 Education N
Description : Windows 10 Education N
Size : 14,311,366,121 bytes
Index : 6
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 15,071,449,952 bytes
Index : 7
Name : Windows 10 Pro N
Description : Windows 10 Pro N
Size : 14,308,214,173 bytes
The operation completed successfully.
You can do the same thing. Mount the ISO file. In command prompt (with admin) run the dism /get-wiminfo command using the install.esd or install.wim file in the sources folder of the mounted ISO file.