P: (Win) Photoshop 27.10 Script "Load Files into Stack" fails with an Error 44: Cannot convert.and cannot be executed

I’m having the same issue. Since updated LrC & Ps to the latest version, when I tried open multiple images to Ps, it popped up a message Error 44: cannot convert. Same message when I opened Ps and used Scrips to load files into stack. 

See here:

Moderators, ​@Sameer K  ,  please merge with existing thread:

P: (Win) Photoshop 27.10 Script "Load Files into Stack" fails with an Error 44: Cannot convert.and cannot be executed | Adobe DME

I've tried changing the language in Photoshop and reinstalling it, but the error persists.

I'm trying to use the PhotoMerge feature, but I keep getting an error message.

I tried reset with this script https://helpx.adobe.com/photoshop/desktop/get-started/settings-and-preferences/reset-preferences.html

but it wasn’t help.

Im using windows 11, and Photoshop 2026

I have the same problem, too

Hi team,

After updating to Photoshop v27.10 on Windows, running the **"Load Files into Stack..."** script immediately triggers an error and fails to launch the dialog.

* **Steps to Reproduce:**
1. Open Photoshop v27.10 (or Photoshop Beta v27.11) on Windows.
2. Go to **File** > **Scripts** > **Load Files into Stack...**
ファイル > スクリプト > ファイルをレイヤーとして読み込み

* **Expected Result:**
The "Load Layers" dialog opens.
* **Actual Result:**
An error popup appears immediately:
> **Error 44: Cannot convert.**
> **Line: 41**
> `-> $.evalFile(g_StackScriptFolderPath + "StackSupport.jsx");`

* **Observations & Environment:**
* **OS:** Windows 11 64-bit
* **Photoshop Versions affected:** Photoshop v27.10.0 and Photoshop Beta v27.11.
* **Mac Behavior:** Working normally on macOS (v27.10), issue appears isolated to Windows.
* **Workaround:** Rolling back to Photoshop v27.9.1 resolves the issue completely.
* **Notes:** Reinstalling clean v27.10 does not fix the issue. Replacing `StackSupport.jsx` from v27.9.1 also does not resolve it, suggesting an issue with path evaluation/handling (`g_StackScriptFolderPath`) in the Windows ExtendScript environment.

Multiple users in the Japanese community have verified and reproduced this identical issue on Windows.

Could the engineering team please look into this?

Thank you!