Windows 10: Runtime error '339': Component "FM20.DLL" or one of its dependencies is not correctly...

Runtime error '339': Component "FM20.DLL" or one of its dependencies is not correctly registered: a file is missing or invalid.

:)

 

Component fm20.dll or one of its dependencies not correctly registered: a file is missing or invalid

Hi Masters,

I am using 64 Bit Win 10 HP lap.

When I try to run a software it stopped with a message

"Component fm20.dll or one of its dependencies not correctly registered: a file is missing or invalid "

When I checked in "C:\Windows\SysWOW64" I couldnt find fm20.dll file.

Can you help me out.

I was trying to run an Air Conditioning software from Daikin called ASTRA.

Expecting your support

Thanks

Sree

 

FM20.dll

Done that repeatedly but to no avail.

Did not have this problem on Win7 with exactly the same app and hence it must be Win10 related - and logically it cannot be machine-specific.

Threads on the community forum suggest that regserv is somehow to blame for FM20.dll not writing to the registry - running regserv from the cmd line is however above my proficiency unless I have explicit step-by-step instructions.

Tks nevertheless for your willingness to assist.

 

run-time error 339: Component 'scrnet.ocx' or one of its dependencies not correctly registered: a file is missing or invalid

I have an old software that i want to run(it is portable no need of installation). There was a lot of dll and ocx files missing so it threw some errors (rt error 449, MSWINSC.OCX missing, mscomctl.ocx missing). I have registered a lot of them and the program
opened and almost running (some features running but other not) but it throws a strange error.

"run time error 339: Component 'scrnet.ocx' or one of its dependencies not correctly registered: a file is missing or invalid".

I have searched for this scrnet.ocx but i think it doesn't exist. I also tried some other ocx or dll files that may cause rt error 339 but nothing worked.(I have tried both windows 10 and windows xp in vm with the exact same results). Does anyone know something
about this error? maybe some more ocx files that could solve this problem?