Jump to content

abbodi1406

Members
  • Joined

  • Last visited

Posts posted by abbodi1406

  1. ·

    Edited by abbodi1406

    Found something really cool, especially for Windows 7 that lacks the "ResetBase".

     

    http://forums.mydigitallife.info/threads/59389-Dism-A-Powerful-Tool-of-Clean-and-Tweak

     

    I gained back 2,5 GB from a fresh install with it.

    For me it just removes \Backup and \ManifestCache contents  :g: 

     

    ----

    the best experience W7's winsxs is to keep the higher version component + RTM version (6.1.7600.16385 and 6.1.7601.17514)

    and remove the inbetween :D

  2. Hotfix rollups are not offered through WU, they are found using there KB articles

    and those rollups are cumularive updates, meaning they already contain and supersede earlier updates and some "not yet published" security updates

     

     

    as for KB3063911, it is the name that appear when you check installed programs

    but the rollup is released under KB3064711

  3. ·

    Edited by bphlpt
    fixed link

    ;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,00
    as for 4, there is no generic or simple setting

    each folder type has different values, each view type has different values as well

    see here:

    http://www.msfn.org/board/index.php?showtopic=142961

  4. After windows installed in VMware, I check "Installed updates" and I couldn't find KB2533552 .....I tried to install this update manually and it says "The update is not applicable to your computer" , weird?

    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
  5. 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 :D

    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

  6. Integrating updates one by one will always take more time than grouping updates in one dism session

    of course not all updates, each session can handle 120 ~ 150 update

  7. 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

  8. Hopefully, abbodi1406 will respond and confirm whether I interpreted his instructions correctly.

    Cheers and Regards

    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

  9. 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_name

    so 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:\mount

    and repeat the process for other editions

    afterwards, change the images' description and edition flag

    imagex /flags "HomeBasic" /info install.wim 2 "HomeBasic" "HomeBasic"
  10. Hi,

     

    another issue I have:

     

    because of the problems with some update from last patch-day I integrate now using rhahgleuhargh's UL from february 24-02-2015, adding the working updates and KB3000483.

     

    Testing with only updates from the list (with RDP 8.1 and IE11), for x86 updates from patch-day march are requested by WU, of course ;).

    For x64 WU is asking not only for updates from patch-day march, it request KB2834140 (IE prerequisite, 811KB) too, even if this KB is in the UL and is shown as installed in the list of installed updates and I don't find the reason why!

    It's not depending from OS-language.

     

    Did anyone experience the same issue?

     

    TNX, Thiersee

    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