Error during process initialization. Cannot open directory "C:\Users\<username>\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned". ERROR_PATH_NOT_FOUND: Das System kann den angegebenen Pfad nicht finden. [FindFirstFileEx]
Why is this happening? With the earlier versions I didn't get this message.
Revert to previous version to confirm that the issue goes away. It will likely still be present.
If it works with a previous version of FFS, then reinstall the current version and see if it is still an issue.
Also, check the SMART data of the drive with gsmartcontrol and run a chkdsk if it is healthy
Revert to previous version to confirm that the issue goes away. It will likely still be present.
If it works with a previous version of FFS, then reinstall the current version and see if it is still an issue.
Also, check the SMART data of the drive with gsmartcontrol and run a chkdsk if it is healthy
xCSxXenon, 24 Jul 2023, 15:26
This is a issue with version 12.5. I use FreeFileSync in daily manner and very often. So with 12.4 and earlier this error didn't come to the log. But with 12.5. The path isn't available on Windows Server Editions. The question is why FreeFileSync is using this path?
And this issue has nothing to do with a drive error.
Last edited by TheExpert on 24 Jul 2023, 17:06, edited 2 times in total.
The path isn't available on Windows Server Editions and on Windows 10. The question is why FreeFileSync is using this path? So every synchronization ends now with errors even if the synchronization itself is successful.
And what's more confusing: On a Windows 10 system there are 3 different synchronization jobs running. But the error happens on only 2 jobs. I expected that all 3 jobs are getting the error message.
A Beta-version is never a Donation version.
If a Beta version proofs to solve the problem it is intended to solve, the solution will very likely be incorporated in the next official release, and will then also be available as Donation version.
