Thanks for the replies and ideas folks. It turned out that the FormEZWizard didn't actually even exist in the mode the SetupScreen was in at the time, so I added an IfObject Exists ahead of the IfObject Visible and it works fine now.
Hi,
My current understanding is like this:
> Unexpected window: 'EZSetup Wizard'
This message means that the object (window) that your test code tries to interact with is overlapped by another modal window which makes it impossible for TestComplete (like for the human user) to interact with the target window.
Considering the above, it looks like that your test code tries to click the Cancel button on the EZWizard form. But at the moment of click this form is overlapped by the EZSetupWizard one. This makes it impossible to click Cancel button and triggers the Unexpected Window error.
With the Delay operation enabled, EZSetupWizard window has enough time to close and this unblocks access to the EZWizard form.
More reliable way to implement this part of test is to wait until the Exists property of the EZSetupWizard window becomes false and then continue. This can be implemented using the .WaitProperty() method.
