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

Cannot vertify Flash add-on on Internet Explorer #25

Open
pftmclub opened this issue Dec 19, 2021 · 4 comments
Open

Cannot vertify Flash add-on on Internet Explorer #25

pftmclub opened this issue Dec 19, 2021 · 4 comments

Comments

@pftmclub
Copy link

Is there anyway to enable this add on? I tried everything and none of them are working

image

@n0samu
Copy link

n0samu commented Jun 2, 2022

In Internet Explorer, go to Tools => Internet Options => Advanced. Scroll down to the "Browsing" section and make sure that "Enable third-party browser extensions" is checked. Also click the Security tab and make sure that the Internet zone is not set to the "High" security level.

@pftmclub
Copy link
Author

In Internet Explorer, go to Tools => Internet Options => Advanced. Scroll down to the "Browsing" section and make sure that "Enable third-party browser extensions" is checked. Also click the Security tab and make sure that the Internet zone is not set to the "High" security level.

I did that, and somehow it's still doesn't work. Is it because Microsoft blocked this thing from system?
image
image
image

@n0samu
Copy link

n0samu commented Jun 30, 2022

Honestly I have no idea then, sorry!

@ShinjoKurumi
Copy link
Contributor

The reason that the plugin is marked as "not verified" is because the patched binary files does not have a vaild digital signature. That is expected since FlashPatch did patched these files and causing the digital signature corrupted or invalid.

This should not affect the functionality of the plugin. You can adjust the security settings of Internet Explorer to allow unsigned ActiveX controls, or create a self-signed certificate to sign these patched OCX binary files.

And if the version number of the plugin is too low, it may be blocked by Internet Explorer, so updating the plugin to the latest version may helps to solve the problem.

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

No branches or pull requests

3 participants