Installing WinUSB (v6.1.7600.16385) - Driver Installation: FAILED (Operation not supported or not implemented) #288
Comments
I'm afraid I can't really support virtual installation of Windows. Especially, you get the error: Are you sure your system clock is correct? It is critical, when dealing with digitally signed binaries like drivers and driver packages that your system clock is set to the current time, as signature validation is time dependent. Also, despite what you state, your log is not the complete log, as it should start with something like |
|
restarted my VM and the clock is in sync with host OS. I still get the Here are the first 31 lines I missed. |
|
Thanks. Can you run Then right click one of the most recent Then if you compress it into a |
|
Thanks, I'm not seeing anything wrong in the certificate when it comes to its validity period, so either the issue is with a different certificate from your system (i.e. one of the certificates from the chain that is used to sign driver binaries) or you might have an issue with how you set your timezone. Can you do something like try to set the timezone of Windows in your VM to something like Japan, as, if it's a case of a check using the local timezone against UTC, having the certificate created in a timezone that's well ahead of UTC might help... |
|
It did not help. I decided to go ahead and do a clean install of windows on my VM and now I am getting a log that's very different error |
|
Can you try the following from an elevated command prompt: Then reboot and try again |
|
Success! Thank you! Initially I had to disable secure boot policy as it was preventing me from running this command :) |
|
Hmm, this is strange. Supposedly test signing is not required. @am6377, what if you just disable secure boot but revert the change to the |
Only disable secure boot, it didn't work. See Zadig1.log Paralles Desktop 18.1.0, Apple M1, Windows 11 ARM64 |
This issue is a known issue now. Zadig does not work on Windows 11 on ARM64, no matter it is a virutal machine or real machine. |
|
Maybe you want to re-open this issue and change the title to something like Windows 11 on ARM64 Support. |
|
I think I may have found a workaround. You need to disable Driver Signature Enforcement in Windows. To do that, you need to reboot your Windows into a Safe Mode (Start Menu, right click on power button, and hold SHIFT while clicking on Restart). While in the safe mode, go into Troubleshoot / Advanced Options / Startup Settings. Click Restart, select option 7 (Disable Driver Signature Enforcement). Once the Windows reboots, install Zadig drivers as usual. I'm running Win 11 Pro in Parallels on Mac and it works well. My setup:
|
|
Please don't spam. Your proposed "workaround" is well know, and is not a real workaround, since it forces the user to disable something that Zadig was designed to prevent them from having to do (since it does put a user's computer at risk). |
Wasn't meant to be a spam, just sorted something that was bugging me for some time and was happy to share. Will dutifully delete of course 🤷🏻♂️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am trying to install/reinstall WinUSB (v6.1.7600.16385) for a GameCube Adapter (not sure if this is the correct place to post this, but I'll try to provide enough details that can help the devs close this immediately if the query is too tangential to what should be posted here so please bear with me)
OS: Running Windows 11 Arm64 on VM Ware on Mac 13.0
Issue:
I get a "Driver Installation: FAILED (Operation not supported or not implemented)"
here's the complete Log
The text was updated successfully, but these errors were encountered: