Windows 10: Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138

Page 6 of 8 FirstFirst ... 45678 LastLast

  1. Posts : 23
    Windows 10 Home
       14 Apr 2017 #50

    TairikuOkami said: View Post
    Somewhat odd component cleanup, I usually get 2x100% or 20% and completed, but 9,6%, that is a new.
    I have just noticed on the screen, that component store is corrupted, RestoreHealth still does not work.
    so DISM restore health w/o source still not work ? s guess i need to stickk with 1607 till this solved
      My ComputerSystem Spec

  2. Cliff S's Avatar
    Posts : 21,213
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       14 Apr 2017 #51

    miqbaln said: View Post
    so DISM restore health w/o source still not work ? s guess i need to stickk with 1607 till this solved
    Why? Restore health is just for the component store in the Windows Side by Side(WinSxS) folder, where system files that are hard linked, or copies of them, with changes are kept, then automatically cleaned up sometime, by Automatic Maintenance anyhow:

    Why is WinSxS so large? has been asked by many Windows users. While this question has been discussed in blog posts, this topic goes into a little more details about the concepts behind the component store (specifically the WinSxS folder) and then provides links to topics that highlight ways to better manage the size of the WinSxS folder.
    The short answer is that the WinSxS folder isnt as large as it may appear at first glance because size calculations can include Windows binaries located elsewhere which makes the WinSxS folder seem larger than it really is.
    The Windows component store and WinSxS folder

    The WinSxS folder is located in the Windows folder, for example c:\Windows\WinSxS. Its the location for Windows Component Store files. The Windows Component Store is used to support the functions needed for the customization and updating of Windows. Here are some examples of how the Windows Component Store files are used:
    Using Windows Update to install new component versions. This keeps systems secure and up-to-date.

    Enabling or disabling Windows features.

    Adding roles or features using Server Manager.


    Moving systems between different Windows Editions.

    System recovery from corruption or boot failures

    Uninstalling problematic updates

    Running programs using side-by-side assemblies

    The Windows Component Store was first introduced in Windows*XP to support side by side assemblies. Beginning in Windows*Vista, the component store was enhanced to track and service all of the components that make up the operating system. Those different operating system components track objects such as files, directories, registry keys, and services. Specific versions of components are then collected together into packages. Packages are used by Windows Update and DISM to update Windows. The components and packages used in a Windows installation are processed by the Windows Component Store. Determining the size of the Windows Component Store is complicated by the fact that many of the files are used by Windows from directories outside the Windows Component Store using a technique known as hard linking. In such cases, the files from a component version appear both inside and outside the Windows Component Store. By using hard linking Windows is able to appear to keep multiple copies of the same file without actually taking the added space for multiple copies.
    Manage the Component Store
      My ComputersSystem Spec

  3. f14tomcat's Avatar
    Posts : 36,218
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       14 Apr 2017 #52

    Cliff S said: View Post
    Why? Restore health is just for the component store in the Windows Side by Side(WinSxS) folder, where system files that are hard linked, or copies of them, with changes are kept, then automatically cleaned up sometime, by Automatic Maintenance anyhow:

    Manage the Component Store
    That reminds me....I forgot to run your "Magic Batch File" after last Insider.....TKS :)
      My ComputersSystem Spec

  4. slicendice's Avatar
    Posts : 3,439
    Windows 10 Pro x64 v1803 Build 17134.228 (Branch: RS4 Release Preview)
       14 Apr 2017 #53

    Bree said: View Post
    Look in Reliability History. It shows as a 'Critical event' with a red cross. I have seen it on every system I've updated - 1511, 1607 and 1703. The MRT seems to run successfully to completion, but then fails to close correctly.
    Only Critical Reliability History events I see is MicrosoftEdgeCP.exe crashes. Those I have a lot! :)

    I am sure I can fix this by modifying permission a bit...but haven't bothered yet.
      My ComputersSystem Spec

  5. Cliff S's Avatar
    Posts : 21,213
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       14 Apr 2017 #54

    f14tomcat said: View Post
    That reminds me....I forgot to run your "Magic Batch File" after last Insider.....TKS :)
    I get the corrupt .mum file error from "C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum" like everyone else, and it cannot be digitally signed like it's .cab file is, I's probably leftover & forgotten from internal testing.

    Also the winsat formal is giving me a "no adapter for device" error for some reason since I upgraded to CU:

    in this protion of winsat
    Extended Media Assessment '-input C:\WINDOWS\Performance\WinSAT\Clip_1080_5sec_VC1_15mbps.wmv -video offscreen -audio mute -prevent3pc -width 100%m -height 100%m -constrain -savereg -autoprofname -expfrmmin 135 -expfrmmax 150 -overrideframetype prog'
    ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for device 0ERROR: no adapter for d
    I have had no problems though, so go figure.
    The video file plays when I go there, maybe the pooped on this too.
    Click image for larger version. 

Name:	image.png 
Views:	7 
Size:	129.9 KB 
ID:	130039

    Click image for larger version. 

