Debugging problem in TestComplete on Windows 11

Update your TestComplete to the latest version.

Good morning!!

Even with the response from colleague sunnychopra, I followed rraghvani's suggestion and updated to version 15.81, and the result was the same as reported by sunnychopra.

When I'm debugging and want to access the variable "var t = Project.Variables.varTableDadosPedidoComercial", the application freezes and closes automatically, something that doesn't happen in Windows version 10.

I did what was suggested, created a new project, changed the variable names to "var tst = Project.Variables.varTableDadosPedidoComercialTest" and the same problem occurred, it crashed and closed.

I'm using JavaScript.

I also did another test using the same project on Windows 10 and neither version 15.59 nor 15.81 of TestComplete had the problem.

Just one additional note, sorry I forgot to mention it.

This freezing and closing of TestComplete only occurs when I try to access the variable's content using the Alt+W, and also in some situations where it freezes/closes unexpectedly.

Your variable name varTableDadosPedidoComercialTest suggests it might be a Table variable. These are more complex and can behave differently during debugging.

Do you see the same issue when:

• Using a simple variable (e.g., string or integer)?
• Running the test normally (Run) vs only during Debug?

This should help narrow down whether the issue is specific to:

• Table variables
• The debugger
• Or a broader **TestComplete + Windows 11 interaction

Since you’ve already confirmed it works on Windows 10 and also reproduced it in a clean project, I would recommend creating a support case with SmartBear. This looks like it could be a product-level issue rather than something project-specific.

If this resolves your scenario, marking it as the solution helps future readers find it quickly.

I did a test like that and didn't have any problems either. Now try inserting data into the variable; in my test, this variable is a table that receives 20 columns, and data is inserted from the return of a procedure. In this scenario, when I try to access it, the application freezes/closes.

Hassan_Ballan

That's right, as I said above, it's a table that receives data from a procedure that populates it to use that data in filling the fields in my application.

I also did this test without debugging and no errors occurred, I also did it with TestExecute and no errors occurred in the test either.

With a simple variable, this error does not occur when accessed via Alt+W.

I consulted with our Microsoft team and it was confirmed that the tool is not designed to run on Windows 11. This version has more secure memory access via the DM.dll file, causing TestComplete to close unexpectedly whenever I pause a debugging session or reach a breakpoint while testing Delphi and C# (.NET) applications. I am using JavaScript.

We performed several tests to try and work around the problem, but all were unsuccessful.

I disabled "Memory Integrity" (Core Isolation) in Windows 11.

I added TestComplete.exe to the "Exploit Protection" exclusions (specifically disabling Hardware-Enhanced Stack Protection).

I re-registered DM.dll.

Attached is a screenshot of the error that occurs in the Windows event log.

Since our company hasn't yet renewed the contract that allows us to open a support ticket with SmartBear, I can't proceed with the request. If anyone could do me this favor, I would appreciate it.

All that's left for us to do here is revert to Windows 10 so as not to interrupt our work.

Thank you all for your collaboration and help.

Thank you.

As a workaround, avoid inspecting the table variable using Alt+W or the Watch/Evaluate window during debugging. Instead, log specific values (e.g., Log.Message(t('col', 0))) or copy small subsets of the data into simple variables or arrays for inspection, since normal execution and TestExecute runs are not impacted.

From what’s been shared, this looks less like a data or scripting issue and more like a debugger-related problem on Windows 11. The crash only occurs when evaluating a populated table variable during a paused debug session, while the same code runs fine outside debug and on Windows 10. That strongly points to how TestComplete’s debugger is trying to evaluate or serialize the table object rather than how the data is being created or stored.

To help others reproduce and narrow this down, it would be useful to isolate the exact trigger by simplifying the scenario step by step: try a table with just one column and one row, then gradually increase columns and rows to see when it starts failing; check whether accessing a single cell versus evaluating the whole table makes a difference; and confirm whether the crash only happens when using Alt+W versus hovering or logging values. This should help determine whether the issue is tied to table size, structure, or the debugger’s evaluation behavior.