machine.config file going missing on Windows 7 and 10 pc's RRS feed

  • Question

  • I'm a .net developer for a large practice management application and we're receiving large numbers of customers experiencing an issue where they get the following error:

    System error- Eaglesoft.exe cause EXCEPTION_ACCESS_VIOLATION in module at 0x65a1acf2"

    Eaglesoft is our application and that is one of our dll's that is throwing the exception however the issue is we traced the problem back to a missing machine.config file. We have checked with the affected customers and their antivirus applications do not have this file in quarantine and no one has intentionally deleted the files. We created a simple batch script to copy and rename the default.machine.config into the appropriate folder, but this seems to only be a temporary fix as the issue keeps reoccurring.

    Is there any known causes for the machine.config going missing. We don't do anything with this file in our code. Our application btw is a C#,C++, and Powerbuilder mixed legacy application running .Net 4.6 with com interops between certain parts of the legacy and C# application pieces. We use WCF with Windows Services for the server side of our application (all on prem services no cloud).

    Any suggestions for what to look at would be greatly appreciated.

    Tuesday, May 14, 2019 5:57 PM

All replies

  • So this looks like the same issue

    Perhaps this application needs a certificate.

    Please remember to mark the replies as answers if they help and unmarked them if they provide no help, this will help others who are looking for solutions to the same or similar problem. Contact via my Twitter (Karen Payne) or Facebook (Karen Payne) via my MSDN profile but will not answer coding question on either.

    NuGet BaseConnectionLibrary for database connections.

    profile for Karen Payne on Stack Exchange

    Tuesday, May 14, 2019 6:47 PM
  • I work for Patterson Companies a developer of Eaglesoft so I'm aware of those issues, those have been resolved the first one was a twain driver issue, and the 2nd one you have quoted was an issue with that particular antivirus needing Eaglesoft added to a whitelist because of the com inter-op nature of parts of our application.
    My question to clarify is what could be causing the machine.config file to go missing from C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config folder.
    Tuesday, May 14, 2019 7:45 PM
  • Hi kevinschmuhl,

    Thank you for posting here.

    For your question, without more details, we could not make sure what cause the missing of machine.config file. 

    Based on my search, you could repair it according to the steps in the link below.

    I hope this would be helpful.

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Wednesday, May 15, 2019 2:11 AM
  • If possible, run ProcMon on affected machine(s) (preferably on DEV/UAT server instead of production server, ask your customer if they have non-production machine that have same behavior, or clone them to observe it because it can probably take quite a while to see it happen) and monitoring for machine.config. It should give you some idea about what deleted the file.
    Wednesday, May 15, 2019 2:50 AM
  • As I stated early I already have created a batch file that repairs the missing file but it keeps going missing.
    Wednesday, May 15, 2019 12:07 PM
  • Thanks I will give that a shot, hopefully this will help us track down what is deleting the file.
    Wednesday, May 15, 2019 12:08 PM
  • The route we ended up going to gather the info we need was to create a FileSystemWatcher application that logs every time this file is deleted and also turn on file auditing. We are currently in the process of deploying this to our customers to gather the data and I will post back here with what is causing the file to go missing.
     The reason we didn't go with procmon is the logs it generates logs that are too large for a long running issue like this where the file only goes missing after a week or so of being repaired. The logs it generated were 400Mb every 30 seconds.
    Friday, May 17, 2019 3:57 PM
  • I wonder if you can provide an update to this? I manage a small number of clients who rely heavily on EagleSoft, and I'm seeing this error fairly regularly. 

    Has there been any resolution? The problem seems to affect clients through the most current release of EagleSoft.

    Friday, February 28, 2020 12:48 PM
  • Our company manages a number of dental offices that use Patterson Eaglesoft. This issue consistently happens with version 20.1 and 21. Is there a fix yet? It's incredibly frustrating. Our solution is to create a login script that copies over the .default version at every reboot. The issue only happens with Eaglesoft that I can find.
    <input id="idg-io-safe-browsing-enabled" oninit="true" type="hidden" />
    • Edited by EthanMc Wednesday, July 29, 2020 5:35 AM
    Tuesday, July 28, 2020 9:01 PM