Good question The one I gave is the OEM version. I believe it doesn't have the debugging code so it's a lot better in terms of performance But other than that, there's not really a difference For those of you with different languages want to make an enterprise version, you can follow the same instructions I have with the insiders version and it should work BTW: I didn't put education but you can make a custom education ISO as well. I won't make instructions for that one though
thankyou for the information. one more things, will this iso that made by imgburn will be UEFI bootable ? or only BIOS bootable ? right now im using GPT partition table so it wont be installable by BIOS boot setup.
Good question It's either or Whichever you want So if you put it as gpt it won't be bootable in bios correct... You just have to make the setting yourself
Thank you. And it is not bad to have your ISO with DisplayName and DisplayDescription. e.g. Code: WIM Information:--------------------- GUID: {4993DA5D-2F37-F72C-0099-E23954915CE5} Image Count: 1 Compression: LZX Part Number: 1/1 Attributes: 0x8 RP_FIX Image Index: 1 ------------------- Name: Windows 10 Enterprise Description: Windows 10 Enterprise Flags: Enterprise Files: 73346 Folders: 14635 Expanded Size: 8884 MB WIM XML Information: --------------------------- <WIM> <TOTALBYTES>2552624682</TOTALBYTES> <IMAGE INDEX="1"> <DIRCOUNT>14635</DIRCOUNT> <FILECOUNT>73346</FILECOUNT> <TOTALBYTES>9316297166</TOTALBYTES> <HARDLINKBYTES>4086178775</HARDLINKBYTES> <CREATIONTIME> <HIGHPART>0x01D0BB17</HIGHPART> <LOWPART>0x01A19EC0</LOWPART> </CREATIONTIME> <LASTMODIFICATIONTIME> <HIGHPART>0x01D0BB19</HIGHPART> <LOWPART>0xB5C7290D</LOWPART> </LASTMODIFICATIONTIME> <WINDOWS> <ARCH>0</ARCH> <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME> <EDITIONID>Enterprise</EDITIONID> <INSTALLATIONTYPE>Client</INSTALLATIONTYPE> <HAL>acpiapic</HAL> <PRODUCTTYPE>WinNT</PRODUCTTYPE> <PRODUCTSUITE>Terminal Server</PRODUCTSUITE> <LANGUAGES> <LANGUAGE>zh-TW</LANGUAGE> <DEFAULT>zh-TW</DEFAULT> </LANGUAGES> <SERVICINGDATA> <PKEYCONFIGVERSION>10.0.10240.16384;2015-07-10T02:28:20Z</PKEYCONFIGVERSION> </SERVICINGDATA> <VERSION> <MAJOR>10</MAJOR> <MINOR>0</MINOR> <BUILD>10240</BUILD> <SPBUILD>16384</SPBUILD> <SPLEVEL>0</SPLEVEL> </VERSION> <SYSTEMROOT>WINDOWS</SYSTEMROOT> </WINDOWS> <NAME>Windows 10 Enterprise</NAME> <DESCRIPTION>Windows 10 Enterprise</DESCRIPTION> <FLAGS>Enterprise</FLAGS> <DISPLAYNAME>Windows 10 企業版</DISPLAYNAME> <DISPLAYDESCRIPTION>Windows 10 企業版</DISPLAYDESCRIPTION> </IMAGE> </WIM>
I'm glad you had fun, but you do realize that the esd version is literally the same thing as oem version, right?
This one doesn't have the debugging code so it's a whole lot faster The tutorial was also just for people wanted to know how to make homebrew...
Okay I need everyone's voice Poll Do I cancel the upload or not... I need answers in about the next 5 minutes or so...
It is nice of you trying to do contributions for us. But most people would appreciate it more if it was something new, like the one you mentioned - Windows 10 Enterprise 2015 LTSB.
Doing the set-edition is not a bad idea. I use it in my win8.1 integrate script to save some file size. It's a good way to integrate a lot of updates and not bloat the image too much. A decent way to integrate the updates so far would be to: start with homesinglelanguage add-package them all using /preventpending /resetbase export wim remount and set-edition:core commit and rename with imagex export, repeat set-editions for pro, enterprise You could add the student one in there too, but the only way to activate them currently would be gVLK and kms.