Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. I tried every version and it didn't work and I tried compatibility options, I don't know why it won't work. The text was updated successfully, but these errors were encountered:.
Sorry, something went wrong. I accidentally wrote cmd idk why. Okay then I need the exact URL of the executable you downloaded that resulted in your message.
Okay, in that case, the only logical explanation I see is you are using an x64 version of Windows where bit compatibility is disabled. You will need to install bit compatibility not sure how, since all I know is you have to get out of your way to disable bit on Windows x64 , as I have no plans to release bit versions of Zadig. Otherwise, you will have to compile Zadig yourself this Wiki page may help. I strongly suspect that you will run into this issue over and over as you try to run bit software on your system Wait, I think that it is enabled, otherwise, I wouldn't be able to launch some applications that I use like Steam Steam is bit afaik.
Logically then, there's not much I can do unless we identify what is so specific on your system, that prevents a standard bit executable from running. And I'm afraid you're the only person who can figure that out Even if this is not the reason, the above link may help to troubleshoot the issue. I'm having this exact same problem after the windows april update.
My computer is 64 bit, compatible with 32 bit applications for sure. Sideload apps is not the problem. I've had that enabled for ages and it's still enabled now. I just made an account to say I am also getting this problem. Latest version of Windows 10 Pro, sideload apps on. I've tried with developer mode as well, I've tried disabling Windows SmartScreen and my anti-virus, I've tried many different versions of the program along with different compatibility modes, I've tried creating a new administrator account and running it, nothing.
Same error every time, "This app can't run on your PC". Unfortunately, the message does not provide any kind of help as to why the application may not be compatible with your versions of Windows, and is it therefore up to Microsoft support to help with this issue, as without having Microsoft providing the exact reason why the message pops up, I literally cannot do anything about this. Oh, and for the record, I too am using the April Update of Windows 10 x64 and I am not seeing this issue, and neither seem the many other people who updated to the latest , so this is definitely not a global issue with the application.
There must be something specific to your environment, that Microsoft needs to help clarify, that prevents the application from running. I've tried resetting my services to default values and safe mode, still nothing. I suppose contacting Microsoft support is the next step, but I don't think they'll be any help.
They'll most likely just brush us off and say "oh it's a problem with the software not us bye". Are there any dependencies required for Zadig we might be missing? Here is my Windows Features list, am I missing anything? Disabling Avast Anti-Virus, and closing everything else still gives no results. I've ran full Avast and Malwarebytes system scans just in case, still nothing. Here is my current PC build, perhaps we may have some hardware in common that's causing the problem?
Never have I gotten a blue screen since I finalized my overclock. Don't know if this is of any value, but I attempted to run the program through PowerShell and CMD elevated and got these errors. I'm trying to think of what could possibly be causing this. My bios and drivers are up to date. I have HPET off?
Doubtful that has an impact but I really can't figure out what the problem could be. Hey, sorry for the double post, but I think this is important enough to keep separate instead of editing it into my previous post.
I have absolutely no idea why this is the case, but downloading the program through Microsoft Edge worked. Google Chrome, for some reason, seems to mess up the file during download. This is the strangest thing I've seen in a long time. This is very odd. I can't seem to replicate the issue with Chrome. If you still have the problematic file, can you please check its size? Het gebruik van software, downloads, scripts en uitleg op deze website is geheel op eigen risico, DomoticX is niet aansprakelijk voor de schade die, rechtstreeks of onrechtstreeks het gevolg is van gebruik van deze website!
It can be especially useful for cases where: you want to access a device using a libusb-based application you want to upgrade a generic USB driver you want to access a device using WinUSB System Requirements: Windows 7 or later. Make sure you pick the right one! This is needed for libusb applications using libusb-win Note that the use of KMDF v1. If that is the case, a Windows popup will appear prompting you to reboot.
Please pay attention to it! Improve error reporting. Fix Windows 7 showing a "Trusted Publisher" dialog. Embedded drivers: WinUSB v6. Fix issues with extended characters in current user directory. Fix a possible crash when deleting the private key. Other improvements.
0コメント