AutoItX slow working after Windows 10 upgrade

[poddex]

Hello everyone.
I always try to work with old Windows 10 versions as much as possible because I know mane compatibility issues with Windows 10 upgrading. 
But I couldn't do anything else (I got drivers problem), and nothing couldn't help me besides upgrading, so I upgraded from 1807 to 1903.
And...get another problem 😃
I use AutoitX library in external project like this.

ObjectAutoIt=New COMObject("AutoItX3.Control");
ObjectAutoIt.AutoItSetOption("WinTextMatchMode",2);
        While ObjectAutoit.WinExists("",WindowHeader) Cycle 
            ObjectAutoIt.WinClose("",WindowHeader);
        EndCycle;
After upgrade I get that this line code 

While ObjectAutoit.WinExists("",WindowHeader)

become extremely low - ~ 20 seconds even if 10 windows open. But before upgrade it takes 0.5 s for a max.

And every time that this code line passes through  - it takes ~20s, (20.115, for example), not less, not more. Something pauses it to work.
How can I diagnose, what is that?
I tried reinstall whole AutoIt, but no results.
Thanks to all.

Edited September 7, 2020 by poddex

[poddex]

Forget a detail - option that I used:

ObjectAutoIt.AutoItSetOption("WinTextMatchMode",2);

[water]

I'm not sure this is true for AutoItX as well but IIRC there was a thread regarding slow performance with Windows 10.
Please search the forum an you will find something like this:

I think this problem is solved with the latest beta:

 

[poddex]

Read, will check the beta. Great thanks for info.

[poddex]

Checked. As for me, installing BETA 3.3.15.3 has NO effect.

Need help with diagnose this. 

[poddex]

The code from 1st post:

ObjectAutoIt=New COMObject("AutoItX3.Control");
ObjectAutoIt.AutoItSetOption("WinTextMatchMode",2);
        While ObjectAutoit.WinExists("",WindowHeader) Cycle 
            ObjectAutoIt.WinClose("",WindowHeader);
        EndCycle;

does this: when Project Windows closed, it finds all related folder-windows and closes them. Only folders are affected.

By testing slow-error, I found, that first iterations passes quickly, folders closes by it. But after closing last folder WinExists loop got a huge delay (~20 s) - on a line "While ObjectAutoit.WinExists("",WindowHeader) Cycle". So, delay appears at last of loop execution, only AFTER all windows matched for a condition (""",WindowHeader" ) close.
Need help with further diagnostic

[poddex]

Please, any help 😃

Any.

Maybe I can find such as verbose mode for AutoitX library?

Thanks.

[poddex]

Ok, I made some diag for this. And found, that I can't even sort opened windows by it's PIDs. I can't select only explorer-related folders for WinExists-condition and WinExists checked title-condition for ALL windows (by logic, yes, but I prove this one more time for me). Some of them caused WinExists function for huge delay described above. imho, it's not effective to see ALL windows, when I want to look for windows of a specific process. But I can't select it. I can get WinList habdles massive, I can get WinGetProcess PID (only one), but I can't point WinExists to look only for Windows caused by specific PID. And I can't to check which handle from WinList is for which PID to close them.
And finally I want to check if this Window EXISTS.
PIDs always changed, ok. But I haven't any ideas for now.
Maybe I'm doing some wrong? It's possible to avoid this delay issue or I must use another script-engine?
I found that WinList function has no delay. This fact shows that delay is exactly in WinExists function, when it "looks inside" a window information.
I found that "While ObjectAutoit.WinExists("",WindowHeader) Cycle" loop cycles as many times as explorer-folders windows are opened. So, WinExists cycles through ALL windows inside itself (not in my code, I see only succeeded loops). So, delay-problem is in WinExists function inside AutoItX library. And I can't trace which window causes it to delay because there is no any verbose (or I didn't find it) inside AutoitX.
Please, anybody, any suggestions will be appreciated.

Edited September 14, 2020 by poddex

[poddex]

Here is a list of WinList[ALL] statement of AutoItX in my code.

Earlier there are no problems with it. But now some window(s) causes a delay. What window can do that?

 

Windows.xlsx

[poddex]

Hmm, I see that this problem is not a mass problem 😃

Anyone help???

Maybe, I will try update Windows again and problem will go away?)))

[Earthshine]

i would suspect you have windows issues. when i face the needle in a haystack, i just blast the machine and install clean. all my stuff is backed up and in the cloud so it takes about 8 minutes to install windows 10 from usb

 

[poddex]

Installing Windows 10 is quick, no problem, but installing ALL other my programs and tools (including their settings) will take 2-3 hours waisting my time. It's easier to switch script engine 😃 

[Earthshine]

You wanted help getting auto IT to work properly on your system. And that’s the way to do it. Just because installing all your programs takes a while doesn’t matter. If you don’t want to do it then just use some other scripting language as you suggested and solve your own problem

 

But that won’t change the fact that your windows 10 image has issues and probably has more problems than you are noticing.

Edited November 19, 2020 by Earthshine

[Danp2]

@poddex Do you still experience the slowness with a simple script like this?

Set oAutoIt = WScript.CreateObject("AutoItX3.Control")

If oAutoIt.WinExists("Untitled -") Then
    WScript.Echo "Window exists"
Else
    WScript.Echo "Window doesn't exist"
End If

 

[poddex]

Still experience with 1903, When I update Windows, I post results about testing here.

[Danp2]

FWIW, the above code runs quickly for me with 20H2

[Earthshine]

I don't want to download your spreadsheet. you can post code here. we can dummy up our own spreadsheets. what antivirus do you use?

Edited November 20, 2020 by Earthshine

[poddex]

On 11/20/2020 at 8:31 PM, Earthshine said:

I don't want to download your spreadsheet. you can post code here. we can dummy up our own spreadsheets. what antivirus do you use?

Same antivirus as before Windows update 😃 ESET Internet Secirity.

I updated Windows for 1909 - nothing changes, still exprerience the issue.

Yesterday evening MS didn't want update me for 2004, only for 1909 😃

 

[Earthshine]

Eset is terrible for windows. I bet this is your problem 

[poddex]

How this explains that before update all was perfect.

I will test with and without ESET and post result here.