Delphi 2007 Win32
Currently, we are seeing an AV in UIAutomationCore.dll when a Win32.exe application closes. This is a software product that has been running on Windows XP, Windows 7 and now running it on Windows 10. Have only seen this issue on Windows 10.Note: The Win32 applications are built using Delphi IDE 2007Application Error: Exception EAccessViolation in module uiautomationcore.dll at 0006AOC9.Cases:1.
Win32 App 1: In the first case every time the Win32 closes the error happens2. Win32 App 2: In the other case we are aware of a Save Dialog is used and then the Win32.exe is closed and see the errorComments:1. Microsoft Windows Automation Framework: UIAutomationCore.dll - The underlying code (sometimes called the UI Automation core) that handles communication between providers and clients. This is only seen on a Windows 10 machine with a touchscreen or on Windows 10 without touchscreen monitors and the automation is enabled (not sure everything that might enable the automation) but Settings - Ease Of Access - Narrator will enable automation.3.
On Windows 10 machine without touchscreen monitors and no automation activated the error does not happen4. The Win32 applications do not use the Automation Framework and therefore do not make any direct calls to it.5. Process Explorer shows SysWOW64UIAutomationCore.dll loaded for both Win32 applications mentioned with touchscreen monitor or automation enabled.

It is not loaded for windows 10 machine without touchscreen and automation not enabled.6. It appears to be happening between FormClose and FormDestroy - we are getting the Delphi IDE setup on a Windows 10 machine to see if we can find more info about the issue with the debugger.Edited by: Brian Clingan on Feb 22, 2017 9:36 PM. Brian Clingan wrote:Currently, we are seeing an AV in UIAutomationCore.dll when a Win32.exe application closes. This is a software product that has been running on Windows XP, Windows 7 and now running it on Windows 10. Have only seen this issue on Windows 10.Note: The Win32 applications are built using Delphi IDE 2007Application Error: Exception EAccessViolation in module uiautomationcore.dll at 0006AOC9.Cases:1.
Delphi 2007 Win32 Error

Win32 App 1: In the first case every time the Win32 closes the error happens2. Win32 App 2: In the other case we are aware of a Save Dialog is used and then the Win32.exe is closed and see the errorComments:1. Microsoft Windows Automation Framework: UIAutomationCore.dll - The underlying code (sometimes called the UI Automation core) that handles communication between providers and clients.
This is only seen on a Windows 10 machine with a touchscreen or on Windows 10 without touchscreen monitors and the automation is enabled (not sure everything that might enable the automation) but Settings - Ease Of Access - Narrator will enable automation.3. On Windows 10 machine without touchscreen monitors and no automation activated the error does not happen4. The Win32 applications do not use the Automation Framework and therefore do not make any direct calls to it.5. Process Explorer shows SysWOW64UIAutomationCore.dll loaded for both Win32 applications mentioned with touchscreen monitor or automation enabled. It is not loaded for windows 10 machine without touchscreen and automation not enabled.6. It appears to be happening between FormClose and FormDestroy - we are getting the Delphi IDE setup on a Windows 10 machine to see if we can find more info about the issue with the debugger.Edited by: Brian Clingan on Feb 22, 2017 9:36 PMI have the exact same problem with a project built with Delphi 2009. The product executes properly on XP, and win 7, but has the UIAutomation error on Win10 with Touch screen.Jony Bassan.
2007-03-14 08:50:13 PMHello,We have a Delphi application where sending HTML based e-mails is themain function. This basic HTML Editbox component was not available inD3, D4, Delphi 6 nor in D2005. I did not buy D2006 due to the fact that thiscomponent was still missing and that I had troubles with third partycomponents when moving from D4 to Delphi 6 and from Delphi 6 to D2005. (E.g.QuickReport is not available in D2005 anymore.)In Delphi 6 and D2005 I use now the DHTMLED.OCX ActiveX component. I had someproblems with importing this ActiveX component in Delphi 6 and in D2005. I getthe error message 'Unknown Interface'. With a workaround on internet, Iwas able to use HTML edit boxes.Is this problem solved in Delphi 2007?In Windows Vista there is no DHTMLED.OCX anymore.
My application give anerror in Vista when trying to open an e-mail window. The error is:'Class is not registered'Has Delphi 2007 finally an HTML component in its package?Thanks,Hubert Anemaat.