After integrating those updates and saving changes, in order to reduce file size, is the following code good to add extra compression? Code: dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\boot.wim /sourceindex:1 /destinationimagefile:W:\win81aio\win81x64\sources\boot2.wim /checkintegrity /compress:max dism /export-image /sourceimagefile:W:\win81aio\win81x64\sources\boot.wim /sourceindex:2 /destinationimagefile:W:\win81aio\win81x64\sources\boot2.wim /checkintegrity /compress:max I guess no issues come up at boot/install time... Moreover, to save even more space can I export only index 2 and leave index 1 out?
It seems that yesterdays patch Tuesday introduced strange connectivity issues in Internet Explorer. Opening websites from Frequent list or from browsing history randomly displays "internet explorer cannot display the page" error. This is happening on two different systems. Is anyone facing this problem too?
nothing like that here, have 4 different systems on 2 different networks with no issues. Are both of your systems on the same network? If possible move one to another network temporarily to test.
Yes. Both of my systems are on the same network. Strangely, no problems with Firefox, torrents and whatsoever. Probably just need to completely reset IE, clean cache and so on..
WinPE images (boot.wim, winre.wim) accept resetting the component store offline which can reduce there size while the image is mounted: Code: dism /Image:C:\mount /Cleanup-Image /StartComponentCleanup /ResetBase wim imagex are max compressed by default, so you don't need to specify compress:max no, both are required to get a setup boot.wim
You *can* but I really wouldn't recommend it. You technically only need a few things to do a boot install using Windows' default setup: -boot.wim with bootable index in the sources\ folder -boot and efi folders with respective bcd files and bootx64.efi if using x64 disc -bootmgr and bootmgr.efi -sources folder with install.wim/esd, lang.ini and setup.exe Everything else is for upgrades or support; but this is off-topic. You can bring it up in the WinIntegration thread if you want.
The problem is that it's not Windows that is causing this to show up. It's wuapp/wuauserv that is causing this to show up. That program checks all the installed packages and builds a database. Normally the bing thing doesn't show up unless you enable the Microsoft Updates (updates for other microsoft products) But it decides how to list the microsoft optional downloads depending on what it finds in that database and hide list. So to get it to stop showing those bing things, you have to add the "Hide" to the database. It doesn't really use the registry except for beta flagging and stuff.
Assuming im using a Win 8.1 x86 pro R2 (April) source from scratch with WHDownloader, is this a reasonable order to be up to date when offline servicing? Mount Install one by one: Windows8.1-x86\Baseline\Windows8.1-KB2966870-x86.cab Windows8.1-x86\Baseline\Windows8.1-KB2959977-x86.msu Windows8.1-x86\Baseline\Windows8.1-KB2934018-x86.msu Windows8.1-x86\Baseline\Windows8.1-KB2975061-x86.msu /Cleanup-Image /StartComponentCleanup /ResetBase ? Windows8.1-x86\General\*.* Windows8.1-x86\Hotfix\*.* Windows8.1-x86\Security\*.* Windows8.1-x86\Additional\CameraCodecPack\*.* Windows8.1-x86\Additional\WinHelp\*.* Add Windows To Go Workspace Add Win7 Games Remove Win 8.1 metro apps Remove Win 8.1 Remove-DefaultAppAssociations Remove Win 8.1 Add App Associations dism /image:' & $Mount & ' /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:"' & $BASE & '\Windows8.1-x86\Windows8.1-x86\sources\sxs Windows8.1-x86\Additional\NET35\*.* Add key Add overlay (copy a few files) Intergrate Drivers Termserv terminal server patch UnMount Commit _DISM($imagex & " /info " & $SourceUpdatesWim & " " & $Index & ' "' & $IndexDescription & ' (' & @MDAY & '\' & @MON & ')" "' & $IndexDescription & ' (' & @MDAY & '\' & @MON & ')"')
Cheers, it worked great. I really don't get why MS put the pending flag on a prerequisite. They knew damn well what they were doing.
There is difference between number of updates needed to make a fully updated ISO. If you check murphy's release, it contains many less updates than WHDownloader offers (excluding Hotfixes). For example, KB2975061, that is recommended to be integrated on top of all but murphy did not integrate this. While, whether you install murphy's windows or integrate all updates of WHDownloader, at last you will get same result, No update is available at Windows Update. So, where is the difference?