abbodi1406

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

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>

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

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

@ youravinalarrrf your issue looks related to: wiaek002.inf 0x80070003 - ERROR_PATH_NOT_FOUND you could see this file for details: windows\inf\setupapi.dev.log if this path or the inf file in it is missing, you need to copy it from another source (like install.wim of your Win8.1 iso) \Windows\System32\DriverStore\FileRepository\wiaek002.inf_amd64_57f9361b96ceea4b

you can not i tried it and the shortcut did not work from desktop

thanks alot