Thanks Rick, no change.

Read through all the post all I can add is, was your reinstall through the Flight1 wrapper as a 'reinstall'

Using a fresh download.

 

bob

Here's a crazy long shot.

 

Is it possible when Ezdok was working perfect and then your AntiVirus Software picked up on an Ezdok False Positive and Quarantined it,  Result been = stopping Ezdok.

 

If this was to happen is it also possible that your virus software now see's this "certain file" that has been Quarantined and stops it any time your Trying to Install Ezdok? 

 

Check your Quarantined area of your virus software.

 

================

 

Here is a quote from Manifar on the SimForums on this issue 

 

""Very strange""

 

Strange bug .  Something doesn't allow to register a component in system. 

 

Solution:

 

Standard actions - 

1.UAC it shall be switched off. Antivirus too.

2. To launch config.exe on behalf of the administrator.

3.  Launch configure tool, open options--> unregistry components. Then options--> registry components. What window appears after that actions and what is written?

 

=================

 

After that,  like you I'm at a loss.  Would be interesting to get to the bottom of it  

Thanks guys,  I appreciate.

Bob, yes I used the Reinstall function with new licence key I just got from F1.

 

Thanks Elaine, I 've seen this message on SimForums and tried it with no success.

My AV is Windows Defender and is turned off.

OMG!!

copy of my exe.xml file just to check the syntax is correct.

 

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

<Descr>Launch</Descr>

<Filename>exe.xml</Filename>

<Disabled>False</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>as_btstrp_config_manager</Name>

<Disabled>False</Disabled>

<Path>as_srv\as_btstrp_config_manager.exe</Path>

</Launch.Addon>

<Launch.Addon>

<Name>EZdok camera addon</Name>

<Disabled>False</Disabled>

<Path>C:\Program Files (x86)\EZCA\EZCA.exe</Path>

</Launch.Addon>

</SimBase.Document>

 

 

bob edit the offsets are not shown

No, it's not related to exe.xml because the sim launches EZCA, no problem there.

The issue is with the registry and I'm getting kooky.

David, see if you have the following registry entries,

 

HKEY_CLASSES_ROOT\EZsimconn.SimConnect.1

Name=Default  Type=Reg_SZ  Data=EZCAv2_connector

 

HKEY_CLASSES_ROOT\TypeLib\{6A13ADEE-8634-4989-A8CC-ACE1A873FE42}\0.0\0\win32

Name= Default   Type=Reg_SZ   Data=C:\Program Files (x86)\EZCA\Ezsc.dll

 

HKEY_CLASSES_ROOT\TypeLib\{E1211242-8E94-11D1-8808-00C04FC2C603}\1.0\0\win32

Name= Default   Type=Reg_SZ   Data=C:\Program Files (x86)\EZCA\dx8vb.dll

Yes Glynn, all 3 of them.

Hi guys,

 

Well, here is my answer to Kevin @Flight1 support.

Thanks to all those who tried to help me here.

:wink:

 

OK, so the only way to get EZCA back is a complete OS reinstall.
Kind of nightmare just because of a crappy code somewhere in the software, I can't believe it.

I've been using EZCA since day 1 and can't imagine flying without it despite all the disconnections, various simconnect messages and small remaining bugs, because it's a fantastic tool. But it's not a reliable software.

Who could tell me this issue won't happen again?

Of course EZCA didn't "brake" anything in Windows and it's my own choice to reinstall Win10.

But a software you pay for that doesn't allow you to use it unless you reinstall your OS has a very serious problem.

 

I hope our friend Marniflarr will wake up a bit from his lethargy and react.

Releasing an update 2 years after letting people find solutions by themselves like he did with P3D incompatibility between versions is not serious.

The user manual is completely out of date and the customer service is not able to help reinstalling the product.

 

I very much appreciate your help Kevin and I understand you must be embarrassed not being able to provide a fix for this weird issue. I sincerely thank you for your efforts.

But I am angry against Marniflarr. I've helped this guy beta testing EZCA long time ago and I did it very seriously in spite of his "folkloric" and unpredictable style.

