Skip to content
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

Open
Marc-Pierre-Barbier opened this issue Aug 15, 2023 · 7 comments
Open

Install fail in 22H2, new workaround found #206

Marc-Pierre-Barbier opened this issue Aug 15, 2023 · 7 comments

Comments

@Marc-Pierre-Barbier
Copy link

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/

@ZanderFoster
Copy link

ZanderFoster commented Aug 23, 2023

+1 also having this issue. However the above workaround didn't work...

@SwooshyCueb
Copy link
Contributor

Disabling driver signature enforcement isn't really a solution as a lot of software will refuse to run under such conditions.

@Marc-Pierre-Barbier
Copy link
Author

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.

@carbolymer
Copy link

carbolymer commented Aug 24, 2023

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:

bcdedit /set nointegritychecks off

Disabling driver signature enforcement isn't really a solution as a lot of software will refuse to run under such conditions.

That's only for the installation period. After that signature enforcement can be enabled.

@channeladam
Copy link

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 !

@sramsay100
Copy link

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.

@infelicitatis
Copy link

Is there a way to install with secure boot?
my bitlocker will prevent booting without secure boot enabled

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants