abbodi1406

Member
  • Content count

    19
  • Joined

  • Last visited

Community Reputation

2 Neutral

About abbodi1406

  • Birthday 01/16/1986

Profile Information

  • OS
    Windows 8.1 x86
  • Country

Recent Profile Visitors

461 profile views
  1. Just an update for the situation now, March 2016 Client KB3138612 fixes the issue as well, for clean install systems at least
  2. It's not atomic bomb most of work is done manually i described it here: http://forums.mydigitallife.info/threads/?p=1254044
  3. This is custom-made solution that provide latest Windows Update Client version 7.6.7601.23453, which is part of July 2016 rollup update KB3172605 some of MDL members already seen it, and since August 2016 rollup didn't replace KB3172605, i thought it would be fine to promote the solution this WUClient version provides the long-awaited fix for the long scan issue in WU, which makes it a highly priority update that should be installed the official way of having this fix is by installing the July 2016 rollup KB3172605 (which require servicing stack update KB3020369 first) but some users may face issues with it (Intel Bluetooth, SSL cipher change.. etc), or simply don't want to install unwanted/unrelated fixes in order to get WU fix so, i ripped the WUClient components off KB3172605, those components are defined and deployed by sub-packages, i extracted/prepared/repacked those packages to be installed easily with DISM tool as individual .cab files this allow you to have the WU fix solely without other fixes in the rollup that you may not want or cause you problems, and without any prerequisites updates the solution also spare you from having to install monthly-changed win32k.sys update, or any other updates only one down-size of the solution, as a side effect you will get multiple enries for KB3172605 in "Installed Updates" panel (at least 2 for x86 / 3 for x64) and if you decided to install the whole KB3172605 rollup later, you will also get one more entry this is merely a cosmetic issue that don't decrease or affect the packages functionality you can install the packages yourself with dism, or recommended to use the scripts i made to automate the process Download: File: Windows6.1-KB3161647-x64.zip MD5: 1696dc0c8f38b4a0501130132bca6cc7 SHA1: 98f0300ad2d725c1025db482b4a88ac50a317f0d File: Windows6.1-KB3161647-x86.zip MD5: f8af8b2c1f25e2401b9735071062a576 SHA1: 98026dcd7e68bc23d91edee417870c9d9b178cf8
  4. No it's not, KB3172605 is completely enough to solve the long delay issue as permanent solution but it require prerequisite KB3020369
  5. Manually install KB3020369 > KB3172605
  6. Sure you can extract cabs and combine them, each will need it's own folder then, point dism to update.mum (or update-bf.mum) that's how simplix pack works acrually
  7. .msu files are digitally signed, you can't merge, modify or create a new one that the system would accept
  8. You can't get what doesn't exist defender don't have separate package on w7
  9. 1) Yes 2) You can integrate each sub-package .mum manually to avoid components, but that's an almost impossible mession due the large number of those packages the easier way would be by integrating the whole rollup, then use install_wim_tweak.exe to remove unwanted sub-packages 3) No, but as in 2, dism can integrate individual sub-packages 4) The rollup contain all hotfixes, except the ones listed in KB article as excluded p.s. 1500 update included: https://blogs.technet.microsoft.com/yongrhee/2016/05/20/enterprise-convenience-rollup-update-ii-2-for-windows-7-sp1-and-windows-server-2008-r2-sp1/ 5) With or without the rollup are practical
  10. Thanks for monitoring when i said telemetry components, i ment the ones included in rollup, it include: - Diagtrack service (KB3068708/KB3080149) - only a fracture of KB2952664, this fracture is latent/ineffective without the whole kb2952664 installed - telemetry points in UAC consent.exe (KB3075249), they also ineffective if Diagtrack service is off (just a guess), and KB3139923 already superseded it - upgrade facilitating WU client (KB3138612), can be easily blocked with registry DisableOSUpgrade "convenience rollup update" is useful even for up-to-date system (WU updates), because: - it contains almost all hotfixes and non-WU updates, which is basically what SP2 will have if it was released - the rollup unifies the components version to one, allowing an easy base for system - individual updates have superseded, duplicated components/files (different versions), which takes more reduntant space, and installing the rollup (newest version) allows Disk Cleanup to remove the old components and gain space as for KB971033, maybe it's re-requested because you didn't set the upgrade block policy so WU needs it to verify Win7 license before offering the upgrade (again just a guess) Regard the SFC integrity issue, here's an explanation for it: http://forums.mydigitallife.info/threads/?p=1231135 the issue is indeed a failure by msft and makes the rollup looks bad, but it's completely harmless
  11. Most great thing msft provided since win8.1 update specially it's LDR only, as all updates released in April/May 2016 GDR branch should have died when mainstream support ended it's the one that has been culpriting WU (and i don't mean the long search issue) as for those telemetry components, it's very enough and easy to disable Diagtrack service/schedule tasks.. and their effect is gone
  12. Unified Background Process Manager = Unified Scheduling Engine = Scheduled Task Process Manager you can export some task from taskschd to see that setting: UseUnifiedSchedulingEngine UBPM include System Events Broker and Time Broker services
  13. Possible, using unattend answer file RunSynchronousCommand in specialize pass runs under system account and have full access to registry <settings pass="specialize"> <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <RunSynchronous> <RunSynchronousCommand wcm:action="add"> <Path>REG ADD "HKLM\SOFTWARE\Microsoft\Windows Defender\Exclusions\Paths" /V "C:\Program Files\Rig\AutoPass.exe" /t REG_DWORD /d 0 /f</Path> <Order>1</Order> <Description>Registry</Description> </RunSynchronousCommand> </RunSynchronous> </component> </settings>
  14. It' better to merge them as Install.wim first, then convert it to esd although i doubt the size will drop if merge the two esd files (because of the solid compressed chunks), but you could try it the merge command is the same whether it's wim or esd dism /Export-Image /SourceImageFile:install.wim /SourceIndex:1 /DestinationImageFile:install2.wimdism /Export-Image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install2.esd /compress:recoveryorwimlib-imagex export install.wim all install2.wimwimlib-imagex export install.esd all install2.esd
  15. Of course you will have 7600 files, SP is an update to the RTM system, not a new system, it doesn't replace all of its components install_wim_tweak /p C:\mount /c Microsoft-Windows-Common-Modem-Drivers-Packagedism /image:C:\Mount /remove-package /packagename:Microsoft-Windows-Common-Modem-Drivers-Package~31bf3856ad364e35~x86~~6.1.7601.17514install_wim_tweak /p C:\mount /h /c Microsoft-Windows-Common-Modem-Drivers-Package