dokan-dev / dokany

User mode file system library for windows with FUSE Wrapper
http://dokan-dev.github.io
5.21k stars 661 forks source link

Issues with installing latest (1.5.1.1000) build #1029

Closed SgtMcBiscuits closed 2 years ago

SgtMcBiscuits commented 2 years ago

Environment

Check List

Description

I'm trying to install Dokany 1.5.1.1000, which was just released. When doing so, it tells me there is another installation of that same version, and it needs to be uninstalled first. There is no other version installed, I have checked both through Windows uninstaller and CCleaner. I have stopped and uninstalled all previous drivers, and deleted all Dokan files I can find. Now that I've tried to install the new release, the previous release (1.5.0.3000) will no longer work either, instead giving me only the option to uninstall (which fails). I've tried installing manually, restarting my computer numerous times, etc. Since it's not installed, I can only give the log from when it tries to install.

Logs

Dokan_Library_1.5.1.1000_Bundle_20211126215556.log

tomato3107 commented 2 years ago

There should exist another log file for Dokan_x64 that is required for analysis (as the bundle log only tells us Error 0x80070643: Failed to execute MSI package). Please upload that as well.

Liryna commented 2 years ago

@tomato3107 Do you still have a dokan1.sys driver present in Windows/system32/drivers ?

SgtMcBiscuits commented 2 years ago

There should exist another log file for Dokan_x64 that is required for analysis (as the bundle log only tells us Error 0x80070643: Failed to execute MSI package). Please upload that as well.

Where would I find the second log file? The one I uploaded was from the installer itself.

Do you still have a dokan1.sys driver present in Windows/system32/drivers ?

No, I do not have the dokan1.sys file present.

EDIT: I've found this log in AppData/Local/Temp when I just tried to re-run the program

Dokan_Library_1.5.1.1000_Bundle_20211126232840_000_Dokan_x64.msi.log

tomato3107 commented 2 years ago

Your registry seems to be left in a FU state after your CCleaner runs.

In issue https://github.com/dokan-dev/dokany/issues/918 somebody fixed his similar problems by using the Microsoft tool Windows troubleshooter.

SgtMcBiscuits commented 2 years ago

Okay, you're correct, it's now installed and works. However, I'm now running into a different issue. With it installed and mirroring a network drive, I cannot write to the file system. My setup is this:

A SMB share on my local server, which I can use "Map network drive" on Windows and interact with the drive as usual, with full R/W access. However, if I use mirror.exe to map the drive as local in Windows, I am unable to write files to it. This is the batch file I'm using:

"C:\Users\DELETED\Documents\Dokan\mirror.exe" /r \192.168.1.201\Disk /l L

When doing this, the drive successfully maps to the L: drive letter and appears, and I can read files with no issue. When using the right click context menu, under New I only have Folder, with an Admin icon next to it. If I drag and drop a file into the drive, small ones (<~1MB) appear to transfer okay, but larger ones will give me a Windows error, telling me the file no longer exists. I can transfer it to the drive as a network share through Windows though, and it appears and is readable through Dokan immediately.

What can be causing this behavior?

Liryna commented 2 years ago

@SgtMcBiscuits The mirror is not built for remote mirroring so such issues are expected. I imagine one of the request timeout or does not respond the expected data.

Instead of opening an issue specifically for this situation m, a feature request should be opened to have remote storage supported (if it does not already exist).

SgtMcBiscuits commented 2 years ago

Ah, I apologize, I was told by someone (unrelated to the project) that it was designed for this. Additionally, it had worked in the past for me, but I understand that was a fluke then. Thank you for your time!

Liryna commented 2 years ago

I would be very happy to review any contribution to support and stabilize remote storage with the mirror in case anyone seeing this would be interested!