Calibre unable to create temporary file

Sonorazona · 10-14-2018, 12:35 PM

Hi all,

I ran into an issue today where Calibre installer is unable to create a temporary file needed for installation. I think it is related to an issue with Windows Defender that won't allow msiexe.exe to make changes to the system.

Has anyone else run into this problem?

I've posted a question to Microsoft about the Windows Defender/msiexe.exe issue and I'll update when I get a response from that. But if someone else has a solution other than configuring Windows Defender to allow msiexe.exe to make system changes (not sure how advisable that is and won't do it until I've received a response from MS) please let me know

-cm-

ShellShock · 10-14-2018, 03:43 PM

It is normal for installers to want to run with elevated privileges so that they can make system changes. You don’t configure misexec to allow it to make system changes (which is a permanent change), rather you give permissions for a specific installation to run with elevated privileges so it can make system changes (a temporary change for the duration of the installation). Depending on your UAC changes you should get prompted to allow the installation to proceed.

BetterRed · 10-14-2018, 05:18 PM

Quote:

Originally Posted by Sonorazona

Hi all,

I ran into an issue today where Calibre installer is unable to create a temporary file needed for installation.

<snip>

I assume you know this from an error message, please provide precise details, i.e. a screen shot.

There may be something in this thread ==>> Installiation Issue

BR

DaltonST · 10-15-2018, 10:10 AM

Oh, yes, I have had that problem in spades. This is how I had to originally fix it:

https://www.mobileread.com/forums/sh...14&postcount=4

However, since then I manually reinstalled Windows 10 Version 1803 April 2018 Update by using the "Windows Media Creation Tool" route. I specified "keep user files and existing applications", then let it go.

I then manually downloaded the cumulative Version 1803 update for September 2018 from the Windows Update Catalog at http://www.catalog.update.microsoft.com/Home.aspx and ran it.

Result: the Windows installer for 1803 treated the prior installation as "legacy", and totally reinstalled the Windows 10 user permissions and security settings, among all of the other things it does. That fixed it. No more Calibre temporary file errors, and just dying without notice.

DaltonST

Sonorazona · 10-16-2018, 10:06 AM

Thanks for all the great advice and information. I will follow up on the links to other information.

I rebooted the computer again and the problem went away. It is noteworthy that the same day as I tried to update Calibre I also tried to install Amazon Drive Desktop and had the same error.

I've had a Windows Defender update since the 14th so that may have also resolved the problem.

10-14-2018, 12:35 PM	#1
Sonorazona Junior Member Posts: 2 Karma: 10 Join Date: Jun 2018 Device: Kindle, Kindle App, Calibre	Calibre unable to create temporary file Hi all, I ran into an issue today where Calibre installer is unable to create a temporary file needed for installation. I think it is related to an issue with Windows Defender that won't allow msiexe.exe to make changes to the system. Has anyone else run into this problem? I've posted a question to Microsoft about the Windows Defender/msiexe.exe issue and I'll update when I get a response from that. But if someone else has a solution other than configuring Windows Defender to allow msiexe.exe to make system changes (not sure how advisable that is and won't do it until I've received a response from MS) please let me know -cm-

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CalibreDB add and Temporary file descriptors filling up disk	seru1us	Library Management	3	05-10-2018 11:22 AM
Calibre 2.7 Unable to open Database file	Gordo29	Devices	22	11-04-2016 11:10 PM
Unable to update Calibre as original install file is missing?	El_Splendido	Calibre	1	08-24-2012 04:43 PM
0.8.49 is unable to create directory on SD card	speedtouch	Calibre	5	05-01-2012 10:42 PM
Create MediaWiki and RTF links for opening an ePub file with Calibre viewer	johnsidi	Calibre	1	12-17-2011 01:31 PM

10-14-2018, 03:43 PM	#2
ShellShock Wizard Posts: 1,176 Karma: 2431850 Join Date: Sep 2008 Device: IPad Mini 2 Retina	It is normal for installers to want to run with elevated privileges so that they can make system changes. You don’t configure misexec to allow it to make system changes (which is a permanent change), rather you give permissions for a specific installation to run with elevated privileges so it can make system changes (a temporary change for the duration of the installation). Depending on your UAC changes you should get prompted to allow the installation to proceed.

10-15-2018, 10:10 AM	#4
DaltonST Deviser Posts: 2,265 Karma: 2090983 Join Date: Aug 2013 Location: Texas Device: none	Oh, yes, I have had that problem in spades. This is how I had to originally fix it: https://www.mobileread.com/forums/sh...14&postcount=4 However, since then I manually reinstalled Windows 10 Version 1803 April 2018 Update by using the "Windows Media Creation Tool" route. I specified "keep user files and existing applications", then let it go. I then manually downloaded the cumulative Version 1803 update for September 2018 from the Windows Update Catalog at http://www.catalog.update.microsoft.com/Home.aspx and ran it. Result: the Windows installer for 1803 treated the prior installation as "legacy", and totally reinstalled the Windows 10 user permissions and security settings, among all of the other things it does. That fixed it. No more Calibre temporary file errors, and just dying without notice. DaltonST

10-16-2018, 10:06 AM	#5
Sonorazona Junior Member Posts: 2 Karma: 10 Join Date: Jun 2018 Device: Kindle, Kindle App, Calibre	Thanks for all the great advice and information. I will follow up on the links to other information. I rebooted the computer again and the problem went away. It is noteworthy that the same day as I tried to update Calibre I also tried to install Amazon Drive Desktop and had the same error. I've had a Windows Defender update since the 14th so that may have also resolved the problem.