Maintenance for the week of December 15:
· [COMPLETE] PC/Mac: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] Xbox: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] PlayStation®: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] PC/Mac: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] Xbox: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] PlayStation®: NA and EU megaservers for maintenance – December 15, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
Error 1005
Since Monday's patch (3.0.8) I've been getting this error whenever I try to either run the Launcher or use eso64.exe: "Error 1005 - OSError_AccessDenied, A file could not be updated due to insufficient permissions or the file is in use by another process."
This seems to only be a problem for the 64-bit client, as I can run the 32-bit client (eso.exe) just fine. I can log into my account and all my characters as normal using the 32-bit version.
I have run the repair function five or six times at this point, and it always gets to the final stage of "Verifying" before throwing out this same Error 1005. I've restarted my computer multiple times, restarted the launcher multiple times, and, as stated, run the repair function in the launcher multiple times. Still cannot run the 64-bit client.
Anyone else having this issue? If so, did you find a solution?
This seems to only be a problem for the 64-bit client, as I can run the 32-bit client (eso.exe) just fine. I can log into my account and all my characters as normal using the 32-bit version.
I have run the repair function five or six times at this point, and it always gets to the final stage of "Verifying" before throwing out this same Error 1005. I've restarted my computer multiple times, restarted the launcher multiple times, and, as stated, run the repair function in the launcher multiple times. Still cannot run the 64-bit client.
Anyone else having this issue? If so, did you find a solution?
0
-
Oh, and just an addendum: I do and always have run the Launcher as an administrator. Same with both the 64- and 32-bit clients.0
-
Rhoric✭✭✭✭✭Check the permissions on the eso64.exe. Should be set to Allow for everything. Also check the permissions for the Bethesda.net_Launcher to see if it is also set to Allow for all.0 -
Check the permissions on the eso64.exe. Should be set to Allow for everything. Also check the permissions for the Bethesda.net_Launcher to see if it is also set to Allow for all.
Thanks for the response. I checked both files, they have all permissions set to Allow.
The launcher still won't finish the repair function, I get the same error, and I still can't launch the 64-bit client.0 -
Rhoric✭✭✭✭✭Well that is good. I checked the support knowledge base on this error.
https://help.elderscrollsonline.com/app/answers/detail/a_id/6490/kw/error 1005
This error can occur if the launcher does not have the required permissions to access certain folders. This problem can be fixed by running the launcher as an administrator.
Here is how to automatically run the launcher as administrator:
Right-click on the launcher icon.
Click on Properties.
In the Shortcut tab, click on the Advanced button.
Tick the Run as an administrator box, and then click on OK.
This option may be available under the Compatibility tab of some versions of Windows.
To do this, on your desktop, Right click the launcher and choose "Run as Administrator."
Give this a try.0 -
I did check that already. I've run both the launcher and both clients (64- and 32-bit) in Administrator mode since the start, which is why this problem is so odd. I've been using the launcher for nearly three and a half years without any issue until Monday's patch.
Something seems to be wrong with the eso64.exe file itself, as it's the only file in the client directory not showing as updated on 6/8/2017. It still shows the previous patch date of 6/1/2017. The launcher isn't updating the eso64.exe file because of this Error 1005, so the 64-bit client can't launch.
The PTS client launches normally from the Launcher, and the 32-bit client starts normally from a shortcut to eso.exe. Any use of eso64.exe does not work, though.
I'm just hoping there's a solution that doesn't involve a full reinstall, because I don't want to download all those files again on my slow connection.0 -
Rhoric✭✭✭✭✭What OS version 32 or 64. I don't know of any other way to get a working eso64.exe without reinstalling. As sending just the file is not really permitted as it is advised against by ZOS.0
-
Windows 10, 64-bit version. I think at this point I may just use the 32-bit ESO client through the weekend and cross my fingers that it magically fixes itself with the next incremental patch.
If not, I'll just reinstall while grumbling to myself.Edited by agabahmeatshieldb14_ESO on June 14, 2017 8:24PM0 -
Well, it's fixed now.
I tried running the 64-bit client through the Launcher today, and rather than giving the Error 1005, it immediately crashed. Tried it again, same result. Then I ran the Repair function (again), and 64-bit is back to working perfectly.
I didn't change anything from yesterday, so... it's a mystery. But, hey, whatever, it's fixed.
Thanks for the replies, @Rhoric. Much appreciated!0 -
Attackfrog✭✭✭agabahmeatshieldb14_ESO wrote: »Well, it's fixed now.
I tried running the 64-bit client through the Launcher today, and rather than giving the Error 1005, it immediately crashed. Tried it again, same result. Then I ran the Repair function (again), and 64-bit is back to working perfectly.
I didn't change anything from yesterday, so... it's a mystery. But, hey, whatever, it's fixed.
Thanks for the replies, @Rhoric. Much appreciated!
I am having this same issue. I had it a few weeks ago....same situation as you, tried running repair a bunch of times, opened a ticket then somehow, I restarted my computer, ran repair and it magically worked. I tried that again this time, but it still isn't working.
It would be great if there was some sort of response on this issue."You can have fun or you can have safety, but you can't have them both"
-A ten-year-old1 -
Attackfrog wrote: »I am having this same issue. I had it a few weeks ago....same situation as you, tried running repair a bunch of times, opened a ticket then somehow, I restarted my computer, ran repair and it magically worked. I tried that again this time, but it still isn't working.
It would be great if there was some sort of response on this issue.
Looking back, what fixed this for me was the most recent Windows update.
The 3.0.8 patch broke it on a Monday, but then that following Wednesday I installed a Windows update and the problem resolved itself.
Maybe this will help, but you can try checking for and installing any new updates for your OS.1 -
Attackfrog✭✭✭agabahmeatshieldb14_ESO wrote: »Attackfrog wrote: »I am having this same issue. I had it a few weeks ago....same situation as you, tried running repair a bunch of times, opened a ticket then somehow, I restarted my computer, ran repair and it magically worked. I tried that again this time, but it still isn't working.
It would be great if there was some sort of response on this issue.
Looking back, what fixed this for me was the most recent Windows update.
The 3.0.8 patch broke it on a Monday, but then that following Wednesday I installed a Windows update and the problem resolved itself.
Maybe this will help, but you can try checking for and installing any new updates for your OS.
Can't thank you enough! I went into Windows update and manually updated, restarted to install the updates, rebooted, ran repair again and now it is working.
Thank you so much! After CS tickets and everything...lol, stupid Windows just needed to update."You can have fun or you can have safety, but you can't have them both"
-A ten-year-old0