Issue with "I couldn't find any D:" error and Error Code 13 and more on Windows 10/11 Body #477
Replies: 1 comment
-
|
I already resolved. I just change the name of the files for "Photos from XXX". |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I'm having trouble using GooglePhotosTakeoutHelper (v3.4.3) on Windows. Despite following several troubleshooting steps, I cannot get the tool to process my photos correctly. Here is a summary of my environment and what I've tried so far:
Current Setup:
Tool Version: v3.4.3 (Dart successor).
OS: Windows 10/11.
Input Path: C:\Users\Davi Brandão\Downloads\input
Output Path: C:\Users\Davi Brandão\Downloads\Fotos_Processadas
Steps Taken:
Folder Structure: I manually renamed the Takeout folders to just the years (e.g., 2020, 2021). I also tried placing these year-folders inside a subfolder named Google Photos within the input directory, as suggested in some threads.
Permissions: I encountered Error Code 13 (Permission Denied). I attempted to fix this by running the CMD as Administrator and ensuring the .exe was unblocked in properties.
Execution Methods:
Tried direct CMD commands with quotes to handle the space in my username (Davi Brandão).
Tried --interactive mode (the folder picker opens, but the process fails to start after selection).
Created a .bat script to automate the execution and handle paths more reliably.
Command Flags Used:
--input / --output
--albums nothing
--copy
--fix (This was the only one that seemed to trigger a file scan, but it didn't move files to the output folder).
--guess-from-name (resulted in many "not set" files).
Persistent Errors:
"I couldn't find any D:": This is the most frequent error. Even with the folders renamed to years and placed correctly, the script often fails to recognize the directories.
"FormatException: Missing argument for fix": When trying to use the fix flag as a workaround.
"FormatException: Could not find an option named 'find-json'": (Realized this might have been removed in v3.4.3).
Current Result:
When I use the --fix command, I get about 7,500 "set" and 5,700 "not set" files, but the Output folder remains empty. When I use the standard --input command, it immediately returns the "I couldn't find any D:" error.
Does anyone know if there is a specific naming convention or a nested folder depth requirement for v3.4.3 that I might be missing? Or is the space in the Windows username still causing issues despite using quotes?
Any help would be appreciated!
Beta Was this translation helpful? Give feedback.
All reactions