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

Windows 10 support #15

Closed
sinkingsugar opened this Issue Aug 1, 2015 · 30 comments

Comments

Projects
None yet
5 participants
@sinkingsugar
Copy link

sinkingsugar commented Aug 1, 2015

I just updated to windows 10 and sadly Interception was not working.
I tried installing again (admin prompt etc) but gave a "could not write to system32\drivers" error.
Nice piece of software! I hope you can get windows 10 support up soon!

Edit: It is actually WORKING!, just the uninstall/install process is acting weird. ( I had it installed under windows 8.1 )

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Aug 1, 2015

Thanks for reporting, I'll take a look when I find some time and a Windows 10 machine. I'm wondering whether they have finally fixed the weird name of the system directory (system32 in the 64 bits age).

@sinkingsugar

This comment has been minimized.

Copy link
Author

sinkingsugar commented Aug 1, 2015

Haha! well.. I had a look and looks just like before ! 64bit system.. yet system32 is filled with stuff :)

@sinkingsugar

This comment has been minimized.

Copy link
Author

sinkingsugar commented Aug 1, 2015

Just an update.. I manage to install it after a reboot! the issue might be quite small then! I'm not sure why it was complaining at that point.
I think that fresh installs might just work.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Aug 1, 2015

Oh, cool, good to know, I'll close it for now then, if someone finds an issue I reopen it.

@oblitum oblitum closed this Aug 1, 2015

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 22, 2016

I am sorry, but I have the same problem and can't solve it for days.
Here is installer output on Windows 10: http://pastexen.com/i/TRnH1RME6M.png
Cmd was run from administrator.
How can I solve that?

And, isn't it better to give some more options for installer? Most of users ofc is developers and this is good idea to give more control. Seems, that something goes wrong with paths, but I can't experiment because have only install and uninstall :)

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow Is this an outdated installer? I think copyright years for the installer available for download are newer than 2012.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow Just checked, you're indeed using an old installer.

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 22, 2016

@oblitum I thought about that in first order, so I've download latest (summer 2015) release from here and it outputs the same :(
Here is proof:
http://pastexen.com/i/VuJBdKdLRi.png
Check the files last modified property. Maybe that is something wrong with my Windows? It it insider preview and that system a little buggy...

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow No idea. Are you sure you're inside an administrator prompt? This is the kind of error that should happen when not running as administrator. I have no issues on Windows 10, but in case I'd run it as non admin, I would get that error for writing permissions.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow just run a raw cmd, not a visual studio prompt etc. And run as administrator.

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 22, 2016

@oblitum The same :(
Tried from admin cmd and from C:
http://pastexen.com/i/mgCcq1pOCq.png

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow try to run "/uninstall". I think your issue should be something with Windows locking the file, so it can't be overwritten. So, even if "/uninstall" gives an error, reboot, and just after reboot, open an admin command prompt (raw cmd), and try install again.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

If still just after reboot it doesn't work, I would try to boot in safe mode, and try install again from there. If it still doesn't work, then, I have no idea without debugging further, still, this error message only shows up when failing on file creation.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow if all of this doesn't work, I advice that you open an issue and detail your platform (Windows version, machine architecture, etc)

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow also stating when it started to be a problem. Last time I installed on Windows x64 there were no problems, but maybe, after some Windows update, things changed.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow Also, just noticed you mention "InsiderPreview", is this newer than Windows 10, or is it an older build? I guess it may be the issue.

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 22, 2016

@oblitum
Ya, just after reboot helps :)
Have no idea what kind of thing blocks the file, but thanks.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 22, 2016

@UndeadBlow at last :-)

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 23, 2016

@oblitum
Okeeey, after installer wrote that installation is successful and I rebooted, interception doesn't works (on win7 I used your lib many times without any problems) and when I'm tried to install or uninstall message above appears again. I've tested that on my friend's machine, on official Win 10 without Insider preview and got the same message.
Do you tested interception on Win 10 x64? Seems strange one problem on two different machines.

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 23, 2016

On another friend's machine installation successfull with first try. Don't know what is going on -_-

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 23, 2016

@UndeadBlow Indeed, it's a strange issue, I'd like to know what's going although I have no idea. It could be possibly, some antivirus software acting strangely, game protecting software that do kernel mode protection, or another software that also make use of keyboard/mouse filters and is not acting as a good citizen.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 23, 2016

I guess there should be no issue on vanilla Windows, and this problem is arising from some extra conflicting software.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 23, 2016

By the way, I don't recommend anyone to use the general AV software that's used in the wide by Windows users. Generally they just offer a false sense of protection and are a resource hog, besides frequently turning the machine less protected: https://code.google.com/p/google-security-research/issues/detail?id=693

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 23, 2016

@oblitum I use no AV because I'm mainly Linux user :) Also all Windows integrated security services disabled as much as possbile, so I am a little in deadlock. I'm agree with you that I'm trying to solve problem and disabled most of soft that runs with sysems but no results for now.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 23, 2016

@UndeadBlow If you're interested, I can produce a installer with more logs so that we can pin-point this more specifically. I can do this at the weekend only though.

@UndeadBlow

This comment has been minimized.

Copy link

UndeadBlow commented Feb 23, 2016

@oblitum Yes, I can do everything you will require.

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Feb 23, 2016

@UndeadBlow ok, see ya at the weekend then, I'll try to build a logfull installer to check this in your machine (since I can't repro).

@serzh82saratov

This comment has been minimized.

Copy link

serzh82saratov commented Jul 7, 2018

Have you found a solution?

@oblitum

This comment has been minimized.

Copy link
Owner

oblitum commented Jul 7, 2018

@oblitum oblitum reopened this Jul 7, 2018

@oblitum oblitum closed this Jul 7, 2018

@paradoxalan

This comment has been minimized.

Copy link

paradoxalan commented Sep 18, 2018

try to run "/uninstall". I think your issue should be something with Windows locking the file, so it can't be overwritten. So, even if "/uninstall" gives an error, reboot, and just after reboot, open an admin command prompt (raw cmd), and try install again.

Above instructions solved it for me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment