starred/zotify

Fork 0

mirror of https://github.com/Googolplexed0/zotify.git synced 2026-04-25 06:15:55 +03:00

[GH-ISSUE #87] [Bug Report] Credentials in System32 #73

New issue

Closed

opened 2026-02-27 04:57:23 +03:00 by kerem · 9 comments

kerem commented

2026-02-27 04:57:23 +03:00

Owner

Originally created by @snapina7format on GitHub (Sep 25, 2025).
Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/87

Originally assigned to: @Googolplexed0 on GitHub.

Ongoing error where I can't even boot up zotify, keep getting this error pictured below

Originally created by @snapina7format on GitHub (Sep 25, 2025). Original GitHub issue: https://github.com/Googolplexed0/zotify/issues/87 Originally assigned to: @Googolplexed0 on GitHub. Ongoing error where I can't even boot up zotify, keep getting this error pictured below <img width="1399" height="659" alt="Image" src="https://github.com/user-attachments/assets/be9169a0-411b-45c3-b7ff-f11455bdb7c4" />

kerem

2026-02-27 04:57:23 +03:00

closed this issue
added the
bug

question
labels

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@RGPZ commented on GitHub (Sep 27, 2025):

I imagine that it's because of where the credentials.json file is stored (that being your System32 file)

@RGPZ commented on GitHub (Sep 27, 2025): I imagine that it's because of where the credentials.json file is stored (that being your System32 file)

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@snapina7format commented on GitHub (Sep 27, 2025):

I imagine that it's because of where the credentials.json file is stored (that being your System32 file)

How do I fix that?

@snapina7format commented on GitHub (Sep 27, 2025): > I imagine that it's because of where the credentials.json file is stored (that being your System32 file) How do I fix that?

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@RGPZ commented on GitHub (Sep 28, 2025):

Change your credentials.json file location to somewhere else in your computer that won't affect your Windows installation like your documents folder if you can. There should be a command for it somewhere on the main page of this GitHub, I'm just too busy right now to check it.

@RGPZ commented on GitHub (Sep 28, 2025): Change your credentials.json file location to somewhere else in your computer that won't affect your Windows installation like your documents folder if you can. There should be a command for it somewhere on the main page of this GitHub, I'm just too busy right now to check it.

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@snapina7format commented on GitHub (Sep 30, 2025):

Change your credentials.json file location to somewhere else in your computer that won't affect your Windows installation like your documents folder if you can. There should be a command for it somewhere on the main page of this GitHub, I'm just too busy right now to check it.

I am getting a new error despite increasing the bulk wait time to 30

@snapina7format commented on GitHub (Sep 30, 2025): > Change your credentials.json file location to somewhere else in your computer that won't affect your Windows installation like your documents folder if you can. There should be a command for it somewhere on the main page of this GitHub, I'm just too busy right now to check it. I am getting a new error despite increasing the bulk wait time to 30 <img width="981" height="449" alt="Image" src="https://github.com/user-attachments/assets/10ef829c-bd97-4558-a655-8290802054a8" />

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Oct 1, 2025):

On a second look, something here is broken. The real question is why the credentials would ever get stored into the system32 folder.

I assume the CONFIG.get_credentials_location() used its fallback logic, pointing to the cwd of C:\WINDOWS\system32, but this fallback only happens when Python doesn't recognize the operating system environment. Your system is obviously Windows so sys.platform should return "win32" and use the default AppData path.

Unless a user explicitly sets CREDENTIALS_LOCATION = "C:\\WINDOWS\\system32" this should not be possible.

@Googolplexed0 commented on GitHub (Oct 1, 2025): On a second look, something here is broken. The real question is why the credentials would ever get stored into the system32 folder. I assume the `CONFIG.get_credentials_location()` used its fallback logic, pointing to the cwd of `C:\WINDOWS\system32`, but this fallback only happens when Python doesn't recognize the operating system environment. Your system is obviously Windows so `sys.platform` should return `"win32"` and use the default `AppData` path. Unless a user explicitly sets `CREDENTIALS_LOCATION = "C:\\WINDOWS\\system32"` this should not be possible.

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@snapina7format commented on GitHub (Oct 3, 2025):

On a second look, something here is broken. The real question is why the credentials would ever get stored into the system32 folder.

I assume the CONFIG.get_credentials_location() used its fallback logic, pointing to the cwd of C:\WINDOWS\system32, but this fallback only happens when Python doesn't recognize the operating system environment. Your system is obviously Windows so sys.platform should return "win32" and use the default AppData path.

Unless a user explicitly sets CREDENTIALS_LOCATION = "C:\\WINDOWS\\system32" this should not be possible.

Here's the thing, I don't even know how that happened. The only thing I can think how it got routed there was the new Windows 11 update. I never messed with the location of the zotify, only started having issues again with the new Windows.

How do I change it back to where it used to be? Just the typical command of 'CREDENTIALS_LOCATION='?

@snapina7format commented on GitHub (Oct 3, 2025): > On a second look, something here is broken. The real question is why the credentials would ever get stored into the system32 folder. > > I assume the `CONFIG.get_credentials_location()` used its fallback logic, pointing to the cwd of `C:\WINDOWS\system32`, but this fallback only happens when Python doesn't recognize the operating system environment. Your system is obviously Windows so `sys.platform` should return `"win32"` and use the default `AppData` path. > > Unless a user explicitly sets `CREDENTIALS_LOCATION = "C:\\WINDOWS\\system32"` this should not be possible. Here's the thing, I don't even know how that happened. The only thing I can think how it got routed there was the new Windows 11 update. I never messed with the location of the zotify, only started having issues again with the new Windows. How do I change it back to where it used to be? Just the typical command of 'CREDENTIALS_LOCATION='?

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@RGPZ commented on GitHub (Oct 4, 2025):

Yeah it should just be 'zotify --config-location "the path for where you want to file to be located in"

@RGPZ commented on GitHub (Oct 4, 2025): Yeah it should just be 'zotify --config-location "the path for where you want to file to be located in"

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@snapina7format commented on GitHub (Oct 6, 2025):

Moved it appropriately, but still getting this error

@snapina7format commented on GitHub (Oct 6, 2025): Moved it appropriately, but still getting this error <img width="1694" height="346" alt="Image" src="https://github.com/user-attachments/assets/c7fb4cb9-f7d0-4441-9d4f-ee084dd2b5db" />

kerem commented

2026-02-27 04:57:23 +03:00

Author

Owner

@Googolplexed0 commented on GitHub (Oct 9, 2025):

Might've been related to #97, whose fix should've fixed this too.

@Googolplexed0 commented on GitHub (Oct 9, 2025): Might've been related to #97, whose fix should've fixed this too.