Forum Discussion

weiwongfaye's avatar
weiwongfaye
Occasional Contributor
14 years ago

Win7 64bit OS with latest windows update, testcomplete not work

Hi Support Team,





We are using TestComplete 7.52, it works fine until last week. This week after we install the latest windows update on win7 64 bit machine, our scripts fail.



The reason is that the objects used to be recognized as WPFObject before are now recognized as window("HwndWrapper[DefaultDomain;;...") in Testcomplete.



I am wondering if there is any hotfix for this?



Thanks in anvance!



(Jack.Wei.Wang@autodesk.com)



Regards

Jack


3 Replies

  • Hi,



    Try using the following fix:



    TestComplete Ent

    TestComplete Std

    TestExecute

    TestRecorder



    Here are the hot fix installation steps:

    1. Unpack the downloaded archive to your hard disk drive.

    The archive contains two folders: 'x86' and 'x64'.



    2. Close the product you are applying the fix to.



    3. Copy the 'x86\tcClrHook.dll" file to the Extensions folder of the product.

    For TestComplete and TestExecute, the folder path looks like this:

    <Product Installation Folder>\Bin\Extensions\

    For TestRecorder, the path is as follows:

    <Product Installation Folder>\Bin\



    4. If you are running an x64 operating system, you will also need to copy the 'x64\tcClrHook.dll' file to the following folder:

    TestComplete, TestExecute:

    <Product Installation Folder>\x64\Bin\Extensions\

    TestRecorder:

    <Product Installation Folder>\x64\Bin\


  • weiwongfaye's avatar
    weiwongfaye
    Occasional Contributor
    Hi Jared,



    Thank you for your reply. 

    We were aware of the hotfix you mentioned and already use it since last year.



    Today, We try on another win7_64 machine with latest update installed, it works fine.

    But we still have two machines (win7_64 and XP64 )which have the problem. Not sure what's happening there.

    Will look into it more.



    Thanks anyway. :)



    Regards

    Jack
  • Hi Jack,



    I'd recommend reinstalling the .NET Framework on your machine. Probably, something is wrong with it.