mirror of
https://github.com/brentvollebregt/auto-py-to-exe.git
synced 2026-04-25 11:45:49 +03:00
[GH-ISSUE #526] Blocker of generating output in critical dirs #407
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mostypc123 on GitHub (Mar 16, 2025).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/526
Originally assigned to: @brentvollebregt on GitHub.
New Feature Description
A blocker of directories where the user should not generate output files, such as system32. If you run auto-py-to-exe as an admin, it could mess up your windows installation.
Reason For New Feature
I was using auto-py-to-exe and it set the output dir to system32. As I do use terminal as admin a lot, it could write to system32 and it might as well just break Windows.
@github-actions[bot] commented on GitHub (Mar 16, 2025):
👋 Hi, just a reminder that if you haven't read the help post yet, give it a read to see if your issue is covered in it and make sure to follow the debugging section.
Also please note, as stated in the README, if your issue is only associated with your application and not auto-py-to-exe itself, please do not create an issue in this repository - instead, comment on the help post, video or create a new discussion.
@brentvollebregt commented on GitHub (Mar 17, 2025):
Might be better as a warning added through
get_warningsin/auto_py_to_exe/utils.pyinstead of fully blocking?Generating the output folder in
C:\Windows\System32shouldn't break things - but I understand it's not ideal, hence just the warning.@mostypc123 commented on GitHub (Mar 17, 2025):
yeah that would be better
@brentvollebregt commented on GitHub (Mar 19, 2025):
I have a change in ac21cda41812e1c3fb83e8cac33f72dbc12e038a which looks fine - however it's missing a why.
I'm unable to see why running auto-py-to-exe in
C:\Windows\System32is an issue? I understand it wouldn't be recommended, but it's just adding anoutputfolder by default which probably doesn't exist already. I have seen many people asking for help running inC:\Windows\System32and not complaining about it breaking anything.@mostypc123 do you know how this could "break windows"?
@mostypc123 commented on GitHub (Mar 21, 2025):
you're right - not really break windows, but it's not good to do it.
@mostypc123 commented on GitHub (Mar 21, 2025):
I think you can remove the why from the warning and keep it as it is
@brentvollebregt commented on GitHub (Mar 22, 2025):
This is now on master