State of Decay: Year-One

State of Decay: Year-One

View Stats:
Rikimaru Nov 16, 2017 @ 5:42pm
'procedure entry point could not be located/KERNEL32.dll' + 'ULLaunch.exe App has stopped working'
Weird to think people are still having this problem, but here I am.

I just bought the game.
I just installed.
When I started it up, I get the 'ULLaunch Application has stopped working' error come up.

After searching for a fix, I tried the following...

Verify the integrity blah blah blah, didn't work.
'-fullscreen' and '-windowed' launch options, didn't work.
Ran in compatability mode, didn't work.

Run as administrator, didn't work.
In fact, it gives me another error before that one that says procedure entry point could not be located/KERNEL32.dll'.
Downloaded a KERNEL32.dll and placed it all around the SoD's local files, didn't work.

I never had this problem when I played the regular version and Breakdown DLC, on the same PC, a few years ago.

Any advice for a poor, lost, survivor?

Edit: I haven't been able to start up the game, but somehow I was given a Steam trading card from it while writing this.
Last edited by Rikimaru; Nov 16, 2017 @ 5:43pm
< >
Showing 1-11 of 11 comments
Undead Nicole Nov 17, 2017 @ 10:13am 
Completely uninstall it, and the folders for the game and then reinstall the game. Make sure you create a desktop shortcut from the game. restart Steam and then try running the game from your desktop shortcut.

If that doesn't work, go into the local files and run the vcredist again. (Or maybe try this first)
Rikimaru Nov 18, 2017 @ 6:47am 
Originally posted by Undead Nicole:
Completely uninstall it, and the folders for the game and then reinstall the game. Make sure you create a desktop shortcut from the game. restart Steam and then try running the game from your desktop shortcut.

If that doesn't work, go into the local files and run the vcredist again. (Or maybe try this first)

Oh, hey!
I didn't think you'd still be active.
I recognise your account from a forum post somewhere when I was looking for some advice.
Thank you for taking the time!

So.

Tried the 'repair' option on the vcredist. When it finished, I was told to restart.
Restarted PC, ran the game but it didn't work.

I uninstalled the game and deleted the whole SoD folder in the steamapps.
Reinstalled, restarted, ran from shortcut, but no dice.
This time, I didn't get the kernel32.dll error because it's not being ran as admin anymore.

Then I uninstalled and reinstalled the vcredist, tried to run again, but that didn't work either.

On a brighter note, my play time is up to 7 minutes! :D

Is there anything else I can try?
Should I try deleting all SoD entries in the 'regedit' program? I remember that had some entries for everything I've played. Could that interfere?
Last edited by Rikimaru; Nov 18, 2017 @ 6:47am
qmjs Nov 18, 2017 @ 7:25am 
Originally posted by Rikimaru Parks:
In fact, it gives me another error before that one that says procedure entry point could not be located/KERNEL32.dll'.
Downloaded a KERNEL32.dll and placed it all around the SoD's local files, didn't work.

What are the actual error messages you are getting (complete message)?

And remove those dlls. if they are not in the correct place in the operating system they won't work properly and can actually make the problems way worse.

That message isn't coming from the game, it is an operating system error happening when the game is trying to access OS functions, but without the full message it is impossible to say what is causing the issue. It could be drivers, directx, visual c runtimes, or maybe even something else.
Last edited by qmjs; Nov 18, 2017 @ 7:26am
Rikimaru Nov 18, 2017 @ 7:42am 
Originally posted by qmjs:
Originally posted by Rikimaru Parks:
In fact, it gives me another error before that one that says procedure entry point could not be located/KERNEL32.dll'.
Downloaded a KERNEL32.dll and placed it all around the SoD's local files, didn't work.

What are the actual error messages you are getting (complete message)?

And remove those dlls. if they are not in the correct place in the operating system they won't work properly and can actually make the problems way worse.

That message isn't coming from the game, it is an operating system error happening when the game is trying to access OS functions, but without the full message it is impossible to say what is causing the issue. It could be drivers, directx, visual c runtimes, or maybe even something else.

"ULLaunch Application has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available."

Only option on that window is to close program.

Right clicking on the StateOfDecay.exe, the file description says ULLaunch Application, which is probably why I can't even start it up.

Right now, that is the only error I'm getting and that's because I'm not running the program as admin. When I do run as admin, I get...

"The procedure entry point K32EnumProcessModules could not be located in the dynamic link library KERNEL32.dll."

Followed by the "ULLaunch Application has stopped working" error.

I've also been trying some other launch options too that change resolution and directx version but they didn't work.
I tried changing some options I saw people doing on the forums in the nvidia control panel with the same problem, but that didn't work either.
Last edited by Rikimaru; Nov 18, 2017 @ 7:42am
qmjs Nov 18, 2017 @ 7:54am 
What operating system are you using? That is due to it trying to call a specific function from on older, incompatible version of the software, and is probably due to the visual c runtimes.

Go to C:\Program Files (x86)\Steam\SteamApps\common\State of Decay YOSE\_CommonRedist\vcredist\2012

If you have a 64 bit OS, run vcredist_x64.exe, otherwise use the vcredist_x86.exe

Run it as an administrator, but don't install or remove, select the repair option.
Last edited by qmjs; Nov 18, 2017 @ 7:56am
Rikimaru Nov 18, 2017 @ 1:28pm 
Originally posted by qmjs:
What operating system are you using? That is due to it trying to call a specific function from on older, incompatible version of the software, and is probably due to the visual c runtimes.

Go to C:\Program Files (x86)\Steam\SteamApps\common\State of Decay YOSE\_CommonRedist\vcredist\2012

If you have a 64 bit OS, run vcredist_x64.exe, otherwise use the vcredist_x86.exe

Run it as an administrator, but don't install or remove, select the repair option.

Yeah, I've done this twice now! It doesn't work.

I'm using Windows Vista.
Like I said, this is the same computer I used when I played the same game a while ago when these problems didn't exist.

My "play" time is up to 15 minutes (of pure troubleshooting) and I haven't even made it to the intro videos!
qmjs Nov 18, 2017 @ 4:29pm 
That is the problem.

MINIMUM:
OS: Windows 7

The previous version would run on Vista, but YOSE requires at least Windows 7.



Last edited by qmjs; Nov 18, 2017 @ 4:30pm
Rikimaru Nov 19, 2017 @ 3:52am 
Originally posted by qmjs:
That is the problem.

MINIMUM:
OS: Windows 7

The previous version would run on Vista, but YOSE requires at least Windows 7.

But, I don't understand how unless there where big changes to the game.
From my understanding it's the base game with the dlc's.
Like I said, I've played the base game on the same system before, kinda sucks they made it unplayable for me.
I even think I used to own and be able to play Breakdown too with no problem, but didn't have the time.

If they have made some major changes then that means this is the second time a game has been "improved" and ended up unplayable for me and many others.

First it was APB Reloaded.
I BOUGHT the game before it was a free to play (still have the box and disk).
Then I played it after they went bankrupt and it went F2P.

After a few months, it was updated and a member of the family couldn't use their laptop.
Then it was further "improved" and then I wasn't able to play despite me having no technical or performance issues whatsoever.

Meanwhile, here's the first Age of Empires game, running with no hitches since 1997, about 2 decades after release.

Well anyway...
...this sucks.
cruinne Nov 19, 2017 @ 5:24am 
The updates to YOSE pushed up the minimum requirements, which is one of the reasons it's not just a "patch" but a different release - it no longer works on Vista and requires DirectX-capable video cards, too.

It feels sucky, I know, but Vista support at MS ceased in 2012. It's pretty out of date.
Undead Nicole Nov 20, 2017 @ 8:52am 
Originally posted by cruinne:
The updates to YOSE pushed up the minimum requirements, which is one of the reasons it's not just a "patch" but a different release - it no longer works on Vista and requires DirectX-capable video cards, too.

It feels sucky, I know, but Vista support at MS ceased in 2012. It's pretty out of date.
^^ What Cruinne said. I'm sorry, friend. You won't be able to play YOSE until you update to at least Win 7.
Rikimaru Nov 20, 2017 @ 9:54am 
Originally posted by cruinne:
The updates to YOSE pushed up the minimum requirements, which is one of the reasons it's not just a "patch" but a different release - it no longer works on Vista and requires DirectX-capable video cards, too.

It feels sucky, I know, but Vista support at MS ceased in 2012. It's pretty out of date.


Originally posted by Undead Nicole:
^^ What Cruinne said. I'm sorry, friend. You won't be able to play YOSE until you update to at least Win 7.

Ok, I guess I'll have to wait a while then.
Thanks for the replies!
I appreciate the help a lot. Thank you very much.
Last edited by Rikimaru; Nov 20, 2017 @ 9:55am
< >
Showing 1-11 of 11 comments
Per page: 1530 50

Date Posted: Nov 16, 2017 @ 5:42pm
Posts: 11