-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install fail in 22H2, new workaround found #206
Comments
+1 also having this issue. However the above workaround didn't work... |
Disabling driver signature enforcement isn't really a solution as a lot of software will refuse to run under such conditions. |
Yea, but that was the only way i found sadly. |
That worked for me, I had to reboot twice until "Test mode" message appeared in the right desktop corner and I was able to install scream. I used:
That's only for the installation period. After that signature enforcement can be enabled. |
The bcdedit command line approach didn't work for me - it said that SecureBoot prevented that. As is also described in the article, disabling the enforcement through rebooting via Startup Settings however did work. Thank you @Marc-Pierre-Barbier ! |
For anyone forced to employ this workaround... If you are not seeing the sound device in the Sound Control Panel... please read on... This workaround worked for me. I too have 22H2. However, I would like to add that the sound device will not appear in the Sound Control Panel if the driver is partially installed on the Device Manager without a driver and then the driver is installed by thaw workaround. Please ensure that any failed attempt that installs the device in the Other Devices section of the Device Manager must be removed first. If you then follow the instructions provided by the OP of this issue then all will be fine. |
Is there a way to install with secure boot? |
as the title says in 22h2 of win10 i can't install the driver with any of the workarounds but i found another one.
i disabled driver signature enforcement
https://pureinfotech.com/disable-driver-signature-enforcement-windows-10/
The text was updated successfully, but these errors were encountered: