New
#380
common error TomCat >
The reference to the file is there - BUT the file is missing from the source imageCode:(p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
common error TomCat >
The reference to the file is there - BUT the file is missing from the source imageCode:(p) CBS MUM Corrupt Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0
I have found that if you run DISM /RestoreHealth on an offline image of 15063 that it will complete without errors. I guess for some reason, when Windows is offline, it does not look for that FlightSigning package. Maybe this would have worked for all of the previous builds as well.
You can do this by booting with Windows 10 build 15063 install media. Use SHIFT-F10 to get a Command Prompt. Use the Install.wim from your boot media as your Repair source. In the example pasted below, I have another installed copy of 15063 Pro on a separate partition and ran offline Repair on it using a copy of 15063 Pro Install.wim. You would need to replace F: in my example with C: or D: for your Windows volume and point to the right path for the Install.wim.
Code:DISM /Image:F:\ /Cleanup-Image /RestoreHealth /Source:WIM:"15063 Pro x64.wim":1 Deployment Image Servicing and Management tool Version: 10.0.15063.0 Image Version: 10.0.15063.0 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.
Ok, now what happens after you run Dism /offline to repair the image..
Does the offline image pass when the image is now online??
No. I have tried that. It still looks for the FlightSigning package in Install.wim and does not find it. In a way there is nothing wrong with the online Windows image. It's the Install.wim that is missing the FlightSigning package. If they use this same Install.wim for RTM, it will never be there. I may not understand it right, but it seems like they will have to instead change the Online install so that it does not look for this package during DISM /RestoreHealth.
the reason being is because you are repairing an off-line widows installation - with an off-line windows image...
So the results of your off-line vs. on-line restorehealth testing - where to be expected...