System Policy has been modified to reject unsigned drivers

[GoogleCodeExporter]

After clicking Install in LibUSB, it tells me "System Policy has been modified 
to reject unsigned drivers." 

Windows 8 x64

Enabled test mode to allow installation of unsigned drivers (allegedly) but 
still no luck.

Original issue reported on code.google.com by yami...@gmail.com on 5 Jul 2013 at 5:15

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Well, that's what I get for trying to do things on no sleep.

Forgot to run inf-wizard as admin.

Got everything installed, neat and tidy, but the chatpad still won't really 
work. I got it to type a lower-case r, by pressing the button repeatedly, but 
it won't recognize any more button presses. So I know that it is, at least, 
getting the signal, but it won't catch the keypresses (other than that one).

Original comment by yami...@gmail.com on 5 Jul 2013 at 5:34

[GoogleCodeExporter]

Good to know about the admin option, I'll make sure to put that in the 
installation instructions.

Regarding the chatpad issue, I'm going to copy your information to Issue #2, 
please monitor that issue for any updates.

Original comment by ksbarnes@skyag.net on 5 Jul 2013 at 5:36

• Changed state: Invalid

[GoogleCodeExporter]

in the instructions its still missing on step 8 for libusb

you should change it to exectue as admin

had the same problem

Original comment by loggjohn...@gmail.com on 11 May 2014 at 3:22

[Timlazisa]

I'm getting the same issue when installing lib. i get "system policy has been modified.... dada di da" despite disabellingsecure boot in my bios. I'm literally ready to chuck this out the window, anyone have any ideas

[Kytech]

@Timlazisa The issue is still occurring when running the libUSB installer as admin correct? Which OS are you running on and what version of LibUSB are you using? Do you happen to have a work/school account on your device that is allowed to manage the computer/configured to allow you to access some internal work/school resources? Those things can sometimes interfere with installation. This project should be compatible with Windows 10 with Secure Boot enabled and no test mode. (have been able to confirm this on one of my laptops). LibUSB should be signed if I recall right. I might have to try doing a fresh install of this to see if I can reproduce the issue if none of the other items are a factor. Might need to tweak the install process with some recent updates if things have changed.

Just tag me in a response with that info so that I get notified. I'll see what I can do to help troubleshoot. If you're on Windows 11, I do have a computer with Windows 11 setup, so I can try an install there as well.

[Timlazisa]

Hi mate and thanks for getting back to me. Its a personal computer running Win10 64bit. The libgen is Libgenusb-32-bin-1.2.6.0 I'm not willing to do fresh install so lets not even go there. I'm not that desperate to play DRL sim

regards

Tim

On Mon, 22 Nov 2021 at 22:18, Kyler Nelson @.***> wrote:

@Timlazisa https://github.com/Timlazisa The issue is still occurring when running the libUSB installer as admin correct? Which OS are you running on and what version of LibUSB are you using? Do you happen to have a work/school account on your device that is allowed to manage the computer/configured to allow you to access some internal work/school resources? Those things can sometimes interfere with installation. This project should be compatible with Windows 10 with Secure Boot enabled and no test mode. (have been able to confirm this on one of my laptops). LibUSB should be signed if I recall right. I might have to try doing a fresh install of this to see if I can reproduce the issue if none of the other items are a factor. Might need to tweak the install process with some recent updates if things have changed.

Just tag me in a response with that info so that I get notified. I'll see what I can do to help troubleshoot. If you're on Windows 11, I do have a computer with Windows 11 setup, so I can try an install there as well.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Kytech/xbox360wirelesschatpad/issues/1#issuecomment-975967433, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRW4XIF2PMH25MRUIEQ7QLUNK6VDANCNFSM5INWKBSA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[Kytech]

Just to make sure, by libgenusb, are you talking about the inf-wizard in libusb 1.2.6.0 or is that just the version of libusb and the download you used (libusb-win32-bin-1.2.6.0). If the download was named libgenusb-32-bin-1.2.6.0, that could potentially be the wrong download, but if the download was named libusb-win32-bin-1.2.6.0.zip, that should be the right one.

Is the driver policy error showing up on the step for the filter driver or the inf-wizard step?

[Timlazisa]

Its the zip file and yes policy error is when I try the inf-wizard

On Tue, 23 Nov 2021 at 16:24, Kyler Nelson @.***> wrote:

Just to make sure, by libgenusb, are you talking about the inf-wizard in libusb 1.2.6.0 or is that just the version of libusb and the download you used (libusb-win32-bin-1.2.6.0). If the download was named libgenusb-32-bin-1.2.6.0, that could potentially be the wrong download, but if the download was named libusb-win32-bin-1.2.6.0.zip, that should be the right one.

Is the driver policy error showing up on the step for the filter driver or the inf-wizard step?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Kytech/xbox360wirelesschatpad/issues/1#issuecomment-976799387, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRW4XJPIBASAY5XNNCYV2DUNO53XANCNFSM5INWKBSA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[Kytech]

