My OS is windows 7, for the record.
I get this message: UnSetup has stopped working

Problem Event Name: CLR20r3
Problem Signature 01: unsetup.exe
Problem Signature 02: 1.0.4930.22560
Problem Signature 03: 51d176c6
Problem Signature 04: UnSetup
Problem Signature 05: 1.0.4930.22560
Problem Signature 06: 51d176c6
Problem Signature 07: 7d
Problem Signature 08: 2
Problem Signature 09: System.NullReferenceException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3082
Additional Information 1: 93c8
Additional Information 2: 93c8bc577a2e79004317b67fe5ba53ed
Additional Information 3: 4146
Additional Information 4: 41466260f4448cb65cf474a989021b17

And afterwards: BUILT WITH UDK has stopped working

Problem signature:
Problem Event Name: APPCRASH
Application Name: UDK.exe
Application Version: 1.0.10907.0
Application Timestamp: 51d1d22f
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdbdf
Exception Code: 00000001
Exception Offset: 0000b727
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 3082
Additional Information 1: 2071
Additional Information 2: 207100c5b69d5033590bed97a487b7ca
Additional Information 3: 22ac
Additional Information 4: 22aca4bed902ca918f5fa0d24d0efaa5

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

any ideas on what to do?

Yeah I have the same issue after a successful installation, on both a Lenovo Yoga 13 (Intel, 8GiB, Intel HD 4000) and a mongrel desktop PC (AMD, 16GiB RAM, Radeon HD7800 series). Both running Windows 8.1).

The only thing I tried was "Run As Administrator" which didn't help either, and updating my HD 4000 drivers.

I'm very sad it doesn't work :(

Hey guys,

Sorry to hear about the crashing. I'll do a bit of digging and see if I can figure this out. Are you guys both installing over previous installations, or are you both new users?

Thanks for picking up the game--hopefully we can figure this out!

Thanks Joe, new user. GOG offered me two downloads; I installed the "Windows installer" followed by the "Universal update (patch 1.13)" and then launched.

I just tried it on a new user account on my desktop system, still got the same crash.

Myself and user "priestlyjudas" are also having this problem. In my case, it's with a fresh install (install game, install udate, run game, get error). I did not try running the game before installing the update though.

I just installed this game for the first time, followed by the update, and am having the same issue too. Windows 8.1, Nvidia GTX660.

I'm encoutering a similar issue with my laptop. I'm on Win 7 64, and I have an I5-3230M, 4g RAM and a GeForce 710 M.
After installing the game for the first time, I tried to patch it put the patching failed. I redownloaded the patch, reinstalled the game, reapplied the patch, and this time the update was successful.
Then, upon lauching the game (for the first time) I see the "Tower of Guns" loading picture in the middle of my desktop, and suddenly "UNSetup has stopped working", followed by "BUILT BY UDK has stopped working".

Thanks a lot to you and your team, blankslatejoe, if you're already working on a fix.

Edit: I get the CLR20r3 error message just like the others.

A workaround- I reinstalled the game and ran it before applying the update. It's working now.

I can confirm this, game crashed at first, had installed + patched. Uninstalled, re-installed and ran the game. It went to the menu, so I quit, and applied the patch, and it's working now.

Same problem. Installed game. Applied patch. Game will not start.


Uninstalled. Re-Installed game. Opened game. Exited game. Patched game. Went back into game. I can confirm this is a work around for the problem.

Works here too, the unpatched version launches. Then quit, then patch, and it launches the patched version.

Thanks!

Huh..well, I'm glad you guys found a workaround.. Even though I *think* I know what the issue is, I'm still trying to figure out the best way to fix it.

I also have this issue on a new install.

Oh and .... AGGGGGHHHHH!

Error: Built with UDK has stopped working.

The above is the error I received when I first installed the game. It's important to note that I (1) installed the game and the new patch before running the game, (2) installed both under the Run as Administrator option and (3) installed both from the Downloads folder.

It seemed that it was a common enough problem and the only real information I found was here (http://steamcommunity.com/app/266110/discussions/0/558749190707849912/), demonstrating a potential issue with file integrity, Direct X and .Net. GOG support seems to prefer the possibility of GPU driver issues. I have yet to encounter a meaningful problem in PC gaming that is the result of out-dated GPU drivers, so I nixed the notion of getting new drivers for my GeForce MTX460 card. I also haven't had any issues with Direct X or .Net, as they're updated regularly, so I figured that it was either a bad install or Windows not liking to install from the Downloads folder...something that has, strangely, happened before.

I uninstalled Tower of Guns and moved both the installer and patch to my 'GoG Installers' folder and then installed just the game with the Run as Administrator option. The game loaded with no problems and I played until the 4th level where, at the boss, I fell through the floor. I didn't die, I was simply boosted back up into the boss room at the cost of a hell of a lot of health. The next run experienced no errors to speak of, so I installed the patch and went back to the game. That run encountered no errors.

To be clear, it seems that at least one potential solution to, at least, the 'Built with UDK has stopped working' error is to: (1) do not install from the Downloads folder, (2) install and run the base game, and (3) install the patch and then run the game. I am not sure whether or not it is necessary to do this in combination, if it is sufficient to simply not install from the Downloads folder or what not but the above three steps worked for me when I was unable to find a solution elsewhere.

Hopefully this is helpful.