Cumulative Update KB4015583 Windows 10 v1703 Build 15063.138

miqbaln said:

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 isn’t 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. It’s 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

Cliff S said:

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 :)

Bree said:

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.

f14tomcat said:

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.

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! :)

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...

slicendice said:

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

Cliff S said:

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?