![]() ![]() However, from my prior experiences with Win7 I know that, occasionally, problems of this nature could be related to protection modes / ownership of the files. None of the solutions you suggested worked for me. Today I successfully installed DIABLO III on 1 WinXP/32bit and 3 Win7/64bit machines, some from the DVD, some from online download and then, on machine#5 I got stuck with the problem you guys describe. Good luck it must work it worked on Vista…… Good Luck! So at the first try it started installing and now im at 100% install after finishing this. I opened the install file back up and it starts at the install screen now, no more update files portion. Ok now that I was stuck all I did was end all the agent.exe processes I had up and exited the install. On when I say open around 8 of them I mean keep them all running there will be about 8 agent.exe files running what this did for me was push the update through to the install and froze me on install but guess what! you made it through the update files portion. Now you’re at the Agent.exe file what you do is keep the update on in the background and you keep opening the agent.exe file and it will slightly push the update through you will need to open around 8 or more i opened around 10. Ok now right click it and hit Open File Directory. Try to run you’re file ok you’re stuck I know now Ctrl + Alt hit delete now you’re in task manager go to processes and you see agent.exe running. I was stuck at 77% like everyone else on update files. Ok guys im on windows vista 64bit ok the worst windows os ever. ![]() I will add more fixes as I find them. Feel free to share one that works for you. PART file means you haven’t finished downloading. decryption error might also indicate a corrupt download. Run the downloader in the same directly you chose originally and it should fix the files automatically and/or finish downloading.  Fix #5 Additional Notes: If you get a decryption error it means you probably didn’t finish the download. Check the folder you downloaded your files into for any that say. All you have to do is replace his version with your old version, and hopefully everything should work (as it did for me).” -SCH from comments An user on the forums posted his version of the C:\ProgramData\Battle.Net folder and uploaded it. “I followed all of the posted fixes and none of them were working for me. ![]() Many are reporting success. Proceed with Fix #5 at your own risk, WAIT! it will get stuck for a min or so and then work Go to C/programdata/ /agent and run the “Agent” executableĥ. Close it, and ctrl+alt+delete and end the “Agent” process.ģ. Run the diablo insall thing… let it get stuck.Ģ. Good luck!įix #4a – Clarification for Fix 4 by GarytheOakġ. Start the agent application manually and after that start Diablo III setup file in your Diablo-III-8370-enGB-Installer folder. This one worked for me: try and find the agent application in the folder (for example C:\Documents and Settings\All Users\Application Data\\Agent). Run the Downloader again, as administrator, and see if it gets past the “Updating Setup Files” window. Right Click the Icon, Run as Administrator.ĭelete your C:\ProgramData\ folder.ĭelete your C:\ProgramData\Blizzard Entertainment\ Cache folder. Select Properties > Compatibility > Check Run this in Compatibility Mode for… > Choose Windows XP (Service Pack 3) (Note: Does not work on Vista.) Right click on the Diablo 3 setup file you downloaded via the Blizzard Downloader Run your Diablo 3 setup as administrator and it should quickly go through Updating Setup Files and bring you to an install screen. Congratulations, your game now (hopefully) works!  If this solved your issue, spread it around. Go to Control Panel > Administrative Tools > Services Here is the fix that finally worked for Graev: After pre-ordering tonight and downloading the client to be ready for Tuesday, we ran into the same problem and thought all hope was lost. Graev has Windows Vista and could not get past the “Updating Setup Files” little window that came up. We scoured the support forums for days, Googled, and had no luck until tonight. Graev was unable to play Diablo 3 during the beta due to a problem with the launcher giving an error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |