Jump to content

Windows 10 / Play Anywhere - Closes on Start Up


Recommended Posts

  • Replies 339
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

This is not about this topic but I’ve got an idea about something you could do for the dlc extinction. Instead of having canteens water bottles and skins you could have a uncommon chance to find a wat

If you search for ARK in Add or Remove Programs, then select 'Advanced,' you'll see a list of add-ons. Just select one of them, and hit uninstall and then head to the store again, to reinstall it. 

Can confirm that installing scorched earth allowed my game to launch fully

Posted Images

So yeah this (Crash to desktop from splash screen) has been happening to me quite often recently. The only thing that works is to delete Scorched earth and then re download it but that's a 5 gb download every few days to play on a dedicated server for a couple of hours. It seems to act up after I play games on steam also the xbox live app on windows won't let me sign out when ever ark is acting up not sure if these are related but once I see one problem I know the other is there. Any info on a fix or an update would be amazing.

Link to post
Share on other sites

Yep, just started getting this with the last ark update, before it was fine, my server would run days without issue, now after 1 day or so it will crash and fail to launch until i download a random app from the store again. Every time i try to launch the game these two events are generated via windows event viewer:

@Jatheish

 

Event viewer related to DCOM and client-licensing

Client-Licensing
Log Name:      Microsoft-Client-Licensing-Platform/Admin
Source:        Microsoft-Client-Licensing-Platform
Date:          3/8/2018 7:01:41 PM
Event ID:      110
Task Category: None
Level:         Error
Keywords:      Service Keyword
User:          SYSTEM
Computer:     
Description:
License install failed for license type: 3
Result code: 0xC03F6603
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Client-Licensing-Platform" Guid="{B6CC0D55-9ECC-49A8-B929-2B9022426F2A}" />
    <EventID>110</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000001</Keywords>
    <TimeCreated SystemTime="2018-03-09T00:01:41.614865200Z" />
    <EventRecordID>2680</EventRecordID>
    <Correlation />
    <Execution ProcessID="6296" ThreadID="848" />
    <Channel>Microsoft-Client-Licensing-Platform/Admin</Channel>
    <Computer>ITX-PC</Computer>
    <Security UserID="" />
  </System>
  <EventData>
    <Data Name="Type">3</Data>
    <Data Name="HRESULT">3225380355</Data>
  </EventData>
</Event>
 
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          3/8/2018 7:01:41 PM
Event ID:      10001
Task Category: None
Level:         Error
Keywords:      Classic
User:         
Computer:     
Description:
Unable to start a DCOM Server: StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38!AppARKSurvivalEvolved as Unavailable/Unavailable. The error:
"317"
Happened while starting this command:
"C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe" -ServerName:AppARKSurvivalEvolved.AppX8dqae3jbqbp71qzw0jv2man0p45gr0c6.mca
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2018-03-09T00:01:41.614822100Z" />
    <EventRecordID>3422</EventRecordID>
    <Correlation />
    <Execution ProcessID="668" ThreadID="8580" />
    <Channel>System</Channel>
    <Computer></Computer>
    <Security UserID="" />
  </System>
  <EventData>
    <Data Name="param1">"C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe" -ServerName:AppARKSurvivalEvolved.AppX8dqae3jbqbp71qzw0jv2man0p45gr0c6.mca</Data>
    <Data Name="param2">317</Data>
    <Data Name="param3">StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38!AppARKSurvivalEvolved</Data>
    <Data Name="param4">Unavailable</Data>
    <Data Name="param5">Unavailable</Data>
  </EventData>
</Event>
Edited by Juggernaut
Link to post
Share on other sites
5 hours ago, Juggernaut said:

Yep, just started getting this with the last ark update, before it was fine, my server would run days without issue, now after 1 day or so it will crash and fail to launch until i download a random app from the store again. Every time i try to launch the game these two events are generated via windows event viewer:

@Jatheish

 

Event viewer related to DCOM and client-licensing

Client-Licensing
Log Name:      Microsoft-Client-Licensing-Platform/Admin
Source:        Microsoft-Client-Licensing-Platform
Date:          3/8/2018 7:01:41 PM
Event ID:      110
Task Category: None
Level:         Error
Keywords:      Service Keyword
User:          SYSTEM
Computer:     
Description:
License install failed for license type: 3
Result code: 0xC03F6603
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Client-Licensing-Platform" Guid="{B6CC0D55-9ECC-49A8-B929-2B9022426F2A}" />
    <EventID>110</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000001</Keywords>
    <TimeCreated SystemTime="2018-03-09T00:01:41.614865200Z" />
    <EventRecordID>2680</EventRecordID>
    <Correlation />
    <Execution ProcessID="6296" ThreadID="848" />
    <Channel>Microsoft-Client-Licensing-Platform/Admin</Channel>
    <Computer>ITX-PC</Computer>
    <Security UserID="" />
  </System>
  <EventData>
    <Data Name="Type">3</Data>
    <Data Name="HRESULT">3225380355</Data>
  </EventData>
</Event>
 
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          3/8/2018 7:01:41 PM
Event ID:      10001
Task Category: None
Level:         Error
Keywords:      Classic
User:         
Computer:     
Description:
Unable to start a DCOM Server: StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38!AppARKSurvivalEvolved as Unavailable/Unavailable. The error:
"317"
Happened while starting this command:
"C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe" -ServerName:AppARKSurvivalEvolved.AppX8dqae3jbqbp71qzw0jv2man0p45gr0c6.mca
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="0">10001</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2018-03-09T00:01:41.614822100Z" />
    <EventRecordID>3422</EventRecordID>
    <Correlation />
    <Execution ProcessID="668" ThreadID="8580" />
    <Channel>System</Channel>
    <Computer></Computer>
    <Security UserID="" />
  </System>
  <EventData>
    <Data Name="param1">"C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe" -ServerName:AppARKSurvivalEvolved.AppX8dqae3jbqbp71qzw0jv2man0p45gr0c6.mca</Data>
    <Data Name="param2">317</Data>
    <Data Name="param3">StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38!AppARKSurvivalEvolved</Data>
    <Data Name="param4">Unavailable</Data>
    <Data Name="param5">Unavailable</Data>
  </EventData>
</Event>

Same exact experience here. Even getting the same errors in my event log. 

It is embarrassing on Microsoft for letting this pass certification, and even more embarrassing on Wildcard for being so lazy about this. Honestly, all I want to do is host a server for my xbox friends to play on. The fact this can't be done with a small service based client is infuriating.

Link to post
Share on other sites

So it looks like Microsoft pushed a windows store update for the "xbox identity program" app yesterday which is supposedly used "to connect pc to xbox live services" and is a new app in probably the last week. Well their latest update for the app has seem to solve the DCOM/Client license issue as I don't get that event issue anymore for now but I am getting a new error now that is causing the game to crash. I am reinstalling the game to see if it fixes the error below

Faulting application name: ShooterGame.exe, version: 0.0.0.0, time stamp: 0x5a8da967
Faulting module name: ntdll.dll, version: 10.0.16299.192, time stamp: 0x6dead514
Exception code: 0xc0000005
Fault offset: 0x000000000001cebe
Faulting process id: 0x2894
Faulting application start time: 0x01d3b8708ececc00
Faulting application path: C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: eaeadfb2-898e-44e8-afc3-3653947291d8
Faulting package full name: StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38
Faulting package-relative application ID: AppARKSurvivalEvolved

Edited by Juggernaut
Link to post
Share on other sites
38 minutes ago, Juggernaut said:

So it looks like Microsoft pushed a windows store update for the "xbox identity program" app yesterday which is supposedly used "to connect pc to xbox live services" and is a new app in probably the last week. Well their latest update for the app has seem to solve the DCOM/Client license issue as I don't get that event issue anymore for now but I am getting a new error now that is causing the game to crash. I am reinstalling the game to see if it fixes the error below

Faulting application name: ShooterGame.exe, version: 0.0.0.0, time stamp: 0x5a8da967
Faulting module name: ntdll.dll, version: 10.0.16299.192, time stamp: 0x6dead514
Exception code: 0xc0000005
Fault offset: 0x000000000001cebe
Faulting process id: 0x2894
Faulting application start time: 0x01d3b8708ececc00
Faulting application path: C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: eaeadfb2-898e-44e8-afc3-3653947291d8
Faulting package full name: StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38
Faulting package-relative application ID: AppARKSurvivalEvolved

And it doesn't stop this error either, when trying to run the game twice on two accounts on same computer.

Unable to start a DCOM Server: StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38!AppARKSurvivalEvolved as Unavailable/Unavailable. The error:
"3236560897"
Happened while starting this command:
"C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe" -ServerName:AppARKSurvivalEvolved.AppX8dqae3jbqbp71qzw0jv2man0p45gr0c6.mca

Link to post
Share on other sites
54 minutes ago, CyberAngel67 said:

And it doesn't stop this error either, when trying to run the game twice on two accounts on same computer.

Unable to start a DCOM Server: StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38!AppARKSurvivalEvolved as Unavailable/Unavailable. The error:
"3236560897"
Happened while starting this command:
"C:\Program Files\WindowsApps\StudioWildcard.4558480580BB9_1.7.771.2_x64__1w2mm55455e38\ShooterGame\Binaries\UWP64\ShooterGame.exe" -ServerName:AppARKSurvivalEvolved.AppX8dqae3jbqbp71qzw0jv2man0p45gr0c6.mca

Yeah still happening, even after re-install. Something broke in the last update, wasn't an issue before. I even gave DCOM services and the associated services that rely on DCOM/licensing set to automatic startup but still having issues.

Edited by Juggernaut
Link to post
Share on other sites
1 hour ago, Juggernaut said:

Yeah still happening, even after re-install. Something broke in the last update, wasn't an issue before. I even gave DCOM services and the associated services that rely on DCOM/licensing set to automatic startup but still having issues.

I think this error is different, but related some how. The only reason I say that is because it used to work, I also have no issue with the game running at all on Windows 10. Only have an issue when I try to run it twice from two different accounts on the same computer.

Which worked for about 10 days after the game was released, since then something updated and it no longer works.

I have reached out to Microsoft, as a developer I have been asking on all the forums with peers and they are basically saying that the App failing is Wildcards problem.

Link to post
Share on other sites
7 hours ago, CyberAngel67 said:

I think this error is different, but related some how. The only reason I say that is because it used to work, I also have no issue with the game running at all on Windows 10. Only have an issue when I try to run it twice from two different accounts on the same computer.

Which worked for about 10 days after the game was released, since then something updated and it no longer works.

I have reached out to Microsoft, as a developer I have been asking on all the forums with peers and they are basically saying that the App failing is Wildcards problem.

This post here https://answers.microsoft.com/en-us/windows/forum/windows_10-security/xbl-clientserver-ipsec-issuing-ca-suspicious/e5038157-7fa4-491a-8c8b-0824ac82e456

is basically the reason. Microsoft certificate is only good for 1 day, My event ID is 64 which is for about to expire certificate which makes sense given my server will crash after only 1 day now. I tried to renew it manually but it didn't work. Makes sense why downloading another app temporarily fixes it because it renews that way but only for 1 day. 

Link to post
Share on other sites
31 minutes ago, IAmBullet said:

i have found a solution, i know this is late but it worked for me. all you need to do is start the install of any dlc, then click on ark and it shouldn't crash when you do. hope this helps.

Yeah if you read this thread, you will find that many have done or tried that and it works for a little while and then stops again. For some others it didn't work at all.

Link to post
Share on other sites

I was going to make a powershell script that launches on reboot, installs a random free app, launches ark and then uninstall the random free app. This might be a good temp fix for now. Then just schedule server reboot time for 5-10 min once a day in the early morning. Not ideal but better then having to check ark server everyday to see if it's crashed.

Edited by xspyboyx
Link to post
Share on other sites

According to some of the posts @Jen made on reddit this morning, Wildcard focuses on exploits and critical issues before even thinking about other bugs. So the fact that they haven't said anything about this thread that has been at the top of forum topic for several days now only goes to show that not being able to run the game isn't a critical issue.

 

As a developer I understand prioritization of bugs and fixing them, but this kind of crap is mind boggling. I miss the days when people strove for excellence, where they knew what needed to be done and did it rather than made excuses about it.

Link to post
Share on other sites
3 minutes ago, DeadlyNancy said:

According to some of the posts @Jen made on reddit this morning, Wildcard focuses on exploits and critical issues before even thinking about other bugs. So the fact that they haven't said anything about this thread that has been at the top of forum topic for several days now only goes to show that not being able to run the game isn't a critical issue.

 

As a developer I understand prioritization of bugs and fixing them, but this kind of crap is mind boggling. I miss the days when people strove for excellence, where they knew what needed to be done and did it rather than made excuses about it.

As a developer myself, it would be foolish for any developer to ignore exploits and critical issues. The only problem is that seems to be ignored half the time as well, especially during the time they where developing Scorched Earth and Aberration, we have legacy servers because of exploits, that Wildcard ignored for how long? Then segregated their servers in the hope that it would solve the problem of them ignoring it for so long, only find out that this didn't fix what they had hoped for it to fix.

But all things aside, it doesn't take every single developer they have to work on exploits. I know they are focusing on improving that side of the equation, but come on, every developer on one problem is not something they should be admitting too.

Link to post
Share on other sites
1 hour ago, Jesse said:

POTENTIAL FIX! If you are still experiencing issues with Win10 version closing on launch, we have some evidence that the problem is fixed in Windows Insider Builds (source: I had the problem > Microsoft mentioned it might be fixed in Insider > I installed Windows Insider Slow Ring > Problem went away). 

If any of you are brave enough to sign up for Windows Insider and give the latest builds a try, please let us know if the problem is resolved for you. If you continue to have the problem, let us know that, too. Thanks!

Jesse, do you know if this also fixes the issue with running the game twice on the same machine under two accounts?

I am in the Insider Program, slow Ring, but not on the machine that I play Ark on and the machine that is, isn't capable of running the game.

But I do have to question, why MS have not released this as an update as yet for current release of Windows. The next update for Windows is not for about 6 months and I don't see people being that patient for a major Windows update to play the game.

Link to post
Share on other sites
2 hours ago, Jesse said:

POTENTIAL FIX! If you are still experiencing issues with Win10 version closing on launch, we have some evidence that the problem is fixed in Windows Insider Builds (source: I had the problem > Microsoft mentioned it might be fixed in Insider > I installed Windows Insider Slow Ring > Problem went away). 

If any of you are brave enough to sign up for Windows Insider and give the latest builds a try, please let us know if the problem is resolved for you. If you continue to have the problem, let us know that, too. Thanks!

did everything you said, with the slow ring and all, but it still crashes on launch :(

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...