Main Forum > Tweaking.com Support & Help

new release of Windows 10 reporting bad digital signiture

<< < (3/4) > >>

whiggs:
Uncanny!!!  I would make that mistake as well.  Not to argue the finer details, but I fail to see, even if I were the one who posted that post, how that would be considered inconsiderate.  The likeliness of getting an issue resolved increases when the number of eyes that see it increases, until that one person who knows the answer finally replies.  So if anything, I would think that limiting the issue to just one web sites forum would do yourself a disservice, as it severely limits the number of people who can see and reply to your problem.... 

Boggin:
I agree that posting on another forum to ask for help when there's no response on one, but otherwise cross posting is frowned upon and is a breach of forum rules on one Forum that I post on.

This is because one helper doesn't know what has already been suggested and suggestions can be duplicated.

What you have to bear in mind is that we are all volunteers that give our time freely and that time can be wasted when perhaps research is needed and both helpers come up with the same answer.

If you do post on another forum then it's best to let both helpers know so one may step back to see how the other progresses.

whiggs:
I will be sure to keep that in mind.

whiggs:
Hey everybody.  So I wanted to report that, since Microsoft has decided to ignore the issues prevalent in the creators update of Windows 10, I did more digging into the issue.  I then found a blog post which confirmed that the corrupt Windows package file is indeed the cause of DISM not working correctly, and it does come that way right out of the box.  However, the blog post also offers a solution: Just delete the references to the corrupt package file from the Windows registry.  There are a total of 4 registry keys: 2 are located in both
 "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex" and
 "[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages".  You will want to delete the two registry keys which contain the name of the corrupt package file: "Microsoft-Windows-TestRoot-and-FlightSigning-Package".  You will have to edit the key permissions in order to do this, as you do not have the permissions by default.  Once you delete those keys, then navigate to "C:\Windows\servicing\packages" and either move or delete the 4 files which also contain (and begin with) "Microsoft-Windows-TestRoot-and-FlightSigning-Package".  Then, run the scan again and it will continue to completion (at least as long as nothing else is wrong).  blog post can be found here:
http://borncity.com/win/2017/04/26/windows-10-v1703-fix-for-dism-error-0x800f081f/#comment-1215

Boggin:
A dism /restorehealth worked okay on this machine yesterday, although I have had the cannot find source file error before now.

As it doesn't seem to be causing any problems for me, I'll just leave it but thanks for the info.

Navigation

[0] Message Index

[#] Next page

[*] Previous page