Can no longer play Grim Dawn: Windows 10016 error

Windows 10 SUCKS BALLS.

So I got a 10016 error a couple months after installing GD on this new rig. Game worked FLAWLESSLY before this started happening. So I looked up the error code, and found a registry fix. It seemed that the error stemmed from permissions not being afforded to the Administrator (my account).

I changed the ownership to my account name in the corresponding CLSID / AppID, changed permissions to ALLOW in both, and restarted GD. Game once again worked great…for ONE DAY.

Now, no matter WHAT permissions I set for the CLSID or AppID for this event (I tried reverting back to the previous settings, and even went back to last known good config), GD locks up when I start the game now, forcing me to either sign off, or restart my rig.

I hope I’m not screwed out of playing this game ever again. ALL OTHER STEAM GAMES WORK, except THIS one! :furious::furious::furious::furious:

ANYONE with a bit of WinBLOWS 10™ savvy able to help??!

Only just got a Win10 machine and no problems for me. Have you tried verifying the game files? Also have you tried right clicking on the game’s desktop icon, going down to Properties and then into Compatibility and setting run as Administrator there?

Windows 10 has always had permissions issues and for whatever reason the issue has had a bone to pick with GD particularly among players. I have no idea if it’s Windows fault or GD’s or just a combination of both because even tho I’ve noticed a rather higher bit of occurrences with GD this is by no means implying that other games and programs haven’t run in to very similar problems. A bit of searching around reveals that GD isn’t totally alone in this, even if it seems that more users experience it. I’ve always found permissions settings to be overly confusing to come to grasp with in OS’es (Linux included), but still, perhaps Google may provide you some relief.

Maybe try some of the tricks from a quick search, like so:
https://www.google.com/search?q=how+to+fix+windows+10+permissions+issues

If worse comes to worse and absolutely nothing seems to work you may consider doing a complete, fresh reinstall of 10 which, in my experience, often fixes these kinds of problems. And set OneDrive not to start with Win10 login immediately after a fresh install, literally before you do anything else. It can cause permissions issues in Win10 with GD since it likes to (automatically) include GD’s documents save folder in to itself which I am sure is part of the problem.

I have reinstalled the OS without OneDrive 4 times now. I have tried to set full permissions WITH INHERITANCE for ALL accounts since the error likes to bounce throughout each account object involved (Desktop users, admin (me), etc). I build my wife’s rig EXACTLY down tot he last component and OS to mine, and she has ZERO problems.

And it’s NOT just Windows 10. I had this bs happening with Windows 7-64 Ultimate as well as Windows 8.

GD is just plain shite when it comes to DCOM permissions, and it comes down to the game’s behavior during play. GD initiates a DCOM request:

When you start the game.

When you log into a character.

Various timed intervals during single player (usually 10-minute intervals).

When you host a game, then log out.

Whenb you JOIN a hosted game, then log out.

When you hang out too long in the join multiplayer menu (internet).

The link you provided only leads to a tutorial on how to obtain ownership of the security permissions of a file folder. It does NOT in any way show how to troubleshoot why even THAT would fail to work.

Next game, Crate, try making sure that your game can run without having to ask for permission every 10 minutes.

I ALWAYS do those things first. Before firing GD up after a fresh install of the game on a new rig, I always set run as admin.

Interesting that noone not running 10 has reported permissions issues that I’ve seen in all this time.

Furthermore, I’ve ran it on 7 and 8 and 8.1 and never had a permissions issue. Only with 10 have I seen a few instances upon reinstalls (along with all the numerous reported instances of issues).

Don’t know why you’re getting all shitty tho. We’re only trying to help.

Not seeing what it matters how many times it asks as long as it makes it past any initial query. Never heard of the game just stopping because of a permission request in the middle of a game. And did you ever consider that it’s Windows triggering the request in response to whatever the game needs to do? Such as: reading and writing of files to disk, communicating with various ports etc… all types of activities Windows would be “in control” of.

I’m assuming your problem is that you can’t even get in to play, perhaps try to stay focused on that count rather than blow it up in to every time it makes a request well after the fact.

Sent from my SM-J727P using Tapatalk

Just a thought, as i could not run GD in an earlier version of win 10 until i did this. Do not worry about setting GD to run as admin through the desktop icon, instead set the GD exe in the install directory to run as admin.

Sounds dumb but, it has worked for me and a few other people. Might as well try it out. :undecided:

Edit: Quick edit. After looking through Google results, this looks like a Windows issue and has nothing to do with GD as far as i can tell.

certainly not a bad idea, but why would Windows answer the same request differently the second or third (or fourth) time GD asks ?

The fact that Windows answers ‘wrong’ is still a Windows problem, that GD asks more often than maybe necessary (no idea if it does) ‘only’ makes it more likely to fall victim to this Windows issue, it is not the source of the problem as far as I understand your explanation

For what it is worth (not much, I know) I never had these issues and have been playing GD a few hours on Win 10 by now

A SHITE game that doesn’t work without 978364987362487634876 DCOM errors when you so much as exit to main menu.

GG.

or maybe it is just a shite windows install, because you are pretty much the only one affected ?