Issue with Autoitobject UDF

[MattHiggs]

Hello all.  So, I posted an issue a while ago concerning an issue I was having with @ProgAndy's Autoitobject UDF.  I will include the original post (with some additional info for convenience) below:
 

Quote

I had an issue with an autoit script I wrote for the longest time, and only just now was able to resolve the problem, but the solution doesn't make any sense to me.  Let me back up.  I wrote an autoit script which you can think of as a media launcher: you select folders for it to monitor for media files and double click the item in the list box to launch the file.  I recently added a cool feature which utilized @ProgAndy's Autoitobject UDF which used Directshow  to allow the script to display a preview of a media file when it was right clicked in a list view.  The below gif displays the functionality when it is working:

  This new feature worked for a long time, but suddenly stopped working one day: the script would not show the preview of the file when it was right clicked, no matter what I did.  The below gif shows the broken functionality:

Fast forward to today, and I tried something I thought so stupid that there was no way that it could possibly resolve the problem: I copied the code from that script, created a new one in the same folder with a slightly different name, pasted the code into that script, saved it, compiled it, and tested it.  The result?  It worked!!  The preview functionality was working on the newly compiled script, but still not working on the old one, despite both having identical code.

So, for the longest time, I didn't know WHY simply moving the autoit executable would fix the issue.  Until today.  I found that the reason the Directshow functionality breaks when a DWord registry value whose name contains the full path to the Autoit executable is added to the HKEY_CURRENT_USER\Software\Microsoft\Direct3D\Shims\EnableOverlays registry key:

So, that being said, deleting these registry values restores the DirectShow functionality to the Autoit script.  I post this because I use this script very frequently, and this directshow breaking action has occurred numerous times, and I would have to move the script to a new location whenever the script stopped working.  I do not know what exactly is creating these registry values.  I know the code in my script isn't doing it (you can take a look at the script here).  So, is it the Autoitobject UDF?  Or is it the Windows 10 operating system.  Is there any way that I can stop the registry values which break the script from being created in the first place?  Oh, btw, below are my operating system specs:

[seadoggie01]

It sounds like it might be Windows changing it for you... see here. They want you to update to video mixing render 9, as you can see here

Can you change the value to 0 to fix it for now? A hacky solution might be to throw a RegDelete into the beginning of the script  

[MattHiggs]

On 5/11/2020 at 10:27 AM, seadoggie01 said:

It sounds like it might be Windows changing it for you... see here. They want you to update to video mixing render 9, as you can see here

Can you change the value to 0 to fix it for now? A hacky solution might be to throw a RegDelete into the beginning of the script  

Very interesting.  Ok.  I will give it a shot.  Thanks for the input.