Name:	image.png 
Views:	8 
Size:	1.53 MB 
ID:	130038
      My ComputersSystem Spec

  6. slicendice's Avatar
    Posts : 3,439
    Windows 10 Pro x64 v1803 Build 17134.228 (Branch: RS4 Release Preview)
       14 Apr 2017 #55

    Here is the Latest and Maintained Microsoft topic on Managing The Component Store:

    Hardware Dev Center > Manufacture > Desktop Manufacturing > DISM - Deployment Image Servicing and Management > DISM How-to Topics (Deployment Image Servicing and Management) > Manage the Component Store

    The link provided earlier in this thread is outdated. I read these topics under the new link all the time! Very useful reading when learning how Windows works and what tools are available for maintaining a clean, up to date installed system and default system image for recovery.

    Cheers! :)
      My ComputersSystem Spec

  7. slicendice's Avatar
    Posts : 3,439
    Windows 10 Pro x64 v1803 Build 17134.228 (Branch: RS4 Release Preview)
       14 Apr 2017 #56

    Has anybody tried to Clean Install Windows 10.0.15063.0 from the official ISO created with Media Creation Tool, updated installation to 10.0.15063.138, without entering insider preview at all, then run the following command:
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    and get it to complete 100% successful???

    Sounds to me that this flight signing package has to do with insider builds, as the ISO I have converted from the Media Creation Tool created ISO, to being serviceable, run the command offline just fine:
    Code:
    DISM /Cleanup-Image /RestoreHealth
    I will play around with this further to see if this can be fixed somehow...
      My ComputersSystem Spec

  8. Cliff S's Avatar
    Posts : 21,213
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       14 Apr 2017 #57

    slicendice said: View Post
    Has anybody tried to Clean Install Windows 10.0.15063.0 from the official ISO created with Media Creation Tool, updated installation to 10.0.15063.138, without entering insider preview at all, then run the following command:
    Code:
    DISM /Online /Cleanup-Image /RestoreHealth
    and get it to complete 100% successful???

    Sounds to me that this flight signing package has to do with insider builds, as the ISO I have converted from the Media Creation Tool created ISO, to being serviceable, run the command offline just fine:
    Code:
    DISM /Cleanup-Image /RestoreHealth
    I will play around with this further to see if this can be fixed somehow...
    I have even tried moving them to desktop(DO NOT delete them), then retried restore health, go errors, then rechecked using Tweaking.com's Windows Repair Pre-Scan tool, but then got 4 errors instead of just this one, when it checked file signatures:
    Scanning Windows Packages Files.
    │ Started at (14-Apr-17 17:17:45)

    │ These Files Are Possibly Corrupt (Bad Digital Signature): (Total: 1)
    C:\WINDOWS\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

    1 Combined Problems were found with the packages files, these files need to be replaced (These mainly only effect installing Windows Updates.)
    │ The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually.

    │ THESE FILES DO NOT KEEP THE REPAIRS FROM WORKING; YOU MAY STILL RUN THE REPAIRS IN THE PROGRAM.

    │ Files Checked & Verified: 3,392

    │ Done Scanning Windows Packages Files.(14-Apr-17 17:18:08)
    └────────────────────────────────────────────────────────────────────────────────┘
    I then put them back
      My ComputersSystem Spec

  9. f14tomcat's Avatar
    Posts : 36,218
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       14 Apr 2017 #58

    Cliff S said: View Post

    Also the winsat formal is giving me a "no adapter for device" error for some reason since I upgraded to CU:


    Same.... got that all thru last Insider cycle. I just ignore it. Maybe somebody at MS forgot a minor piece of code?
      My ComputersSystem Spec


  10. Posts : 79
    W7 x64 & W10 Pro x64 (Dual boot)
       14 Apr 2017 #59

    slicendice said: View Post
    Only Critical Reliability History events I see is MicrosoftEdgeCP.exe crashes. Those I have a lot! :)

    I am sure I can fix this by modifying permission a bit...but haven't bothered yet.
    I had this problem once, with version 1511, and ran in Powershell the following:
    Get-AppXPackage -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register $($_.InstallLocation)\AppXManifest.xml -Verbose}
    Rebooted pc and reconfigured Edge.
    The problem never came back with 1607 and 1703 builds, so it may help you...
      My ComputerSystem Spec


 
Page 6 of 8 FirstFirst ... 45678 LastLast

Related Threads
Update April 11th 2017: This KB4016251 update was replaced by KB4015583. 849040898163752960 Source: Feedback Hub
849836090638778368 849040898163752960 Source: Feedback Hub KB4016252 direct download links:
847862697324564481 Source: Feedback Hub KB4016250 direct download links:
Source: https://support.microsoft.com/en-us/kb/3197356 Windows Update - Check for and Install in Windows 10 - Windows 10 Forums
UPDATE: Download Windows 10 1607 Script fix to unblock update for Windows Insiders from Official Microsoft Download Center Source: Cumulative Update Build 14393.22 for PC and Build 14393.221 for Mobile now available - Feedback Hub How...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 05:19.
Find Us