dokan-dev / dokany

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

Install fails on Win11 - Paralles on Mac M1 #1228

Closed harrynorthover closed 1 month ago

harrynorthover commented 1 month ago

Feature request can skip this form. Bug report must complete it. Check List must be 100% match or it will be automatically closed without further discussion. Please remove this line.

Environment

Check List

Description

I'm getting an error when installing Dokany on my Windows 11 VM, on a fresh install. I've tried this several times, each with a fresh VM. This is with secure boot disabled. log.log

However, when I re-run the install, it then complains that Dokan is already installed. It looks like it's an issue with starting the service.

I'm trying to use MemProcFS, and when I manually run sc.exe create dokan2.sys binPath=C:\windows\system32\drivers\dokan2.sys type=kernel && sc.exe start dokan2.sys I get a BSOD with the error SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD. What failed: Dokan2.sys

Logs

Please attach in separate files: mirror output, library logs and kernel logs. In case of BSOD, please attach minidump or dump analyze output.

Liryna commented 1 month ago

Hi @harrynorthover ,

Could you please try to get the memory dump and analyse it ? https://github.com/dokan-dev/dokany/wiki/How-to-Debug-Dokan#crash-report-bsod

harrynorthover commented 1 month ago

@Liryna thanks for your help! Is this what you're after? dokanDump.dml.txt

Liryna commented 1 month ago

Oh sorry, you are running a Windows ARM64 but trying to use the msi x64 to install dokan which is not going to work since the driver cannot be emulated. You will need to manually install (sc create as you did) but with the arm64 binary present in the zip release.

harrynorthover commented 1 month ago

That worked. Sorry, and thank you! It seems to be an issue with MemProcFS not detecting the driver, as I can mirror a folder perfectly fine using mirror.exe

Liryna commented 1 month ago

Glad to hear it worked! I unfortunately cannot say why it is not detecting the driver. Could be a difference of version but looks like they are using the v2.