till213
commented
1 year ago Hello,
Thank you for reporting this issue! In fact, I can now reproduce this issue (even on Windows 10), and it is as I had thought: the issue is related to "ransomware protection", as introduced by Windows 10:
(The URL points to the German site, but I am sure there is a "language selector" somewhere on that site)
In any case, "ransomware protection" (specifically: "protected folder access") was disabled in my case. I have now enabled it, and after having made sure that "SkyDolly.exe" is not in the list of "allowed applications" I can now reproduce the "file not found" issue:
And then, while trying to create a new logbook (CTRL + N) in my (now protected) "documents" folder:
However it should be possible to create new logbooks in non-protected folders, such as c:\temp (that I have created previously):
One way (workaround? By Windows design?) to allow SkyDolly.exe to create logbooks in any protected folder is to add it to the list of "allowed applications":
The easiest way is to choose "last blocked app":
And then select SkyDolly.exe (with the appropirate path where you have unzipped it):
At this point you need to make a concious decision, by trusting the app SkyDolly.exe (and in general for any other app that you add to this list): SkyDolly.exe now will get access (both read and write) to your protected folders, such as your "documents" folder. Click on the "+" (plus) button to add the app to the list of "allowed apps".
Again, the alternative is not to give SkyDolly.exe any permission, and store your logbooks to a non-protected folder (such as c:\temp, or any better named folder). This is a decision you must make.
If you have decided to add SkyDolly.exe to the list of "allowed apps" then your list should look something like this:
(Again, with corresponding paths)
Once you have done so you should then be able to create your logbook in your "documents" (or any other protected) folder:
I will keep this issue open for now, as I think the process should be smoother: I would expect Windows to ask for permission once you try (via the file selector) to create a folder / file anywhere in a protected folder. I assume (have to re-read the Windows API documentation) that this is related to the so-called "manifest" files: XML documents that are typically embedded into the executable (here: SkyDolly.exe). Hence my initial reference to the other issue, that might also be related to the currently embedded (and "generic") XML manifest file.
But do let me know if adding SkyDolly.exe (if you decide to do so) to the list of "allowed applications" does help already in your case!
I am aware that the above screenshots are Windows 10 specific - I hope you figure out the corresponding settings in Windows 11 ;)
PhilM5253
re our previous conversations ...
I am using SD v0.16.3
No - as far as I can see / tell - SD is NOT creating a log file, that I can ever find, in any location, via File Explorer.
What seems to be happening (to my untutored eye) is that SD is running a check to see if there is an existing log file: that would be loaded if present, both to be available for use and to prevent a new, default file being opened which would (?) overwrite the existing file.
On first use, there is no existing log file, and so SD correctly (?) shows an error message that no file exists.
If (?) SD should then create a new, default file for use, is it that next step that is not happening?
And, as said before, I cannot manually create a new file either.
In trying to open, create and save a log file, file explorer can never 'see' a *.sdlog file with which to perform any operation.
Is the first, correct (?) error message that no file exists on opening somehow stopping the create / save file actions from working as expected?
As noted in the other issue post, SD IS creating Registry entries on my system: it was that info that was in my screenshot (posted here also for ease of reference): I don't have any idea what the Registry entries should look like or contain, but I thought they might help explain was is / is not happening?