Diablo Ii Installer Has Stopped Working
Posted : adminOn 5/10/2018Found the solution for this. Posting in a new separate thread, but i will post it here below as well: Blizzard Update Agent has failed [FIX - for Multiprocessor systems (not just multicore)] Inspiration for the fix was a search on google: And then I got the idea myself, to use a program to force management of process threads.
I found this: ProcessLasso. For this to work, 1.) Download ProcessLasso: 2.) Install ProcessLasso. 3.) Delete all the Battle.net and Blizzard directories in ProgramData folder. Almanaque Mundial Pdf Reader.
4.) Start ProcessLasso. 5.) right-click explorer.exe (in ProcessLasso) and select >Default CPU Affinity >Avoid Non-Physical Cores 6.) right-click explorer.exe (in ProcessLasso) and select >Default CPU Affinity >Select CPU Affinity >leave cores 0, 2, 4, 6 checked, rest unchecked. 7.) Start Diablo III Setup.exe 8.) Immediately go into ProcessLasso, and do steps 5-6 only for 'Diablo III Setup.exe', for step 6, only leave core 0 checked, all the rest unchecked. 9.) In ProcessLasso, do steps 5-6 only for 'Agent.exe' for step 6, only leave core 0 checked, all the rest unchecked. 10.) Now, for all of the above, you must also set their current affinity to the same as the default. (This goes especially if the Agent.exe is opened several times, you must do this for every instance (until you have set the default values, more might open, and for every Agent.exe process, you must do this). The reasoning for restricting explorer.exe is that Agent.exe spawns a subprocess that calls explorer.exe, and is unable to handle it, if it has too many cores.
And as explorer.exe will spawn child processes based on Agent.exe's commands, it will fail, as explained in the top second link. Tbh, i simply dont want to go those lengths. If Blizzard had a bugged component they should fix it, it not up to us to find a workaround for their problem. I have a 64bit Windows7 and I also have this 'Updating setup files' problem.
Some of the things I tried are: 1. Rename/delete agent file in programdata 2. Try it in safe mode with networking (hard to do when secondary logon doesnt work in safemode) 3. Delete blizzard cache, 4. Delete battle.net out of programdata 5. Nikon Mh-30 Instruction Manual. shut down agent service and reload while the installer is running. 6.check secondary log on is activated p2p is off 7.
Different comptibility modes 8.turn uac off 9. Make sure download is from latest client, not previous buggy one, that had to be patched on launch day 10) Some of the other solutions are even more far fetched. Uninstall WoW????????????? OS Upgrade??????????????????? Ofc at a time, from blizz's advice for example: Run downloader program again, and make sure that it has finished downloading completely and that it launches the installation automatically?
I can’t get Diablo 2 to install on my new laptop. Will this fix the non-working gamma and contrast sliders in the. How to Play Diablo II on Windows 10.
If you close the downloader and launch the installer yourself, the game files won't have finished yet, so you may experience issues I've downloaded the whole set up files 3 times (corrected version), always deleting every single bit of content (all the Battle.Net, etc.). With always the same result. In the end, after being sure Agent.exe isnt running in the processlist I tried these: A) Since I already have the 7.60Gb of installation files (and i waited for downloader to launch automatically installation everytime i downloaded the 7.6gb again), I run set up from there. A1) C: ProgramData Battle.net Setup diablo3_engb Log I see 2 logs everytime: 2012/05/20 10:43:17.408 - Blizzard Setup v500 at 'Z: Programas Diablo Diablo-III-8370-enGB-Installer Diablo III Setup.exe' for diablo3_engb enGB reporting for duty! 2012/05/20 10:43:17.408 - Setup Complete! 2012/05/20 10:43:17.408 - Bootstrapper Stage: CHECK_PERMISSIONS 2012/05/20 10:43:17.408 - Fix permissions is not set. 2012/05/20 10:43:17.408 - Bootstrapper Stage: CHECK_RUNNING_INSTANCE 2012/05/20 10:43:17.411 - Bootstrapper Stage: CHECK_ELEVATION 2012/05/20 10:43:17.411 - We don't need to elevate.