Today that I need him, he isn't there.

 

I am done.

Geez,  that's mad David isn't it.    I wonder how or why that happens and is it only a windows 10 thing.  I would love to know what file it damages or changes so maybe a user could reverse it without having to reinstall the OS.  

Hi David,

 

Crikey, you have been through the wringer and, under these circumstances, your reaction towards the author is completely understandable.

 

One thing that hasn't been mentioned is Backups. It may seem obvious now, and believe you me I've been down that road once or twice in the past, but what is often forgotten is the ability to 'fix' issues relatively quickly and with minimal hassle by simply biting the bullet and restore your setup using the latest backup image/s. If EZCA is installed on, say, D: and the OS on C: then it's likely you might need to restore both drive images. I would have tried C: first as it would ensure that any registry corruption was reversed to a working state. If that didn't work then restore D: as well.

 

Personally, I use 'Macrium Reflect' although I believe Windows has a decent basic backup utility. My previous backup solution was Acronis, but I became disenchanted during the inexcusable debacle surrounding the 'Operations in Progress' nonsense which prevented normal system shutdown. This has been going on for 2-3 years and there are still reports coming in that it hasn't been fixed. Rather late in the day, as far as I am concerned, but I understand Acronis have at last acknowledged the issue.

 

Macrium Reflect is fast, intuitive and, like Acronis, allows the backing up of individual folder trees. It offers the ability to mount images as drives which can then be browsed normally with Explorer making file retrieval possible. As with Acronis you can create incremental and differential backups. My preferred choice following the initial full backup is to perform incremental backups, with verification, which happens very quickly. It's the first thing I will do following any significant changes to Prepar3D or the System installation. Once I'm happy that everything is stable I will perform a backup. That way I always have peace of mind. If a troubleshooting exercise seems to be taking too long or it becomes tedious and frustrating the solution is at hand and very little will have been lost in the process and then only temporarily.

 

I'm quite sure, like the rest of us, you have been around the block a few times so my apologies if none if this is new, but there are likely to be others who could benefit from this experience.

 

Regards,

Mike

Hi David,

 

Crikey, you have been through the wringer and, under these circumstances, your reaction towards the author is completely understandable.

 

One thing that hasn't been mentioned is Backups. It may seem obvious now, and believe you me I've been down that road once or twice in the past, but what is often forgotten is the ability to 'fix' issues relatively quickly and with minimal hassle by simply biting the bullet and restore your setup using the latest backup image/s. If EZCA is installed on, say, D: and the OS on C: then it's likely you might need to restore both drive images. I would have tried C: first as it would ensure that any registry corruption was reversed to a working state. If that didn't work then restore D: as well.

 

Personally, I use 'Macrium Reflect' although I believe Windows has a decent basic backup utility. My previous backup solution was Acronis, but I became disenchanted during the inexcusable debacle surrounding the 'Operations in Progress' nonsense which prevented normal system shutdown. This has been going on for 2-3 years and there are still reports coming in that it hasn't been fixed. Rather late in the day, as far as I am concerned, but I understand Acronis have at last acknowledged the issue.

 

Macrium Reflect is fast, intuitive and, like Acronis, allows the backing up of individual folder trees. It offers the ability to mount images as drives which can then be browsed normally with Explorer making file retrieval possible. As with Acronis you can create incremental and differential backups. My preferred choice following the initial full backup is to perform incremental backups, with verification, which happens very quickly. It's the first thing I will do following any significant changes to Prepar3D or the System installation. Once I'm happy that everything is stable I will perform a backup. That way I always have peace of mind. If a troubleshooting exercise seems to be taking too long or it becomes tedious and frustrating the solution is at hand and very little will have been lost in the process and then only temporarily.

 

I'm quite sure, like the rest of us, you have been around the block a few times so my apologies if none if this is new, but there are likely to be others who could benefit from this experience.

 

Regards,

Mike

 

Macrium Reflect has saved me much grief, many times. I highly recommend it.