Jump to content

error 0x3fff then "Error Creating temporary file" with mirror.


Recommended Posts

Eset 8.0.8028.0. When the first client is updated I get the 0x3fff error. After several updates, I get an error creating a temporary file.
I found a similar topic, but the solution from the topic doesn't help me. How to fix it?

 

Link to comment
Share on other sites

  • Administrators

Check the system and user TEMP and TMP variables and make sure the folders they point to do not contain too many files. Empty the folders in safe mode (some files may not be possible to remove).

Link to comment
Share on other sites

1 hour ago, Marcos said:

Check the system and user TEMP and TMP variables and make sure the folders they point to do not contain too many files. Empty the folders in safe mode (some files may not be possible to remove).

I tested on clean Windows 10 pro 2004 and Windows server 2019. Сlearing those folders doesn't help

Link to comment
Share on other sites

  • Administrators

Please generate a Procmon log while attempting to update, compress it and upload it here.

Link to comment
Share on other sites

11 minutes ago, Marcos said:

Please generate a Procmon log while attempting to update, compress it and upload it here.

My actions:

1.Created a mirror in the folder f:/eset
2. Updated eset on another pc from my mirror.
3. I press the button to check the update on the eset mirror and I get an error 0x3fff

Logfile.zip

Link to comment
Share on other sites

I noticed that when deleting an archive with logs from mirrors folder, the error disappears until a new archive appears.

eset norm.PNG

eset.PNG

Link to comment
Share on other sites

  • Administrators

Please carry on as follows:
- in the advanced setup -> tools -> diagnostics enable complete application dump + advanced update engine logging
- reproduce the issue
- disable advanced update logging
- collect logs with ESET Log Collector
- upload the generated archive here or to a safe location if too big to be uploaded here and provide me with a download link in a private message.

Link to comment
Share on other sites

  • Administrators

This is a known bug which will be addressed in the next version of Endpoint v8. You can work around it by any of the following:

- do not use multi-level mirrors
- do not use the ESET http server to serve mirrored updates

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...