Windows 10: Error 13 is Caused by SHA-2 on Win7,how to solve it?

Installed the SHA-2 for Win7 x86 yesterday,now the system doesn't boot and the system say error 13

:)

 

SHA-2 Code Signing questions

First and foremost, this is my very first experience with Code Signing.

I bought Standard Code Signing from Certum for 3 years.

It is SHA-2 based:

They are all normal Windows Executables; for end users, both portable and installers.

Questions:

1. Bearing in mind the certificate has been issued 10. 10. 2016, i.e. after 1. 1. 2016, does this somehow influence how the signature will behave? I ask this on behalf of reading about deprecation of SHA-1, e.g.:
   
   
2. Should I also timestamp? What is this good for? Are there any disadvantages of timestamping? I found this, which does not really clear things up:
   
   
3. Supposing I would drop support for XP and Vista, will SHA-2 code signature work properly on Windows 7? I read on DigiCert that SHA-2 Code Signing support on Windows 7 is Partial:
   
   
4. There is a havoc around cross-signing SHA-2 (SHA-256 in particular) and SHA-1. Supposing as I said I will no longer support WinXP and Vista, do I need this?
   

 

SHA 2 Encryption

What do you mean exactly with the marked part?
Sha 2 is isn't that new.

 

Windows 10 update: start up and sleep issues caused

Dear Vijay,

Thank you for your response: apologies for slow feedback.

Regarding step 1 - doing a restore point : I tried this twice and twice it failed. Now, the date of the update that caused the issue (13/14 September 2019) has disappeared from the history list. Is there a way of finding it, still?

Regarding Step 2- the list of updates installed: the two suggestions above do not seem to appear in the list in the window "Installed Updates".

There are two updates listed for 13 September - Security Update for Adobe Flash Player and Security Update for Microsoft Windows.

Could you advise what I might try next?

Thank you so much.