-
Notifications
You must be signed in to change notification settings - Fork 283
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
Stopped working in Insider build 15002 #431
Comments
Any clink.log in |
|
Same here; however, it must be noted that 15002 introduced a lot of buggy behavior for me too (default audio device not being used for playback through waveout and a couple of "older" applications (like SysInternals' AutoRuns) not displaying correctly). So as much as I'd like this fixed, it may just be unfuxed at the next update. |
Still not working in 15007 :( I really, really miss it!
|
Same for build 15014:
|
Interesting fact I just discovered by accident: although clink is broken in C:\WINDOWS\system32\cmd.exe, it works in C:\Windows\SysWOW64\cmd.exe. I have no idea what the practical difference between the two is, if any. |
That makes sense, C:\Windows\SysWOW64\cmd.exe is the 32 bit version. It seems only the 64 bit version changed in an incompatible way. |
At 15031 it’s back to working again. |
partial working it seems at 15042. aliases (doskey) still not working. |
True, I had noticed that a doskey macro wasn’t working but hadn’t investigated it. |
Closing in favour of #438 which deals with the specific new problem. |
I’m in the Windows Insider Program, and in build 15002 which was just released to the Fast ring (Build 15002.rs_prerelease.170102-1700) Clink has stopped working.
clink inject
just doesn’t do anything. No apparent errors or anything.The text was updated successfully, but these errors were encountered: