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

Please help us understand what the users encountered? #980

Closed
VictorVG opened this issue Jul 15, 2017 · 2 comments
Closed

Please help us understand what the users encountered? #980

VictorVG opened this issue Jul 15, 2017 · 2 comments

Comments

@VictorVG
Copy link

Started with the question:

bashaero

Hello. What's wrong with x86 startup?

1

I have no such phenomena, advised to disable UAC and EDS check, but after it turned out that two people have similar phenomena:

NOSS68

I do not have either UAC or parental control, it was the message of the program itself at start-up, I wanted to put the screen here, consult. It was in the morning, there was no one on the forum, so I downloaded 2.15.1117 from offsite. This version started and worked fine.

BetterLink

to Victor_VG

Your assemblies worked fine for me, but from the very beginning the same error started.
UAC / Parental Control is disabled.
If it was only a warning - OK.
But first: a warning

warning

, and when you try to run - the result

crash

. We have to use the official version.

Suspicion falls on problems with VisualC++2015 Redistributable. Perhaps, when installing a hefty modern application, this package was automatically replaced by 2017. Accordingly ... I can not now check the assumption.

I do not understand what can cause this behavior of the Win 7 OS, but I think that this is the reaction of some "beyond important security updates" from Microsoft.

@pbatard
Copy link
Owner

pbatard commented Jul 15, 2017

Sorry, but as I hope you can understand, I cannot support unofficial versions of Rufus, and especially, I will not provide any advice on how to remove the warning about using an unofficial version, which is there for a very good reason.

Also, if you do decide to provide your own binaries (Why? Where? For whom?), I STRONGLY advise that you digitally sign them (PLEASE get a code signing certificate if you haven't already done so, and sign your binaries!!). If you can demonstrate that you only publish Rufus binaries that are digitally signed with your own code signing certificate, then maybe I'll be willing to help you on this. But otherwise, you're 100% on your own, because telling Windows users that they can run unsigned versions of elevated apps is exceedingly bad security practice and the precise reason why I will always try to distance myself from anyone doing so.

@pbatard pbatard closed this as completed Jul 15, 2017
@lock
Copy link

lock bot commented Apr 6, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@lock lock bot locked and limited conversation to collaborators Apr 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants