I was having the exact same problems as the OP. What I did to fix it, was I uninstalled the game. Reinstalled the game with out the update and installed it in my C drive folder which (windows 7) is located. Than I ran the game, It seems to run perfectly now. I am going to see what happens when I install the update... I'll edit this post to mention what happens.

Update: The update works fine. I don't know why it worked. I am suspecting the game has to be installed with out the update first and ran for the UDK to process the files since there is a Terms of Agreement that shows up I never saw before.

Yeah, this particular problem is not GPU related. GPU issues CAN still happen with the game (particularly with the Intell integrated HD3000 GPU, which GPU updates can resolve) but this issue, if it's what I think it is, is related to the initial game setup. There are some tricks people can try listed in that thread, you might also be able to run the installer with -progressonly as a launch parameter. I'm working on a more proper fix though. Sorry for the issue, guys :-(

I added this fix to the PC Gaming Wiki page for Tower of Guns.

I don't know if this will help anyone, but I also had the "Built with UDK has stopped working" message after the splash screen, so I re-installed.

Now the game boots, but the screen is pitch black except for the epilepsy warning, so I restarted my computer and ran the game as an admin from Start Menu > Games and now it's all good.

I have full confidence that Joe will be able to identify and fix the problem(s) causing this issue. For my part, I'm just glad that the workaround I found was able to be of some help.

Had the same problem with my fresh, patched install, [url=http://www.gog.com/forum/tower_of_guns/tower_of_guns_crashes_when_starting_up/post9 ]Loonie's workaround [/url]did the trick for me as well. Thanks, BB!

I'm getting this too. After reinstalling, launching the game and reinstalling the patch it worked again, but on the second time I ran the game, it crashed. However, if I use the previous patch instead of the current one, it doesn't crash.

For those of you crashing on the update..

inside this .zip file (http://www.towerofguns.com/u/PutThisInTowerofGunsSlashBinaries.zip) is a file called Unsetup.exe.

If you use it to replace the Unsetup.exe file thats in the towerofguns/binaries directory you might be able to bypass the crash. (Make a backup of the old Unsetup.exe file first though, just in case).

I'm not *positive* about what the issue is, but I have suspicions. If it's what I suspect, than this should bypass the problem. If anyone with the crash is able to tell me if this fixes things, I'd appreciate it.

Thanks!
-Joe

Much like GOGer raklar, I encountered 'Built with UDK has stopped working' again. It's strange because it happened not when I launched the game for the first time after the new patch but a hour later when I went to play again. I uninstalled the game but kept the save files, then reinstalled the game and patch following the workaround I mentioned in this thread. That seems to have worked but also seems to indicate the problem is intermittent, making it very likely to be a pain in the ass to track down.

Seeing that it demonstrates intermittence, would there be a way to legitimately tell if the new Unsetup.exe is working?

As long as the save file doesn't get corrupted, simply uninstalling (along with electing to keep the save files) and reinstalling the game seems like a manageable workaround for the time being. I understand that it's far from ideal. With that said, the game uninstalls and reinstalls quickly and this does much to make it bearable.

Update #1

Replacing the Unsetup.exe file resulted in an immediate 'Built with UDK has stopped working'.

Update #2

This will be the second time uninstalling and reinstalling the game since the new patch. Running the game immediately after patching works fine, however closing the programme and then trying to run it again has twice resulted in the 'Built with UDK has stopped working' error.

Update #3

A third uninstall and reinstall is now necessary. For some reason, the new patch results in a 'Built with UDK has stopped working' error when the programme is started after the first time the programme is patched. In other words, installing the patch and running the programme sees no error. It is not until the game client is closed and opened again, the second 'start up' after the latest patch, that the 'Built with UDK has stopped working' error resurfaces.

Hopefully this information is helpful.

For my part, I am going to roll back to the previous patch since that did not seem to have this issue. I'm glad that I save each game patch, just in case. If possible, please offer the previous patch to to GOGers and others so that they can continue to enjoy the game. (And, for that matter, Attention GOG: it would be FANTASTIC if previous patches/versions of the games on GOG were available for us!) It seems like the last patch was solid or at least did not come with this particular set of issues.

Update #4

Rolling back to the previous patch (v.1.1.13E AKA Cookiecrumb; GOG patch 2.0.1.7) works. Until the 'Built with UDK has stopped working' error is resolved, or at least its presentation in the current patch is handled, I'll be playing on that last patch.

Joe, please provide folks with a link to the aforementioned patch so they can keep playing while the issue is worked on since the Cookiecrumb patch really does seem to be stable.

GOG, please look into keeping previous versions of patches/installers readily available on the Games page so that when things like this happen players can easily roll back to a stable version, continuing to enjoy the game while allowing developers the chance to work on fixes without players frothing at the mouth.

I had the problem with the new patch, as described by raklar. The Unsetup.exe file you linked has it working properly again for me. Tried it a few times to make sure it was working. Thanks.

Dunno if this matters but I bought the vanilla version a good while back and played it a bunch, updated to the first patch and played it a bunch, and then installed this last update.

I can now conform that the Unsetup.exe file in Joe's link works for me as well, testing it three times by opening and closing the programme to see if the error would manifest. It didn't. I'm not sure why it didn't work for me the first time, but I'll chalk that up to some error on my part.

Now I can once again enjoy all of my hard-earned Exploding Robot Coins (TM) being sucked out of my pockets and moving in super slow-motion. XD

Indeed, my install had stopped working again after the latest update, though not initially. It worked and then upon later start up produced the error again.

Replacing UnSetup.exe with the one from that zip file seems to have fixed it.

I tried this and the game worked only once. But when I quit and relaunched the game again, the error came back. Is there another solution to this problem?

Update: I tried blankslatejoe's solution of replacing the UnSetup.exe file with the one from the zip file and that seemed to fix the problem.

The file did it for me! Works perfectly now.

I was sad after the update. Now I am very happy! Best FPS in many years!