electron-forge make Error:ENOTEMPTY: directory not empty, rmdir 'C:\Users\*\AppData\Local\Temp\electron-packager\tmp-yZRjUa'

[JeffreyCheungGit]

Pre-flight checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project uses.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version

7.5.0

Electron version

33.2.0

Operating system

Windows 11 (24H2)

Last known working Electron Forge version

No response

Expected behavior

package.json:
"scripts": { "start": "electron-forge start", "package": "electron-forge package", "make": "electron-forge make" }, "devDependencies": { "@electron-forge/cli": "^7.5.0", "@electron-forge/maker-squirrel": "^7.5.0", "@electron-forge/plugin-auto-unpack-natives": "^7.5.0", "@electron-forge/plugin-fuses": "^7.5.0", "@electron/fuses": "^1.8.0", "electron-squirrel-startup": "^1.0.1", "electron": "^33.2.0" },

cmd run :
$=> npm run make

I expect can output make and **-win32-x64 normally.

Only the first time was a success, and the remaining dozens were failures

Actual behavior

Only output **-win32-x64 and error:

Thanks！

Steps to reproduce

run npm run make

Additional information

No response

[VerteDinde]

Thanks for reporting this issue! Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

I'm adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment.

Thanks in advance!

[JeffreyCheungGit]

Thanks for reporting this issue! Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.

Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.

I'm adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment.

Thanks in advance!

The code is the sample code of the official website, without any special code, only index.html and main.js files

[lunaDHD]

Thanks for reporting this issue! Would it be possible for you to make a standalone testcase with only the code necessary to reproduce the issue? For example, Electron Fiddle is a great tool for making small test cases and makes it easy to publish your test case to a gist that Electron maintainers can use.
Stand-alone test cases make fixing issues go more smoothly: it ensure everyone's looking at the same issue, it removes all unnecessary variables from the equation, and it can also provide the basis for automated regression tests.
I'm adding the blocked/need-repro label for this reason. After you make a test case, please link to it in a followup comment.
Thanks in advance!

The code is the sample code of the official website, without any special code, only index.html and main.js files

To fix this all you need to do is have a completely empty folder and run the command to create a template.