MobileRead Forums - View Single Post - Calibre can't access DB from Standard User, but does from Admin User (Win10)

medownunder · 05-27-2021, 08:44 PM

I hadn't used Calibre for a while, opened it successfully, saw there was an update so I installed that. It appeared to install successfully but on first launch it said the DB was corrupt, and when I followed the prompts to repair/restore the db these failed (both the Yes and No options failed).

I uninstalled, restarted Windows, and reinstalled from an Admin-type User Account, which then worked fine. But I want to use Calibre from my usual Standard-type User so I switched back to that. It has the original problem. Of course I can set Calibre to run as Admin, but then the library is stored in my Admin-type user which I don't want.

I think I may have switched my usual User Account from Admin to Standard Type since I first installed the earlier version of Calibre some years ago. Is this a known problem of recent Windows 10 updates, or of Calibre v5.18 (64bit)? Is there a fix?

Can you help? Many thanks in advance.

05-27-2021, 08:44 PM	#1
medownunder Junior Member Posts: 5 Karma: 10 Join Date: May 2021 Device: KINDLE	Calibre can't access DB from Standard User, but does from Admin User (Win10) I hadn't used Calibre for a while, opened it successfully, saw there was an update so I installed that. It appeared to install successfully but on first launch it said the DB was corrupt, and when I followed the prompts to repair/restore the db these failed (both the Yes and No options failed). I uninstalled, restarted Windows, and reinstalled from an Admin-type User Account, which then worked fine. But I want to use Calibre from my usual Standard-type User so I switched back to that. It has the original problem. Of course I can set Calibre to run as Admin, but then the library is stored in my Admin-type user which I don't want. I think I may have switched my usual User Account from Admin to Standard Type since I first installed the earlier version of Calibre some years ago. Is this a known problem of recent Windows 10 updates, or of Calibre v5.18 (64bit)? Is there a fix? Can you help? Many thanks in advance.