
Hey all I went through the last few pages of threads on this board and didn't see anything like what I'm getting and figured I'd start a new one.
So yeah, after unzipping I attempt to load Dolphin.exe and it appears to begin loading and the cursor spins then goes back to normal. No sign of the program....UNTIL I check my task manager and see this:
![[Image: 7cc79d3636.png]](http://puu.sh/eOxbj/7cc79d3636.png)
Woahhh did I really try to open it that many times? Well yeah, but apparently I can't kill any of them without restarting. After seeing this I restarted and decided to try the most recent stable for my system (over 1 year ago)and it worked well enough but I'd like to be current. I also tried running the current build under different compatibility modes but still nada.
Lemme know if I need to include more details, will post asap.
UPDATE: I am currently downloading and trying several of the most recent builds to see if any of them introduced a bug.
UPDATE 2: After trying a 10 of the most recent versions as well as a build from over a month ago (which I can only assume is enough time to have ironed out any bug that completely prevents startup) I'm getting the same issue so obviously it's on my end. Still stumped.
So yeah, after unzipping I attempt to load Dolphin.exe and it appears to begin loading and the cursor spins then goes back to normal. No sign of the program....UNTIL I check my task manager and see this:
![[Image: 7cc79d3636.png]](http://puu.sh/eOxbj/7cc79d3636.png)
Woahhh did I really try to open it that many times? Well yeah, but apparently I can't kill any of them without restarting. After seeing this I restarted and decided to try the most recent stable for my system (over 1 year ago)and it worked well enough but I'd like to be current. I also tried running the current build under different compatibility modes but still nada.
Lemme know if I need to include more details, will post asap.
UPDATE: I am currently downloading and trying several of the most recent builds to see if any of them introduced a bug.
UPDATE 2: After trying a 10 of the most recent versions as well as a build from over a month ago (which I can only assume is enough time to have ironed out any bug that completely prevents startup) I'm getting the same issue so obviously it's on my end. Still stumped.