unable to verify digital signature of drivers

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Kale_Maxon
    PCHF Member
    • Oct 2023
    • 6

    #1

    unable to verify digital signature of drivers

    Guys, I messed up!

    I have just purchased the oscilloscope Hantek60022BE.
    I installed the wrong driver (Hantek60022BL) and, after realizing the error, I uninstalled it and reinstalled the correct ones (i.e., Hantek60022BE).
    But, after reinstalling the driver, in “device manager” the oscilloscope is displayed as “unknown device”.
    Also in “device manager” if I try to update the oscilloscope driver (which I repeat is displayed as “unknown device”) a message comes up saying “unable to verify digital signature of drivers required for the device it is possible that during a recent hardware or software change a corrupted file with an incorrect signature or consisting of malware of unknown origin was installed”.

    What can I do? Do I need to change the registers of the system?
    I have already written to product support but waiting if someone can solve the problem I would be really grateful.
  • PeterOz
    PCHF Technical Response Team
    • Mar 2021
    • 4181

    #2
    Good chance that the driver is not installed as unable to verify digital signature of drivers.
    Normally stops the driver from installing and you have to install the driver in unverified mode.
    Basic is to restart from advanced mode and disable driver signature for this driver (option 7)
    Doing it this way will only turn it off for this instance.
    https://www.groovypost.com/howto/disable-driver-signature-enforcement-in-windows-11/#:~:text=In%20the%20bottom%20left-hand,select%20Disable%20Driver%20Signature%20Enfor cement.
    DO NOT do it via a registry hack.

    Comment

    • Kale_Maxon
      PCHF Member
      • Oct 2023
      • 6

      #3
      Originally posted by PeterOz
      Good chance that the driver is not installed as unable to verify digital signature of drivers.
      Normally stops the driver from installing and you have to install the driver in unverified mode.
      Basic is to restart from advanced mode and disable driver signature for this driver (option 7)
      Doing it this way will only turn it off for this instance.
      https://www.groovypost.com/howto/disable-driver-signature-enforcement-in-windows-11/#:~:text=In%20the%20bottom%20left-hand,select%20Disable%20Driver%20Signature%20Enfor cement.
      DO NOT do it via a registry hack.
      I have already followed this video and it worked as soon as I restarted the computer … however, the second time I restarted it the same problem arose. It doesn’t work like this

      Comment

      • Bruce
        PCHF Member
        • Oct 2017
        • 10697

        #4
        @Kale Maxon - any update?

        Comment

        • PeterOz
          PCHF Technical Response Team
          • Mar 2021
          • 4181

          #5
          Originally posted by Kale Maxon
          however, the second time I restarted it the same problem arose
          Are you saying it uninstalled the driver?

          Comment

          • Kale_Maxon
            PCHF Member
            • Oct 2023
            • 6

            #6
            Originally posted by PeterOz
            Are you saying it uninstalled the driver?
            Originally posted by Bruce
            @Kale Maxon - any update?
            I SOLVED.
            Basically the driver is trash. .. and this is not coming from me, this is coming from the technician near my house who has been fixing PCs for 30 years. I gave him $40 to “fix it” and install a driver that would solve this problem. I have no words. Hantek’s driver (of my oscilloscope in question) was created for Windows XP and in w11 it gives problems. I don’t know the more technical explanation. I tried from scratch to install the official drivers on another computer and the problem is the same! I then updated them with the drivers that the technician made available to me and now everything works.

            Comment

            • PeterOz
              PCHF Technical Response Team
              • Mar 2021
              • 4181

              #7
              Thanks for posting the fix

              Comment

              • Bruce
                PCHF Member
                • Oct 2017
                • 10697

                #8
                glad it got sorted.
                will close as solved.

                Comment

                Working...