ricktendo

Well then you need to find the problem driver, do some tests, integrate DP one by one, then when you found the problem DP then you do the same for the sub folders until find the culprit

Better remove the drivers for hardware that you dont have

Do NOT integrate WMF 3/4, they require .net 4.0+

If you want one similar to the original, then use the rebuild (I only better compress the MZZ file for 100 MB space saving) Now the "slim" is still the "full" framework, only that I remove setup stuff (you will find the VBS that I use to edit the MSI on the first post) and I do a admin install for better 7zip compression...this is why you see \ProgramFilesFolder and \Windows directories, you can use the VBS to slim your package and delete all setup files exept the 4.5.1 MSI and the MZZ file I been meaning to do some videos on what methods I use to make my slim and rebuilt installers (in case I am unable to continue) but it keeps getting put off

Ultimate x86 aquí también y Windows 8 Pro con WMC

If you compress with lzma2 you get that error, use regular lzma

Y sources\setup.exe (puedes eliminar el setup.exe de la raíz) Si no incluyes a el setup.exe en \sources te dará un error durante instalación http://www.msfn.org/board/topic/147213-what-folders-can-safetly-deleted-from-windows-7-dvd/#entry943854

Updated

Los unicos que necesitas en el DVD son \boot \efi bootmgr bootmgr.efi \sources\boot.wim, install.wim, setup.exe

Extract the MSI and other files from the slim installer, also extract the MSP from the update installer, run the following command msiexec /a <msi_name>.msi /p <msp_name>.mspBTW there is no need for updating this installer, it already has this months security updates

Done

Do you mean how do you integrate a update into the installer?

WOW I did not realize it was that bad

LOL

They are already added to the update rollup http://imageshack.us/a/img577/2152/zh2o.png If you use the ENU you will have these, I have not updated the INTL

After you install ADK you have to point WinTK to the dism of ADK, so it uses that one (Options -> Misc: Custom DISM) BTW ADK supersedes WAIK, so you can delete WAIK and keep ADK (it works on Win7 as well)

Make sure you are on Windows 8 or have ADK installed and tell WinTK to use that version instead of the default BTW would be cool if WinTK detected that you were on Windows 7 servicing Windows 8/8.1 and warn you...maybe even provide a link for ADK

Updated

Problem should be solved

This is great, thanks

AHA! a solution would be to integrate your drivers

Not to mention all the weed you smoked in Amsterdam is probably making you think your internets is "funny" (when its not)

Kewl kars

You can with Autounattend.xml I think

For OEM activation you need your bios to have a 2.1 slic, you need to add your OEM product key and add your (OEM specific) <licence>.xrm-ms needs to go in \system32\oem to automatically register (add to mounted wim or use sources\$oem$ method) If all 3 of these criteria are there, you will have your genuine OEM windows