Since there is a bit locker element on some machines in order to disable Driver Signature enforcement I’ve included how to handle it here:
As you may know, Microsoft recently implemented strict driver signature enforcement in Windows 11, which blocks drivers that don't carry a valid Microsoft-approved signature. Unfortunately, ZWO camera drivers fall into this category. You may have seen a warning message pop up when connecting your camera, or perhaps your camera has simply disappeared from NINA or other capture software. Windows 10 does not enforce this policy, so this only affects Windows 11 users.
I have a ticket open with ZWO and they confirm they are working on the problem, but have not specified what the fix will be or when it will be available.
In the meantime, there is a workaround: disabling driver signature verification in Windows 11. Before you proceed, please read the security note at the end — this is not a step to take lightly.
The workaround — step by step:
Before you start, you may need your BitLocker recovery key — a 48-character code. Not all machines will require this, but if yours does you'll need it written down, as you cannot copy and paste in this environment. To get your key in advance, visit aka.ms/myrecoverykey — it will ask for your Microsoft account credentials to retrieve it.
Open the Start menu, click the Power icon, then hold the Shift key and click Restart. Keep holding Shift until the screen turns blue.
Select Troubleshoot → Advanced Options → Startup Settings. If prompted for your BitLocker key, enter it now.
Click Restart. When the numbered menu appears, press 7 to select "Disable driver signature enforcement."
Your PC will boot normally and your ZWO camera should be visible again.
Important — this is temporary. Signature enforcement returns the moment you reboot. You will need to repeat this process every imaging session.
Security warning: Disabling driver signature enforcement means Windows will load any driver, signed or not, for the duration of that session. A valid concern here is that this workaround is being suggested at the prompting of a company asking you to reduce the security posture of your Windows machine. That may be entirely innocent — a straightforward driver signing oversight — but it is worth stating plainly. Only proceed if you understand and accept that risk. Do not do this on a machine that holds sensitive personal or financial data, or one that is regularly exposed to untrusted software or websites.
The right fix is ZWO properly signing their drivers through Microsoft's certification process. Until that happens, the decision to use this workaround is yours to make.
I already tried:
