Windows 8.1 AIO 20in1 with Update x86 en-US Apr2014 v2 (By murphy78) - TEAM OS | 2.87 GB32-bit RTM Sources:
These RTM Sources are the final Build 9600
Windows 8.1 (Core) / KMS-Activated
Windows 8.1 (Core) N / KMS-Activated
Windows 8.1 (Core) Single Language / KMS-Activated
Windows 8.1 Pro / KMS-Activated
Windows 8.1 Pro N / KMS-Activated
Windows 8.1 Pro VL / KMS-Activated
Windows 8.1 Pro N VL / KMS-Activated
Windows 8.1 Enterprise / KMS-Activated
Windows 8.1 Enterprise N / KMS-Activated
Size: 2.86 GB
Language: en-US (English - United States)
Added resetbased hotfixes:
KB2899189, KB2933809, KB2942844
Added pending hotfixes:
KB2959977, KB2934018, KB2894853
SetupComplete.cmd phase (Pre-Activated indexes only):
Defender exclusion key for AutoKMS
Warning.vbs short non-genuine notification
dism for Image Exports
oscdimg for ISO mastering
Microsoft Diagnostics and Recovery Toolset (DaRT) 8.1
Added Info folder to Windows Setup dir to annoy credit theives
murphy78 diskpart/apply script v1.1.1
-Windows 8.1 with Update MSDN/ESD download
-Highly compressed ESD format.
-DaRT 8.1 integrated into boot.wim and winre.wim recovery options.
-EI.CFG is present. *You will need to extract the iso and delete this file to upgrade from a previous version of Windows*. You will also want to allow setup to download updates during upgrade process.
-I tried every damn thing I could think of to not have to change the default boot options. It simply will not correctly extract ESD files all the ime using the Windows Setup.exe program. I believe it has something to do with the way that esd compressed files are being handled in the extraction portion of setup. I believe they are not properly waiting until all the extraction threads are finished to proceed with the image mods that they do around the 88-95 percentish range.
-ESD lifecycle has reached it's end for pre-activated monthly versions using the default Windows Setup program (boot setup). To get around this issue, I've integrated my setup script from my diskpart/apply project. You can still try to use Windows Setup by closing the script or selecting the No option at the opening of the script.
-Previous v1 release had an issue with the recenv call in winre.wim. As a result it will simply reboot when you try to use it. Most people will never see this issue since most of the recenv is integrated into windows itself. However, to fix, you do the following:
-run admin prompt command:
select disk 0
list partition (find the one with 300mb)
select partition 3 (or whatever the number of your 300mb one is)
(use backslashes not forward slashes in directory locations for rest)
-Then turn on system file viewing in your control panel. copy/paste the winre.wim file from the recovery partition recovery/windowsre directory.
-mount the winre.wim index 1 using dism: dism /mount-wim /wimfile:c:/temp/winre.wim /index:1 /mountdir:c:/mount
-edit the c:/mount/windows/system32/winpeshl.ini file
-Change the line:
-Then unmount /commit and copy/paste over old file. dism /unmount-wim /mountdir:c:/mount /commit
-copy/paste it over the old one from recovery/windowsre in the 300mb recovery partition. Make sure you didn't use any forward slashes...
murphy78 Setup Script features:
-Multi-Boot, Fast Setup, Add drivers to PE environment, Add drivers to post-install offline image, Recovery image partition, Fully ESD compatible, split-wim compatible, No Extra system partition option for MBR users. -You can even shrink your recovery image after install and resize your partitions, though I haven't automated that part. You would just assign a drive letter to the recovery partition, copy/paste the install.wim to your system drive and export the image to an install.esd using recovery compress. Then you point reagentc at the osimage again.