Scripting will not work in Windows 11

[QPR John]

Hi,

PS v 24.3. Win 11 (not sure of version as I reverted back to Win 10)

I have successfully used some VB scripting for quite a few years now. I recently upgraded my OS from Win 10 to Win 11.

Now the scripts do not work, I reverted back to Win 10 and it's working again.

Is there something I need to do to get it to work? 

Thanks John

[QPR John]

Sorry should have expanded, I use PS VB scripting in VB.Net. I have an app that I use to caption and save images in PS.

[QPR John]

Hi,

This is the error message I am getting...

System.InvalidCastException: 'Unable to cast COM object of type 'System.__ComObject' to interface type 'Photoshop.Application'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{5DE90358-4D0B-4FA1-BA3E-C91BBA863F32}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).'

[UMUZI]

I have the exact same error and this article comes up when searching.

[jazz-y]

Have you done a clean install of windows 11 or an upgrade? If it's an update, try uninstalling and reinstalling Photoshop. It is possible that during the upgrade process the objects required for VB ScriptingSupport to work were not re-registered in the operating system.

[QPR John]

Hi,

@jazz-y Thanks for replying. I Googled the error and I found a video that showed how to fix it. I used the ID from the error message and searched for it in the registry, it could not be found. On one of my WIN 10 PC's I found the entry, I exported it onto a USB and then imported it into the Win 11 registry and it worked.

It was an upgrade, I'm glad you mentioned that it would not have registered in the OS as it gives me confidence it's fixed.

I'm currently upograding back to Win 11 on my new laptop and I will uninstall PS and reinstall it to see if your recommendation works.

I will post the results.

Thanks again for replying, I was beginning to wonder if my post had been seen.

[UMUZI]

Can you share you script and the video you found.  

" I Googled the error and I found a video that showed how to fix it. I used the ID from the error message and searched for it in the registry, it could not be found. On one of my WIN 10 PC's I found the entry, I exported it onto a USB and then imported it into the Win 11 registry and it worked."

[QPR John]

@jazz-y 

I did as you suggested, uninstalled and reinstalled PS and it worked fine. 🙂

Have many other people had the same problem?

Thanks for your help.

John

[jazz-y]

@QPR John, reports of such problems are rare in the community.

[UMUZI]

I would search further afield.  Your first instinct should NOT be it's Microsoft's problem.  I've seen other reports reagrading COM and how rolling back Photoshop version 24 resolved the issue.  Not rolling back the OS.  Photoshop is the one with poor API, poor documentation, poorly written software not Microsoft.     

[UMUZI]

The solution that resolved the issue for my client was reinstalling Photoshop 2023. The root cause remains unclear. It could have been the Windows upgrade or Photoshop itself that damaged what seems to be Windows registry entries. The more likely scenario, however, would attribute the problem to a Windows upgrade, and this isn't the first time. After the upgrade, it rearranged my external drive letters. For several weeks, I suspected a hacking attack, only to later discover it had swapped my drive letters. I tried using recovery software to retrieve my files, but the only major directory I was concerned about was nowhere to be found. It was only then that I realized the relative sizes (free space) of the external disks in question (3 - 1 TB). That's a significant mistake! I've also noticed other quality lapses in Microsoft products. Nevertheless, they remain one of the top software producers globally.