_14e30a.png)
_8126ce.png)
abbodi1406
Members
-
Joined
-
Last visited
Everything posted by abbodi1406
-
Updated however, i didn't have the time to test and verify it
-
;1[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]"NavPaneShowAllFolders"=dword:00000001;2[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced]"HideDrivesWithNoMedia"=dword:00000000;3[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\CabinetState]"FullPath"=dword:00000001"Settings"=hex:0C,00,02,00,0B,01,00,00,60,00,00,00as for 4, there is no generic or simple settingeach folder type has different values, each view type has different values as well see here: http://www.msfn.org/board/index.php?showtopic=142961
-
Data base for all updates released through WU i don't there is an easy way to read its conents, it's really messy
-
KB3068708 still in Download Center Edit: Both are back on, same version
-
Yes, despite the supersedence, WU still asks for KB2533552 (as SP1 KB976932) i was only refering to the condition of the update itself amd we already know and experienced that WU request superseded updates sometimes
-
No, it's not weird https://support.microsoft.com/en-us/kb/3057448 "The update is not applicable to your computer" error when you install Windows updates Cause number 1: Update is superseded KB3020369 fully and directly supersede KB2533552 thus, if KB3020369 is installed, KB2533552 cann't be installed using the .msu file the workaround (that even WU use) is to use the inside .cab file to integrate the update online by dism tool: dism /online /add-package:Windows6.1-KB2533552-x64.cab
-
I think he means: C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
-
Yes, possible but not tested, so i don't guarantee it works
-
Did you use latest addon? both updates should not be shown if so msp are like msi, cann't be integrated offline
-
BTW, KB3022345 had been killed and not available for download
-
Or you can add registry value to disable it [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Gwx]"DisableGwx"=dword:00000001via admin cmd: reg add HKLM\Policies\Microsoft\Windows\Gwx /v DisableGwx /t REG_DWORD /d 1 /f
-
Actually, the two updates are indeed an MSP files and should accept converting from exe to msp
-
I really don't know what it depends on, but it's more related to the serviced image not the Host OS i guess on the size of updates and how many are already in the image, how many is pending but in my experience, after +100 update or so, the dism command will be become slower and slower in adding the packages the command is the same for dism /add-package, each update need its /packagepath: parameter of course using this grouping will recuire some batch scripting and using the inner .cab files is much better and faster in integrating the main script that i learned that concept from is Installer For Windows Updates V28 by Burf however it's intended for Online operation and contains various checks there is a reduced version i modded without most checks and for offline integrating: InstallerV27z.zip
-
-
The two new security updates KB3023224 and KB3035490 are already included in the rollup
-
Regarding KB3021952: same status as last month
-
Updated with new rollup already include security update KB3037581
-
1. Prerequisites: KB2670838 / Platform update, IE11 won't accepted/integrated without it KB2786081 KB2834140 KB2871997 / replace KB2639308, KB2533623, KB2731771 KB2882822 KB2888049 KB2970228 / replace KB2729094 2. IE11 main packages: KB2841134 / IE11 KB2849696 / IE-Spelling-en.msu KB2849697 / IE-Hyphenation-en.msu 3. IE11 LangPack: IE11-Windows6.1-LanguagePack-x64-de-de.msu IE-Hyphenation-de.msu IE-Spelling-de.msu 4. IE11 Updates: KB2976627 KB3021952 KB3032359 KB3023607
-
Sorry for being late i honestly tested only one image (HomeBasic) and can confirm it works so, the first group of your code is correct and should work imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomeBasicimagex /commit /append c:\mount HomeBasicimagex /unmount c:\mountimagex /flags "HomeBasic" /info install.wim 2 "HomeBasic" "HomeBasic"imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomePremiumimagex /commit /append c:\mount HomePremiumimagex /unmount c:\mountimagex /flags "HomePremium" /info install.wim 3 "HomePremium" "HomePremium"imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:Professionalimagex /commit /append c:\mount Professionalimagex /unmount c:\mountimagex /flags "Professional" /info install.wim 4 "Professional" "Professional"imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:Ultimateimagex /commit /append c:\mount Ultimateimagex /unmount c:\mountimagex /flags "Ultimate" /info install.wim 5 "Ultimate" "Ultimate" however, the second group won't work, because the mounted image c:\mount already upgraded once, and upgrading an upgraded edition will mostly cause errors in the image
-
You know, imagex has a nice feature that makes the process much easier: APPEND IMAGEX [FLAGS] /COMMIT mount_path ["image_name"]Commits the changes made to a mounted image without unmounting the image. mount_path - The path of the mounted image to commit. image_name - If the /append flag is set, then a unique image name must be provided.Accepted FLAGS: /APPEND Captures the changes made to the wim into a new image in the wim. /TEMP Specifies the path where temporary files are stored.Example: imagex /commit c:\mounted_images imagex /commit /append c:\mounted_images new_image_nameso instead of copied/duplicating wim files and then re-merging, one could do it with one file: imagex /mountrw install.wim 1 c:\mountDISM /Image:c:\mount /Set-Edition:HomeBasicimagex /commit /append c:\mount HomeBasicimagex /unmount c:\mountand repeat the process for other editions afterwards, change the images' description and edition flag imagex /flags "HomeBasic" /info install.wim 2 "HomeBasic" "HomeBasic"
-
KB2834140 is a bi-update, it can be installed (offered) with/without platform update KB2670838 so if you installed it before KB2670838, you have to install it afterwards too
-
Installing WMF4.0 KB2819745 (or WMF3.0) will make KB3006625 superseded, thus removed
-
The 5.2 MB is KB3023607, it's bundled with both updates deepclean removes superseded updates correctly WU is the one requesting superseded updates, it's a total mess in Windows 7
-
Delete the two updates and re-download them
-
Mainstream support ended latest updated CABs: http://www.microsoft.com/en-us/download/details.aspx?id=43898
