Hi ,

In my application (using Powerbuilder 12.5 which IS compatible with Windows 10) I'm using an OCX control which uses MSHTML.dll.

When I'm running my application I'm getting an ieframe  exception . This exception occurs when I try to open from inside my application the screen that uses the specific OCX.

My question is .

Is it possible to make Windows 10 ACCEPT my OCX control ? Add it somewhere or register it somehow in order for Windows 10 bypass the security validations which causes the issue ?????

Because I believe that Windows 10 finds that this is a malicious software (which is not) and blocks whatever it tries to do with the ieframe.dll.

I know this is a security issue so How can overcome this ?

Appreciate your help on this.

thank you

Hi zakkar,

"register it"
I hope the following link will be useful.
How to register an ActiveX control manually (.ocx)
https://support.microsoft.com/en-us/kb/2746232

Considering this is more likely a developing issue, it is recommended to ask from out MSDN forum.
MSDN Forum
https://social.msdn.microsoft.com/Forums/en-US/home

Best regards

hi Meipo ,

I'm not asking how to register an OCX. This is not my issue.

I'm getting a lot of security warnings from windows 10 because the OS assumes that this is an exploit program or virus or I don't know what else.

And I'm asking .

Is there any way to "Allow" to this OCX I'm using in my application to run without all these securities ?

Is there anywhere in the Windows 10 list something that we can declare the programs that we want to run without issues ?

thank you

I believe that you should digitally sign the OCX file.  I'm not familiar with PowerBuilder, here is an article on VB6 that talks about it

https://msdn.microsoft.com/en-us/library/Aa231196%28v=VS.60%29.aspx?f=255&MSPPError=-2147217396

Hi graye ,

This what I get when debugging. It sees that the register does not have the same value and jumps off.

Konsole output

534e98b6 8bfc mov     edi,esp

534e98b8 ff761e          push    dword ptr [esi+1Eh]

534e98bb ff761a          push    dword ptr [esi+1Ah]

534e98be ff7616          push    dword ptr [esi+16h]

534e98c1 ff7612          push    dword ptr [esi+12h]

534e98c4 52              push    edx

534e98c5 ff760c          push    dword ptr [esi+0Ch]

534e98c8 ff7608          push    dword ptr [esi+8]

534e98cb ff7604          push    dword ptr [esi+4]

534e98ce 51              push    ecx

534e98cf 8bc8            mov     ecx,eax

#####534e98d1 ff15b0069953    call    dword ptr

[ieframe!__guard_check_icall_fptr (539906b0)]

534e98d7 ff542438        call    dword ptr [esp+38h]

534e98db 3bfc            cmp     edi,esp

534e98dd 7407            je

ieframe!IConnectionPoint_InvokeIndirect+0x596 (534e98e6)

534e98df b904000000      mov     ecx,4

*****534e98e4 cd29            int     29h

534e98e6 e9ebfeffff      jmp

ieframe!IConnectionPoint_InvokeIndirect+0x486 (534e97d6)

"*****" denote the point where the program terminates.

The call denoted by "#####" (Control flow guard) returns normally.

So, you've already gotten a certificate from a CA, and have used the SignCode feature to digitally sign the OCX file?

Yes but still the same.