Ok. Got it. Sorry for the late response @Timlazisa. I'll try working through a fresh install of this application on my system to see if I can recreate the issue. I have a machine that I haven't installed this project on before. It appears that some others have had similar issues with libusb, getting the same error, so I may try following the advice I found in this libusb issue, then I'll update the installation directions on this repo accordingly. If you're feeling adventurous enough to try the suggestions in that issue, you're welcome to, but no worries if you can't. I just won't really be able to get around to this for about a week or two. It may also be possible to run this application with only the filter driver step, based on some testing I did a while ago if I tweak things a bit, though that may be an enhancement I make a little later.

[Timlazisa]

Hi thanks for the update. No rush. It may be just easier to buy a controller that actually works with DRL out of the box!

Tim

On Sun, 5 Dec 2021 at 23:45, Kyler Nelson @.***> wrote:

Ok. Got it. Sorry for the late response @Timlazisa https://github.com/Timlazisa. I'll try working through a fresh install of this application on my system to see if I can recreate the issue. I have a machine that I haven't installed this project on before. It appears that some others have had similar issues with libusb, getting the same error, so I may try following the advice I found in this libusb issue https://sourceforge.net/p/libusb-win32/mailman/libusb-win32-devel/thread/CAGjSPUDC9krp-PvPnMbFJCML616ouB6VBKkxjcvEwVUbzAnBPg%40mail.gmail.com/, then I'll update the installation directions on this repo accordingly. If you're feeling adventurous enough to try the suggestions in that issue, you're welcome to, but no worries if you can't. I just won't really be able to get around to this for about a week or two. It may also be possible to run this application with only the filter driver step, based on some testing I did a while ago, if I tweak things a bit, though that may be an enhancement I make a little later.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Kytech/xbox360wirelesschatpad/issues/1#issuecomment-986325306, or unsubscribe https://github.com/notifications/unsubscribe-auth/APRW4XJUKZBI7SHT5YL7F6LUPP2RHANCNFSM5INWKBSA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[eggplantedd]

Was this ever solved? I am still currently having this issue.

[Kytech]

Was this ever solved? I am still currently having this issue.

I haven't been able to get to the bottom of this, but I have a couple of things to suggest.

I'd start by double-checking that the LibUSB version downloaded was 1.2.0.0 or newer (I may need to update the project README of it specified an older version). Those versions are signed so they shouldn't be encountering this error in most circumstances.

If you do have a new enough version, you could try using Zadig to attach the driver since that sometimes works better.

Let me know if neither of those things work. If not, it might be that there's a slight tweak that we need to do to a registry value due to some change in driver signatures in Windows 10 that affects devices that were not upgraded from a certain older version of windows 10 or earlier.

[eggplantedd]

Yeah, as this is a first time install, I picked the newest version, for my x64 machine, making sure to get the inf-wizard from 1.2.6.0.

I tried Zadig with the following settings. However, it timed out-

The weirdest thing about this - I have distinct memories of using my chatpad on my (Windows 7) PC somehow, I remember reassigning the buttons for Il-2 1946 distinctly, with the buttons lighting up. I don't have any wired connection means apart from the charger cable for a battery-powered 360 controller. Nor did I buy controller companion. So I have no idea how I recall doing it, because there isn't an Xjoy or LibUSB folder on my old HDD.

EDIT: Orrr it's maybe not so weird. Those 2017 files and folders - SkyAg - leads back to you!

But I still don't know how I managed this without LibUSB or Xjoy.

Let me know if neither of those things work. If not, it might be that there's a slight tweak that we need to do to a registry value due to some change in driver signatures in Windows 10 that affects devices that were not upgraded from a certain older version of windows 10 or earlier.

And yes, after Windows 7 bricked I installed Win10.

[Kytech]

Yeah, as this is a first time install, I picked the newest version, for my x64 machine, making sure to get the inf-wizard from 1.2.6.0.

I tried Zadig with the following settings. However, it timed out-

Let me know if neither of those things work. If not, it might be that there's a slight tweak that we need to do to a registry value due to some change in driver signatures in Windows 10 that affects devices that were not upgraded from a certain older version of windows 10 or earlier.

And yes, after Windows 7 bricked I installed Win10.

Can you check the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy registry key to see if a DWORD value called UpgradedSystem exists? If not, create it and set its value to 1, reboot the system, and try installing again. I'd suggest trying both Zadig and the installers included in libusb-win32 to see if either one of those work after that registry change.

Let me know if either of those things makes a difference. If that fixes it, I'll certainly need to update the install instructions for this. If not, I'll have to do some digging.

I've been wanting to get an installer put together at some point since the install process is quite a pain as of right now, but it's been such a long while since I've had much free time to work on this project. I'll probably put together an installer when I do eventually get around to some other changes I've been wanting to make. I'd really like to replace libusb-win32 with usbdk since it can allow the chatpad app to disconnect and reconnect on the fly in case some games don't play nice with this driver, then I'd like to replace vJoy with ViGemBus since it actually creates a virtual Xinput-capable device, which should solve a lot of compatibility problems that the current app has (and those components are much easier to automate the installation for). usbdk and ViGemBus are newer drivers that weren't aroudn when this project was originally started, and I also suspect they will play nicer in general on newer systems.

