Oh that's right! A metered connection coupled with a 12 hour span to limit restarts is a sort of kinda workaround.
Same here... People run software that sort of butchers Windows in the name of whatever terrible thing they think Windows is doing in their systems "this week" ("spying on them," sending their tax dodges to the IRS, revealing their pizza orders to the "rabid Russians", or whatever other nonsense they imagine)--and then they forget about this garbage software being installed--a new update comes along and their "protective" software interferes with it and they begin having major problems--which of course they dutifully blame on Microsoft... It has been clinically proven, time and again, that the buggiest component in any given computer system is the one that sits between the keyboard and the chair...!
Guys again offtopic going are we? I want you guys to run these 2 commands in sequence in elevated command prompt. Code: Dism.exe /online /Cleanup-Image /AnalyzeComponentStore Dism.exe /online /Cleanup-Image /StartComponentCleanup Just let me know if they error out after KB3189866 is installed. Nothing fancy. They just clean up all the old updates and free up space. Clean and tidy Windows is a healthy Windows.
KB3189866 is 14393 I did what the OP asked: Fresh install with 14393.187 x64 iso (offline updated): Code: Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. Alle rechten voorbehouden. C:\Windows\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\Windows\system32>dism /online /cleanup-image /analyzecomponentstore Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [===========================99.3%========================= ] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 7.58 GB Actual Size of Component Store : 7.40 GB Shared with Windows : 5.42 GB Backups and Disabled Features : 1.85 GB Cache and Temporary Data : 125.01 MB Date of Last Cleanup : 2016-07-16 14:39:50 Number of Reclaimable Packages : 0 Component Store Cleanup Recommended : Yes The operation completed successfully. C:\Windows\system32>dism /online /cleanup-image /startcomponentcleanup Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [==========================100.0%==========================] The operation completed successfully. C:\Windows\system32> SCC is now running on a x86 system with KB3189866 installed by WU. Code: C:\Windows\system32>dism /online /cleanup-image /startcomponentcleanup First gave error 2 (file not found) Then i did a /analyzecomponentstore first and after it the scc again and it ran fine. Now running it on my mainsystem x64 Pro en-US (CU installed by WU): Code: Microsoft Windows [Version 10.0.14393] (c) 2016 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>sfc /scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations. C:\WINDOWS\system32>dism /online /cleanup-image /analyzecomponentstore Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [===========================99.3%========================= ] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 6.47 GB Actual Size of Component Store : 6.45 GB Shared with Windows : 5.62 GB Backups and Disabled Features : 500.34 MB Cache and Temporary Data : 335.75 MB Date of Last Cleanup : 2016-07-26 03:27:39 Number of Reclaimable Packages : 0 Component Store Cleanup Recommended : Yes The operation completed successfully. C:\WINDOWS\system32>dism /online /cleanup-image /startcomponentcleanup Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [=========== 20.0% ] Error: 2 The system cannot find the file specified. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log C:\WINDOWS\system32> Error but after re-doing it againg it showed succesfully completed: Code: C:\WINDOWS\system32>dism /online /cleanup-image /analyzecomponentstore Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [==========================100.0%==========================] Component Store (WinSxS) information: Windows Explorer Reported Size of Component Store : 6.47 GB Actual Size of Component Store : 6.45 GB Shared with Windows : 5.62 GB Backups and Disabled Features : 500.34 MB Cache and Temporary Data : 335.75 MB Date of Last Cleanup : 2016-07-26 03:27:39 Number of Reclaimable Packages : 0 Component Store Cleanup Recommended : Yes The operation completed successfully. C:\WINDOWS\system32>dism /online /cleanup-image /startcomponentcleanup Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 [=========== 20.0% ] The operation completed successfully. C:\WINDOWS\system32>
I know about that. I found out it's broken in build 14926 by the antecedent of that post. I only mentioned it.
Oh, I see. But, it will try to fix the issues until it gets to 19% before giving the usual resource-protection error.
But it says completed at 20%. Something funky is going on with this update. Previously, it used to complete till 100%
I know it’s late in the day to mention it, and in all probability you’ve already considered it, but there’s still no harm in mentioning it. So don’t you have a System Restore Point to take your system back in time to before this whole adventure started? That’s what the much neglected SRPs are for and, despite the general contempt for and avoidance (even disabling) of them, they are a damn sight neater than chasing ghosts afterwards.
I believe abbodi1406 once told me when the progress bar ends before showing 100% but the cmd is "completed", it's a lag at the api. Most of the times when you run a command once, the second time the bar goes to appr. 20% and there is a completion shown, try resetbasing a boot.wim or winre.wim twice without adding an update between the 2 commands.