Windows 10: Mouclass.sys is not digitally signed anymore and this has caused a Code 52 on Mice and...

I have tried three different mice on all of my usb ports and none of them worked but they are recognized by my computer in Device Manager.Under Mice and other pointing devices an HID compliant mouse will appear when plugged in, but has a yellow exclamation point on the icon. When properties are checked it the device statue displaysWindows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file thay is signed incorrectly or damaged, or that might be malicious software from an unknown source. Code 52I cannot

:)

 

Code 52 Error for Signed Driver.

Hello,

We are developing an application which communicates with out hardware via USB.

We are using libusb-win32 driver for this.

We have got this driver digitally signed.

However, when we try to install it on windows 10 Pro, we get Code 52 error i.e. Windows cannot verify the digital signature for the driver required for this device.

The same driver package executes seamlessly on Windows 7.

Kindly guide on this.

Thank you.

 

Windows 10 (Code 52) Error occurring with a confirmed signed driver "PaeStudio192_x64.sys"

I have an issue with this device
Studio 192 Mobile Audio Interface/Studio Command Center

Clean Install, OS up to date Windows 10 Pro (14393.187), unit connected via USB 3.0 cable, directly to the Surface Pro 3's one USB 3.0 port or connected via the

Microsoft Surface Dock (Surface Dock Firmware checked via "Surface_Dock_Updater_v1.0.8.0" and is up to date). I install its latest software/driver set

Universal Control 1.8.1 and driver installs without complaint.

Restart system, Power on the 192, Windows throws up error regarding this driver "PaeStudio192_x64.sys".

Stating: "A digitally signed driver is required TUSBAudio Class Driver V@@FileDescription | Windows blocked the installation of a digitally unsigned driver. Uninstall the program or device that uses the driver and check the publisher's website for a digitally
signed version of the driver."

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code
52)

This is the only device I've had a problem with, and I'm really uncertain as to why that is... I've already checked the driver through various means, such as "sigverif", which itself indicates the driver is signed! So what's wrong, could my Surface Pro 3
still be considered problematic when this is the only device I've had a problem with on it, or is the more likely issue something else?

I'm leaning toward something else, but I need a hand on this one... and I know of only one other dealing with the same thing according to the Feedback Hub: Presonus Studio 192 Signed drivers (PaeStudio192_x64.sys) are being assigned a (Code 52) in Build
14915

********************************
Microsoft Signature Verification
Log file generated on 9/24/2016 at 1:25 PM

OS Platform: Windows (x64), Version: 10.0, Build: 14393, CSDVersion:

Scan Results: Total Files: 297, Signed: 297, Unsigned: 0, Not Scanned: 0
File Modified Version Status Catalog Signed By

------------------ ------------ ----------- ------------ ----------- -------------------

paestudio192_x64.sys 6/3/2016 3.34.0.0 Signed paestudio192.cat PreSonus Audio Electronics Inc

The only workarounds I've discovered for this issue thus far have been disabling Signed Driver Enforcement or Disabling Secure Boot.

And It seems Windows can be 'tricked' into excepting the drivers, if drivers are installed prior to updating to Preview.

However, if the device is removed from the Device Manager, in the attempt to reinstall, Windows will return to exclaiming the driver is Unsigned. Even though these are ways around the problem, None of these things should have to happen in order to get this
working in Windows 10!

 

USB printer support doesn´t work in windows 10 because its not digitally signed

Hi Liem,

Thanks for posting your query on Microsoft Community.

The error code 52 mainly occur, when the system cannot verify the digital of the driver.

I suggest you to remove the digital signature of the device and check if the issue persists.

Follow the below steps.

• 
  Press and hold Shift key and click on
  Restart your Computer.
  
• 
  Select Troubleshoot.
  
• 
  Select Advance Option.
  
• 
  Select Startup Settings.
  
• 
  Select Disable Digital signature enforcement.
  

Hope this helps. Please get back to us if the issue still persists. We are here to assist you.