Main Forum > Tweaking.com Support & Help

new release of Windows 10 reporting bad digital signiture

(1/4) > >>

whiggs:
Hello forum community.  So I updated to the newest build of Windows 10 a couple of days ago and I began getting an error when attempting to perform Dism /online /cleanup-image /restorehealth commands (even with the /source and /limitaccess arguments specified) that the source files could not be found.  In an attempt to fix, I ran Windows AIO app in safe mode, and found that, during the pre-scan, the following package file was found to have a bad digital signature:

C:\Windows\servicing\Packages\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.mum

So I mounted the "install.wim" of the boot media used, obtained the file in question fresh from the source, replaced it, and tried again.  It was still flagged as having a bad digital signature.  So, thinking that it may have been due to the in-place upgrade, I wiped my computer and installed from scratch.  After a few application installs (office, new adk, etc) I ran the above DISM command again only to find that I was again getting the source files could not be found error.  I then ran the pre-scan again to find that the exact same file mentioned above was still showing as having a bad digital signature.  Is this an error on the part of Windows AIO repair, or is this a Microsoft issue.  I am inclined to think it is a Microsoft issue, but wanted to get another opinion.

Boggin:
I don't know if Shane has tested WR on 15063 yet but I'll pass this onto him.

whiggs:
Sounds good me amigo.  Like I was saying above, I think is more of a Microsoft issue.  The application states clearly that the "mum" file in question only affects Windows updates, and the issue I am having is in regards to the DISM /online /cleanup-image /restorehealth command returning the source files could not be found, the source files which are usually obtained from Windows update.  I actually have a call scheduled with a level 2 Microsoft Tech on Monday concerning this as well, so hopefully there will be a quick fix.

Boggin:
I've seen that quite often reported when running the /restorehealth cmd and the problems when trying to point it to the source file with the subsequent limit access cmd.

If a sfc /scannow comes up clean then it's unlikely a /restorehealth would resolve anyway.

A sfc /scannow is usually run after the /restorehealth cmd to see if any corruption remains.

I'm not sure if running dism /online /cleanup-image /startcomponentcleanup before the /restorehealth cmd would help or have any effect on the Package error, but you could give it a try.

BTW - Good luck with MS tech support and hope you get someone who knows what they are doing and don't try to fleece you out $s.

whiggs:
Thank you for your feedback.  So SFC does not report any corruptions.  In fact, if you look at the log file I posted in the original post, it states that "The SFC (System File Checker) doesn't scan and replace some of these files, so you may need to replace them manually."  And since there is only one file, I assume that it is referring to that file.  My concern is that I have encountered this issue on two different machines in the span of less than 24 hours.  It occurred immediately after I performed an in place upgrade, so, since I assumed something must have gone wrong during the update, I ripped the iso to a usb and did a clean install.  Booted it into audit mode, did some basic installs, ran it again and boom, it was happening again.  That kind of error should not be occuring on a brand new machine build, much less an in place update where it was working fine before, you know?  While nothing may is necessarily wrong right now, I would think it would be very important to get that command to work, as it is a major repair tool that many people and applications (including Windows AIO repair) use to fix systems.

Navigation

[0] Message Index

[#] Next page