abbodi1406

Howdy @Atari800XL imagex time is the one reported as elapsed it after finish applying? for me i used echo %time% before and after imagexin a script, the difference was ~ 3:40, while imagex reported 3:00 still, manual observation of WinNTSetup applying gives ~ 4:20 BTW, where do i find WinNTSetup log? and it detects 1st index of UUP as 64bit https://i.imgur.com/yNRfOpq.png

AFAIK, Win7 only got SP2

No you don't need strangely, i have some policies set, and WU settings page sometimes don't show that administrator messege

Well, did you try to delete the whole key and see if the messege in Settings goes away? reboot might be required

No you either edit install.wim registry, or use RunSynchronousCommand in autounattend.xml / specialize pass

That's definitely the right way to do, no chopping i use similar approch i can actually "prevent" installing most of "unneeded" system apps with deleteing one registry key for each prior installation (or during setup pass specialize) set key=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\InboxApplications FOR %%i IN ( holocamera holoitemplayerapp HoloShell PPIProjection AppRep.ChxApp ContentDeliveryManager CortanaListenUIApp Cortana Holograms HolographicFirstRun ParentalControls SecHealthUI SecureAssessmentBrowser XboxGameCallableUI ) DO ( FOR /F %%a IN ('reg query %key% /s /f %%i /k 2^>nul ^| find /i "InboxApplications"') DO IF NOT ERRORLEVEL 1 (reg delete %%a /f 2>nul) ) note: in ver 1703, preventing Cortana will make Start Menu greyed (functional but not clickable)

Win 10 v1703 cumulative update is still lite, so it won't fail for now by chopping i mean removing internal packages and "nLiting" the OS extensively how did you reduced your OS?

Check if this registry path exist HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU

Chopping and updating Windows 10 is a lost cause you can have one of them, not both

Applying any WU group policies, or disabling Delivery Optimization will make it show

Yes, MSU files uses WUA engine however, dism + cab files can pass that

There might been a standalone installer, but i could not find anyone kept its links version RTM: https://support.microsoft.com/en-us/help/18520 version 11.0.11: http://www.microsoft.com/en-us/download/details.aspx?id=43898 version 11.0.15: x64 http://download.microsoft.com/download/7/7/D/77DEA30E-F617-4088-9352-FDBFED2987EE/IE11-Windows6.1-KB2841134-x64.cab x86 http://download.microsoft.com/download/7/7/D/77DEA30E-F617-4088-9352-FDBFED2987EE/IE11-Windows6.1-KB2841134-x86.cab version 11.0.17: x64 http://download.microsoft.com/download/5/C/7/5C7074F0-CE81-4612-902F-DAAF3061B959/IE11-Windows6.1-KB2841134-x64.cab KB3038314 (update version 11.0.18) http://www.catalog.update.microsoft.com/Search.aspx?q=KB3038314+Internet+Explorer+11+for+Windows+7

Workaround: https://blogs.msdn.microsoft.com/vsnetsetup/2016/03/28/a-certificate-chain-could-not-be-built-to-a-trusted-root-authority-2/ More details: https://support.microsoft.com/en-us/help/3149737

Just an update for the situation now, March 2016 Client KB3138612 fixes the issue as well, for clean install systems at least

It's not atomic bomb most of work is done manually i described it here: http://forums.mydigitallife.info/threads/?p=1254044

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

No it's not, KB3172605 is completely enough to solve the long delay issue as permanent solution but it require prerequisite KB3020369

Manually install KB3020369 > KB3172605

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

.msu files are digitally signed, you can't merge, modify or create a new one that the system would accept

You can't get what doesn't exist defender don't have separate package on w7

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

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

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

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