.

[~Ash ☆~]

.

[Just Some Guy]

Because 1. Windows 8 is a joke and 2. I doubt it's windows 8's fault.

[Just Some Guy]

Originally posted by Haduken™:

Problably is... ;p and yeah i know win 8 is a joke

You can try running the executable in compatibility mode for windows 7.

[krashd]

The game doesn't work for me on Windows 10 so I doubt it's your windows version, my game went from working to broken with the move to Steamworks.

[Just Some Guy]

Originally posted by krashd:

The game doesn't work for me on Windows 10 so I doubt it's your windows version, my game went from working to broken with the move to Steamworks.

Worked for me on win 10 though.

[Calmer Llama]

How to get this going on Windows 10 (and most likely Windows 8)
1. Right click on 'Dead Rising 2' in Steam and select 'Properties'
2. Click on the 'Local Files' tab
3. Click on the 'Browse Local Files ...' button
4. In the Windows Explorer window that opens, right click on 'deadrising2.exe' and select 'properties'
5. Click on the 'Compatibility' tab
6. Check the 'Run this program as an administrator' box at the bottom.
7. Click OK to close the 'properties' box, and close the 'explorer' and 'Dead Rising 2 Properties' boxes.

Game should now run.

[krashd]

Nope, exact same CTD again.

With one more of these error logs needing to be deleted...

Exception Handler

Build Info:
	Build 3221, Thu May 14, 2015 10:10:59 PM

Callstack:  
	Address     Function                                Location
	UNKNOWN     UNKNOWN                                 UNKNOWN
	UNKNOWN     UNKNOWN                                 UNKNOWN
	UNKNOWN     UNKNOWN                                 UNKNOWN

Exception: Access Violation (00A2EA25)
	>UNKNOWN LOCATION

Memory:
	Heap(0): C  352596 /  352596  W 4194303 / 4194303
	Heap(1): C    1049 /    1049  W 4194303 / 4194303
	Heap(2): C     127 /     127  W 4194303 / 4194303

[Calmer Llama]

Hmmm. I found this as well in Steam Discussions which is the same as what I did: https://steamcommunity.com/app/45740/discussions/0/617335934150411049/ in which WolfPup3 fixed his/her Windows 8.1 issue.

On that screen where you click 'Run this program as an administrator' there are other settings including running the game in Windows 8 Compatibility Mode. Perhaps that setting (or even choosing an earlier version of Windows) may resolve your issue but you'd have to test it out.

There's also a Compatibility Troubleshooter that can be run that might sort out settings to get it to work.

I've definitely run older programs like Red Faction: Guerilla (with its crappy GFWL in the past) using these settings so it may be worth a try.

Sorry my first suggestion didn't help.

[krashd]

Nah, any help is welcome, but I think there is a bug somewhere inside the new version of the game compiled since Steamworks was added because the game worked perfectly with no needed special settings when it was GFWL. Then they updated it and it broke, I've done absolutely everything to the game from compat-settings to deleting old settings files, deleting and redownloading the game folder, googling those memory errors in the crash file. I've tried running the game using emulators

It seems as though something inside the .exe, one of it's first calls or hooks is requesting something that it assumes to be there but isn't. If I knew what it was I could do it, but other than installing the directX version and VCdist that came with the game I am out of ideas.

EDIT: The one thing I think it might be (due to zdp and xlive.dll still being in the game download) is a misconfigured GFWL, but I am not going to be tinkering with GFWL for 2 reasons...

1.) Any time you tinker with it to fix one game another will develop problems and I have 3 or 4 other games, Bulletstorm, Earth at War, etc that work fine as long as GFWL is not touched.

2.) This game was moved to Steamworks, so GFWL should have been removed in it's entirety, not just pushed to the side and left running, so if the game still requires some level of GFWL to be there and thinks mine needs fiddling with then the game can politely "f... off" until someone realises you don't remove GFWL by in fact just leaving it in....

[Calmer Llama]

Um I was going to suggest https://pcgamingwiki.com/wiki/Dead_Rising_2 as a last site to check but going through the thread again ... I thought I should confirm that I am (as of this moment) running Dead Rising 2 on my Windows 10 x64 PC! For some inexplicable reason I thought you were also having trouble with Windows 8 (or 8.1)

The first post I did, definitely fixed my issue (which was that the game started but I couldnt interact with it). Checking Task Manager showed that it was running as a Process, not an Application. As soon as I switched it to run as Administrator it's worked fine!

So I think there's just a problem with either the install, or other component that the game requires on your PC.

Happy to provide more info if you need it.

[Calmer Llama]

Update: My PC was freshly rebuilt in March this year and I do NOT have any bits of GFWL on it. Install was from a backup made in March 2016 and no patches were required after install.