The weirdest thing about this - I have distinct memories of using my chatpad on my (Windows 7) PC somehow, I remember reassigning the buttons for Il-2 1946 distinctly, with the buttons lighting up. I don't have any wired connection means apart from the charger cable for a battery-powered 360 controller. Nor did I buy controller companion. So I have no idea how I recall doing it, because there isn't an Xjoy or LibUSB folder on my old HDD.

EDIT: Orrr it's maybe not so weird. Those 2017 files and folders - SkyAg - leads back to you!

But I still don't know how I managed this without LibUSB or Xjoy.

Yeah, this is the same codebase you would have been running back then, probably with only minimal changes since 2017, so I'd think you would have had LibUSB or vJoy at the time. If you had the LibUSB install files from your previous setup, I'd say to try that, but it seems that's not possible and Windows 7 required manual installation of the xbox 360 drivers in some cases, unlike Windows 10.

SkyAG is the original author, while I made a few contributions to the project back when it was hosted on Google Code and I have used it off and on since then, so I can see how that breadcrumb trail brought you here. Someone else migrated it to GitHub when Google Code shut down, then that person transferred the repo to me when I touched base and they noticed I was a contributor. I recently managed to reconnect with SkyAG (see #78), so they have access to this project now, but they've handed primary maintenance off to me.

If we're still stuck, I could try touching base with SkyAG to see if they have any info that may help with this, but I'm expecting I may need to try setting this up on a computer with a fresh Windows install to see if that yields anything insightful.

[eggplantedd]

Can you check the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy registry key to see if a DWORD value called UpgradedSystem exists? If not, create it and set its value to 1, reboot the system, and try installing again. I'd suggest trying both Zadig and the installers included in libusb-win32 to see if either one of those work after that registry change.

So it turns out it didn't exist-

So, with the drivers reset (removed from libUSB, returned it back to stock Microsoft ones, confirmed by controller connecting again), and the computer rebooted after this, I tried again and got the same error -

So I try installing it under test mode. Still nothing -

I then disable driver signature enforcement in boot. It successfully installs -

Yet now it won't even detect the Xbox 360 Wireless Receiver, in the chatpad app, whereas before it did even when I couldn't install the unsigned driver in inf-wizard:

So now I'm really at a loss!

And for record, mine is the official Microsoft Wireless Receiver.

[Kytech]

Can you check the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CI\Policy registry key to see if a DWORD value called UpgradedSystem exists? If not, create it and set its value to 1, reboot the system, and try installing again. I'd suggest trying both Zadig and the installers included in libusb-win32 to see if either one of those work after that registry change.

So it turns out it didn't exist-

So, with the drivers reset (removed from libUSB, returned it back to stock Microsoft ones, confirmed by controller connecting again), and the computer rebooted after this, I tried again and got the same error -

So I try installing it under test mode. Still nothing -

I then disable driver signature enforcement in boot. It successfully installs -

Yet now it won't even detect the Xbox 360 Wireless Receiver, in the chatpad app, whereas before it did even when I couldn't install the unsigned driver in inf-wizard:

So now I'm really at a loss!

And for record, mine is the official Microsoft Wireless Receiver.

@eggplantedd thanks for the very thorough investigation. As I did some digging around, it turns out the version of libusb-win32 that I've been using is version 1.2.6.0, while the latest is 1.2.7.3 I'd thought I'd been on the latest version this whole time, but it appears that is not the case. I'd try version 1.2.6.0 to see if it makes any difference since there were some changes in how the libusb-win32 project signed the driver in 1.2.7.3

I saw your Windows version is 10 pro, so you may want to check the following group policy option using gpedit: User Configuration > Administrative Templates > System > Driver Installation to see if it's set to something other than "not configured" for whatever reason.

If version 1.2.6.0 doesn't work, does installing the driver by right-clicking the generated .inf using the install option manage to install properly (in or out of test mode) with the device being recognized by the app with that method? If you haven't installed the filter driver yet and the device is not recognized, but the driver installed, I would suggest installing the filter driver as well. The bin/<arch> directory of the libusb-win32 zip should include a testlibusb-win.exe file that should indicate if libusb-win32 is seeing the device. I'd suggest checking that application to see if it shows up there while not being found by the chatpad program.

You may also want to try installing the filter driver first, or see if it will even work with just the filter driver alone and no inf-wizard (I recall getting this to work with just the filter once, skipping the inf-wizard, but I don't remember if I had to do anything else.) to see if that makes a difference.

If you can get 1.2.6.0 working, but only in test mode, I'd suggest disabling secure boot and booting in normal mode to see if everything works correctly. Secure Boot can sometimes require certain constraints on kernel drivers, so testing this could help us eliminate yet another variable.