It's to update the setup components. You'd have to refer to the actual update KB support article to see what is fixed.
Sir, I guess you missed this part... "Also after integrating in winre.wim we have to update setup files of ISO. How to do that?"
go into mount\sources\ and sort by date. Any ones that were modified by updating will have timestamp from time of modification. Copy them to ISO\sources\ folder. Also copy setup.exe from mount\ to root of ISO\
Murphy78 i have some question about Create partitons.txt and Applyimage-BIOS.bat i have these two files rem == CreatePartitions-BIOS.txt == rem == These commands are used with DiskPart to rem set up the drive and create three partitions rem for a BIOS/MBR-based PC. rem Adjust the partition sizes to fill the drive rem as necessary. == select disk 0 clean rem == 1. System partition ====================== create partition primary size=350 format quick fs=ntfs label="System" assign letter="S" active rem == 2. Windows partition ===================== rem == a. Create the Windows partition ======= create partition primary rem == b. Create space for the recovery image shrink minimum=15000 rem == c. Prepare the Windows partition ====== format quick fs=ntfs label="Windows" assign letter="W" rem == 3. Recovery image partition ============== create partition primary format quick fs=ntfs label="Recovery image" assign letter="R" set id=27 list volume exit this is the createpartitons.txt when i try to execute from USB Diskpart /s F:\createpartitons.txt dont make nothing And also i have and other one the Applyimage-bios.bat rem == ApplyImage-BIOS.bat == rem == These commands deploy a specified Windows rem image file to the Windows partition, and configure rem the system partition. rem Usage: ApplyImage WimFileName rem Example: ApplyImage D:\Images\ThinImage.wim == rem == Copy the image to the recovery partition == md R:\RecoveryImage copy %1 R:\RecoveryImage\Install.wim rem == Apply the image to the Windows partition == dism /Apply-Image /ImageFile:"R:\RecoveryImage\Install.wim" /Index:1 /ApplyDir:W:\ rem == Copy boot files to the System partition == W:\Windows\System32\bcdboot W:\Windows :rem == Copy the Windows RE image to the :rem System partition == md S:\Recovery\WindowsRE xcopy /h W:\Windows\System32\Recovery\Winre.wim S:\Recovery\WindowsRE\ :rem == Register the location of the recovery tools == W:\Windows\System32\Reagentc /Setreimage /Path S:\Recovery\WindowsRE /Target W:\Windows :rem == Register the location of the :rem push-button reset recovery image. == W:\Windows\System32\Reagentc /Setosimage /Path R:\RecoveryImage /Target W:\Windows /Index 1 :rem == Verify the configuration status of the images. == W:\Windows\System32\Reagentc /Info /Target W:\Windows how can i make to execute these to files right Createpartitons.txt and Applyimage-bios.bat. Which are the right way to execute these two? Can you help me please?
You have to boot into a WinPE environment, such as a win8 boot dvd/usb. Then you press shift-f10 to open admin command prompt. From there you do: Code: Diskpart /s F:\createpartitions.txt f:\Applyimage-BIOS.bat f:\sources\install.wim This assumes that F: is your USB drive in the WinPE. You should verify it before running the scripts.
If I understand correctly, I can "/cleanup-image /startcomponentcleanup" on Offline integration but cannot use "/resetbase" option but when using sysprep/capture method I can use it. Right? Also, this is what I found in your "Clean-and-ResetBase-WinSxS-Folder.cmd". Code: @echo offcolor 1f pushd "%CD%" CD /D "%~dp0" (NET FILE||(powershell -command Start-Process '%0' -Verb runAs -ArgumentList '%* '&EXIT /B))>NUL 2>NUL :-------------------------------------- ECHO ------------------------------------------------------------------------------- echo. WinSXS ResetBase script ECHO ------------------------------------------------------------------------------- ECHO This script will remove all hotfix uninstall information and make all changes ECHO permanent. I personally think you should only use this as a last resort to ECHO re-capture a few hundred megs. I have found it to be very error-prone while ECHO installing future updates. You have been warned. ECHO ------------------------------------------------------------------------------- CHOICE /c YN /n /M "Run this script? (Y/N): " set errortemp=%ERRORLEVEL% IF %ERRORTEMP% EQU 2 EXIT IF %ERRORTEMP% EQU 0 EXIT dism /online /cleanup-image /startcomponentcleanup /resetbase ECHO ------------------------------------------------------------------------------- echo. Finished ECHO ------------------------------------------------------------------------------- echo Press any key to exit... pause>NUL "This script will remove all hotfix uninstall information and make all changes permanent. I personally think you should only use this as a last resort to re-capture a few hundred megs. I have found it to be very error-prone while installing future updates. You have been warned." So why recommend "/resetbase" when it is vulnerable to errors in future updates? Isn't it safe to just do "/cleanup-image /startcomponentcleanup" on all 3 files and finish the job?
It's a gamble. If you use it on a newly released update and there's a problem with it, you won't be able to remove it. If you use it on a leaked update, you won't be able to install the final update. Also, no, you cannot do the normal /startcomponentcleanup because of pending flag as well.
Hello Sire (murphy78), Since The Pirate Bay went haywire, there haven't been any activity of yours, as it's back up and running now, I was wondering, when can we expect updated versions of your Office Pro Plus and Windows 8.1 AIO be released Apologies, as this comment may not be completely related to this thread. Thank You for everything you do.
Thank You for replying. I was checking on the profile mentioned in your Facebook account. Thanks for the update. I don't have enough posts yet to reply via, PM . Sorry about that
Thanks murphy78 Sir, I successfully created updated iso of Enterprise SKU. Passes sfc /scannow. I downloaded your Windows 7/8.1 AIO releases for last month. You mentioned... Code: Pro-Tip to make your own smaller images of single index versions: dism /export-image /sourceimagefile:c:\win81dist\sources\install.swm /swmfile:c:\win81dist\sources\install*.swm /sourceindex:1 /destinationimagefile:c:\win81dist\sources\install.wim I understand the code but I want to export multiple indexes, how to do that for if the file is .swm and .wim? Also, will the setup files need to be changed or updated?
You can export them all if you just want to work with a gui program such as GimageX v2: Code: for /l %x in (1,1,58) do (dism /export-image /sourceimagefile:c:\win81dist\sources\install.swm /swmfile:c:\win81dist\sources\install*.swm /sourceindex:%x /destinationimagefile:c:\win81dist\sources\install.wim) To get more than one index in an install.wim, you just export more than one index to the same destination file.
Great! I would definitely like to do that with that program. So for the wim file, if I understand correctly, I have to do this, Code: dism /export-image /sourceimagefile:c:\win81dist\sources\install.wim /sourceindex:1 /destinationimagefile:c:\win81dist\sources\install.wim and then Code: dism /export-image /sourceimagefile:c:\win81dist\sources\install.wim /sourceindex:2 /destinationimagefile:c:\win81dist\sources\install.wim and so on...? And please tell how to convert your swm files to wim files? I also read what you wrote all about esd compression and it's limitations. So how many indexes it can handle perfectly and upto what size? I would like to export few of your indexes into esd if possible so that the size of 9.3GB would not be an issue for me. And what does (1,1,58) specify in the command you mentioned above? Though, I got a rough idea but please tell about each parameter.
I just installed your Windows 8.1 AIO Dec2014 x64 version on VMware with ProWMC SKU and did a sfc /scannow. It resulted in errors at 36%. This is the first time I experienced errors on your release. Why so? CBS.log file attached in .zip as size was greater than limit.
Code: (F) STATUS_OBJECT_NAME_NOT_FOUND "C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.17415_none_0a5dfdcc33c06e7e\MSDTC.LOG"
Sir murphy78, did you investigate the problem? Please throw some light on it... I never had this problem with any of your releases, may be because of /resetbase etc. you used (I may be wrong!). Is this a matter of concern or there is some other reason for the error? PS: I will be checking the x86 version today, will tell you if anything goes wrong. EDIT: Yes, the x86 version also fails at 45%