Skip to content
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

Download of Autorunsc64.exe Incorrectly Uses HTTPS #54

Open
null-default opened this issue Jan 26, 2021 · 3 comments · May be fixed by #55
Open

Download of Autorunsc64.exe Incorrectly Uses HTTPS #54

null-default opened this issue Jan 26, 2021 · 3 comments · May be fixed by #55

Comments

@null-default
Copy link

The following line of AutorunsToWinEventLog/Install.ps1 fails, due to live.sysinternals.com being hosted over HTTP and not HTTPS:

Invoke-WebRequest -Uri "https://live.sysinternals.com/autorunsc64.exe" -OutFile "$autorunsPath"

Fix should be as simple as changing the URI to http:// instead of https://.

@clong
Copy link
Contributor

clong commented Jan 26, 2021

live.sysinternals.com should be hosted on both HTTP and HTTPS, but they seem to be having a fair amount of HTTPS downtime lately. The correct fix here is to add a failover to HTTP.

@null-default
Copy link
Author

@clong is correct. #55 adds the HTTP failover, addressing this issue.

@spanningtrees42
Copy link

spanningtrees42 commented Oct 1, 2023

In admin command prompt I'm getting error: "mc : error: 0x2 trying to open file <CustomEventChannels.man>." I successfully opened and saved it in ecmangen and closed it so I don't think it's due to the file being open/in-use. I'm doing this on a Windows 10 v22H2 pc with internet access running SDK v10.0.26624(It's actually an earlier version, Microsoft posted an update saying this is expected behavior to display a higher number when it's actually lower.) The WEF server I built doesn't have that access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants