-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
do not work with windows 10 #279
Comments
Didn't install windows 10, maybe I will take a look at this after Window 10 release 😄 |
For me it's working fine under Windows 10 (last three builds on fast channel) |
Windows 10 Pro, build 10130, Wox works as expected. |
win10 family works OK, but always error when startup with win10 open |
@qianlifeng any update on this? Still doesn't work on Win10 after release. |
@skotzko what's the problem exactly? I can confirm that beta version works on the current release as it has been working on technical versions too. |
@dgutkowsky I just reinstalled the beta on Win10 (by downloading latest Github release and moving the unzipped beta folder to Program Files x86) and once I launch Wox, it has no built in plugins at all (e.g. there is no program search, can't launch settings, etc). Maybe I installed wrong? |
@skotzko maybe it is the case, can't tell why you have problems... just be sure, it is local, not the problem of Wox itself. |
@dgutkowsky hmm, okay. Is that the correct install approach? There are no instructions so wasn't 100% sure. Tried the choco install earlier which didn't work, guessing it's the old version. |
@skotzko I am running it portable, no installer. Be sutre that you firewall does not block the Wox and Everything (it makes connections on localhost) |
@dgutkowsky Hmm. This is so weird. It's unzipped, given administrator access, and explicitly allowed through the Windows Firewall. |
@skotzko sorry to hear that, I must say I can't imagine using Windows without Wox anymore ;) |
Yeah, this is frustrating. Clear install instructions would be much appreciated, as all the documentation has nothing on this. |
Okay, I figured it out. Here's how to fix it when installing the beta: Problem 1 Fix: Getting Wox Beta to see its assemblies
This will fix the issue of being able to run Wox--after inspecting the logs after the error, it was clear that Wox could find its plugins but could not load the plugin assemblies because they were blocked. Problem 2 fix: Getting Wox beta to start at system startupNow to the second issue: having Wox actually start up with Windows. First, I unzipped it to C:\Program Files, but no matter what I did (including settings tweaks), Wox woudln't start with Windows. The fix is to make the unzipped folder live in a folder that doesn't require elevated permissions to write to. So:
This issue, as far as I can tell, is because Wox is designed in such a way that it writes data back to the folder where it is contained, and so this requires admin permission to do anything (including start Wox at system startup). Hence, it wouldn't start at startup even though the settings were correct. I may have some pieces of this off, but wanted to post the fix I got to work here so others can find it. |
good for you! |
Hi guys, good news. |
No description provided.
The text was updated successfully, but these errors were encountered: