Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disk is not mounted on logon (Windows 10 Home Edition) #971

Closed
andronov-alexey opened this issue Sep 30, 2019 · 5 comments
Closed

Disk is not mounted on logon (Windows 10 Home Edition) #971

andronov-alexey opened this issue Sep 30, 2019 · 5 comments
Labels
state:stale Issues without any activity that will be closed automatically type:bug Something isn't working

Comments

@andronov-alexey
Copy link

I tuned cryptomator to start on windows via Windows Task Scheduler, but it won't show mounted disk on windows explorer
Logfile says drive was mounted successfully
The task is set to mount on specific drive letter ("M" in my case)
If I start cryptomator manually using shortcut it mounts disk and works as expected

What I've tried:

  • start Windows Scheduler Task using SYSTEM and user privileges (+ delaying start for 1-2-3 minutes)
  • open "unlocked" disk (see "Cryptomator running.PNG") via Cryptomator "Open disk" context menu (see "Failed to open unlocked disk")
  • lock/unlock storages in cryptomator, doesn't mount disks unless app is restarted
  • use dropbox/google drive storages

System Setup

  • Operating system and version: Windows 10 1903 with latest updates
  • Cryptomator version: 1.14.15
  • Drive: Dokany

Reproducibility

Always

Additional Information

No mounted disk Windows Explorer
Cryptomator running
Failed to open unlocked disk
locked disk options
cryptomator options
cryptomator0.log

@andronov-alexey andronov-alexey added the type:bug Something isn't working label Sep 30, 2019
@overheadhunter
Copy link
Member

Can you translate what the error message on the second screenshot says?

When registering the app in the scheduler, you need to make sure to run it as the same user as you log in with. Otherwise the drives will be visible only for the owner of the process.

Of course, autostart is not yet officially supported, but some users managed to get it working as described in issue #418.

@andronov-alexey
Copy link
Author

Can you translate what the error message on the second screenshot says?

"Location is not available
M:\ refers to a location that is unavailable. It could be on a hard drive on this computer, or on a network. Check to make sure that the disk is properly inserted, or that you are connected to the Internet or your network, and then try again. If it still cannot be located, the information might have been moved to a different location."

When registering the app in the scheduler, you need to make sure to run it as the same user as you log in with. Otherwise the drives will be visible only for the owner of the process.

Yeah, I tried to run it under logon user as well with no avail

Of course, autostart is not yet officially supported, but some users managed to get it working as described in issue #418.

Thanks I'll take a look at it

@infeo
Copy link
Member

infeo commented Oct 1, 2019

Addtional info: Normally your vault is mounted with the dokany flag CURRENT_SESSION. This flag prevents other users to access your vault. (including system)
You can choose in the advanced options of your vault to use your own mount flags (for usage see https://community.cryptomator.org/t/what-are-the-custom-mount-flags/3966)

@andronov-alexey
Copy link
Author

andronov-alexey commented Oct 2, 2019

I solved the problem by granting "Full access" in "Cryptomator.exe"'s properties and now it works :)

cryptomator full access

PS: forgot to mention I use Win10 Home Edition
PSS: Guys thanks by the way for the awesome product :)

@andronov-alexey andronov-alexey changed the title Disk is not mounted on windows 10 start Disk is not mounted on logon (Windows 10 Home Edition) Oct 2, 2019
@stale
Copy link

stale bot commented Dec 31, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Dec 31, 2019
@stale stale bot closed this as completed Jan 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:stale Issues without any activity that will be closed automatically type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants