RiseT
Comments
-
@SharkBait Yes, I can confirm that Backupper's kernel mode drivers finally are code-signed correctly with a Microsoft certificate. No problems regarding this issue on …
-
I consider this a serious issue.
AOMEI states "The methodology is not simple password protection; the password is …
-
PS: I'd recommend updating the version number of the setup file. The setup file's properties still say version 4.0.0.0, which could confuse users as they cannot distinguish the 4.0.1 setup file from the 4.0 one.
-
@admin Great to hear that this is finally fixed. I can confirm after some testing that so far it's working as expected.
Just don't forget that the Microsoft certific…
-
...and the kernel mode drivers are still not code-signed by Microsoft. At least that's what my Windows is saying...
-
Imho, the real problem is that AOMEI took notice of this issue far too late.
Initially, Microsoft published their intent to enforce code-signing for kernel mode drivers in April of 2015 (yes, that's a 5):
in Windows 10 Anniversary: Backupper 3.5's drivers not signed with EV certificate Comment by RiseT December 2016
-
Nope. I've already tried that new setup file. They've updated the Symantec certificates, but no code signing by Microsoft. They obviously didn't understand the problem at first.
It's like I've described above - but I've forgotten to mention…
-
Backupper 3.5 is not compatible with Windows 10 Anniversary Update if you're installing on a system that is a clean install of said Windows version (doesn't apply to upgrading from an ealier version).
It won't …
-
Btw - I have to correct myself slightly regarding the steps to take to sign your drivers correctly. The end result is the same, but the steps are slightly different.
1. Firstly, you have to have a Extended Validation Code Signing certificat…
-
This information is pretty important as well in order to understand how to get your kernel-mode drivers correctly signed. I think I've posted it before, but just to be sure.
in AOMEI Backupper Pro fails after WIndows 10 Anniversary Update Comment by RiseT September 2016 -
May Microsoft's Code Signing FAQ is helpful for any further…
-
@admin: No problem. All I've been trying to do here is pointing you to the real issue and its only proper solution.
-
Cautionary note regarding the installation medium:
When trying to reproduce this configuration, don't use an installation medium with Windows 10 version 1511 or even lower and then upgrade.
You have to use an installa…
-
Installing Backupper with Secure Boot disabled:
I will try, but I'm pretty sure that it will work when disabling Secure Boot. As I've written before, th…
-
"That I was able to install the 'new' 3.5 version (indeed why not make it
3.5.1?) was due to the fact that I had Backupper already installed… -
@admin: Thanks for your reply.
1. I've uninstalled Backupper via Windows "Apps & Features". After uninstalling and rebooting, I've noticed that your uninstaller …
-
@renehoss: Just curious - are you using an UEFI system with Secure Boot enabled?
-
Let's rephrase that slightly in order to make it more clear:
Your have to get Extended Validation certificates issued by Microsoft for your two kernel drivers "ammntdrv.sys" and "amwrtdrv.s…
-
Ahem. Are you sure you've got your kernel drivers (i. e. ammntdrv.sys and amwrtdrv.sys) signed with an Extended Validation certificate from Microsoft?
I'm asking because my Windows 10 AU is still saying that Backupper's dri…
-
I think the underlying problem here is that Aomei intends to fix this in the next major version only. And before this one is released, aside from fixing this specific problem, they have to fully develop & test all new (and un…
-
The digital certificate "PAssist_Std.exe" is signed with is valid until 2016-06-26, in other words the certificate has expired. So what you experience is not really surprising.
Additionally, the certificate is using SHA1 as a h…
-
See this thread for more information on this issue.
-
Thanks for your comment. The obvious, official and only (apart from not using your own kernel drivers at all) remedy for fixing this issue is to submit Backupper's kernel drivers to Microsoft's in Windows 10 Anniversary: Backupper 3.5's drivers not signed with EV certificate Comment by RiseT August 2016
-
PS: Your website has been hacked & defaced (nice pic, though).