_14e30a.png)
_8126ce.png)
abbodi1406
Members
-
Joined
-
Last visited
Everything posted by abbodi1406
-
Yes but those are just the related to KB2919355 (Update1)
-
@BrokenZer0 there are an updated version of both text files for systems that already have KB2919355: 1. KB29750612. KB29668703. KB29599774. KB2934018for RTM systems that don't have KB2919355: 1. KB2975061 (Prerequisite)2. KB29668703. KB29193554. KB29320465. KB29375926. KB29384397. KB29599778. KB29340189. KB2938772
-
Updated i didn't use v4.5.3 since it's a pre-release
-
Maybe but i don't have free time at the moment
-
They can be integrated normally after 2919355 but 2919355 must be integrated first in a separate dism session "Install pending" has no affect or prevent the integration nevertheless, it's recommended to use latest released Update ISO that have 2919355 already integrated
-
You did read InstructionsRTM.txt right?
-
-
WMF4.0 (KB2819745) WMF3.0 (KB2506143)
-
Open install.wim file with hex editior then search for hex value: 3C 00 43 00 52 00 45 00 41 00 54 00 49 00 4F 00 4E 00if you got the first result before at the end of file, then skip to next result because this first result will be for winre.wim file now you replace the text values manually replacing each character or better, prepare the new value by adding dot (.) after each character so you can easily paste it instead of the current value 0.1.C.F.8.4.2.1.9.5.D.B.5.4.0.0.repeat the operation for each index (each search result)
-
Thank you both
-
I don't think that will work it's similar to if you try to use Dism from another system in second partition: Error: 0x80090006An error occurred. DISM could not be initialized in the local folder.Ensure that DISM is installed correctly and that all of the binaries are present
-
Of course but at install screen it will show the creation date as last modified date it's just something cosmetic
-
No, CreationTime is the date that get shown on the install screen when you choose between Editions and as i said, it represent the date when the image (index) was captured for the first time as new probaply, but when someone update that image with latest updates, tweaks.. etc, he would want the image to have new date
-
It's your choice it's only used by sfc.exe if there is a system file corrupted so it replace it yes
-
Hex-Edit the wim file itself xml entry will be at the end
-
The normal or the official way will be by applying then re-capturing the image (recommended to use vhd to easily delete it later) but you can do it manually by changing the CREATIONTIME of index's xml entry <CREATIONTIME> <HIGHPART>0x01CF7F87</HIGHPART> <LOWPART>0xD084E5D3</LOWPART> </CREATIONTIME>
-
C:\Windows\WinSXS\Backup AFAIK, is required for Windows Resource Protection (sfc) based on the refreshed Windows 8.1 released ISOs, i use this wimscript.ini exclusion list: [ExclusionList]\Users\Administrator\Windows\Logs\CBS\*\Windows\Logs\DISM\Windows\Logs\PBR\Windows\Panther\Windows\Prefetch\Windows\System32\Sysprep\Panther\Windows\System32\Sysprep\Sysprep_succeeded.tag\Windows\System32\winevt\Logs\*\Windows\Temp\*\Windows\WinSxS\ManifestCache\*
-
BTW, i made same procedure and image installed just fine all updates are integrated, except "Extra" category when you say "Windows Update Downloader" you mean the built-in one in Wintoolkit?
-
KB2533552 is an essential servicing stack update and every running system should have it
-
express cab contains only the update manifest files + xml file.. those are used by WU to identify the original package contents and to determine what components of it are needed for the system so it download them only i.e. if the update are multilingual, it will download only lang resources matching your system only WU knows how to handle this mechanism so, express cab are useless and cannot be used for integration
-
1) Both use the same Updates Lists 2) _IE11, and _NotAllowedOffline (after installing the system)
-
Only one update not included: Security Update KB2954853
-
Try to git rid of queued operations: %windir%\Microsoft.NET\Framework64\v4.0.30319\ngen.exe executeQueuedItems /silent
-
Because it's designed to handle KB2533552 this way
-
KB2533552 cannot be integrated offline, this is by design from MS exclusive="true" allowedOffline="false"KB2603229 however, can be integrated (offline or online), but this will make it just a null entry in the updates list, it doesn't allow the actual fix to be applied (updatewowregisteredowner.exe) therefor, it must be executed online directly by using the .msu file (double-click)
