Some games not launching with builds 20257 and 20262

Anonymous
2020-11-19T16:15:42+00:00

Since build 20257, the Assassin's Creed Origins, Assassin's Creed Odyssey and Assassin's Creed Valhalla games are no longer launched. I was hoping that build 20262 would fix the problem, but it doesn't. So I have to go back to build 20251 for these games to work.

Windows Insider program | Apps on Insider preview

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

68 answers

Sort by: Oldest
  1. Anonymous
    2020-12-20T18:34:53+00:00

    Over a month later and games are still crashing.

    We are not getting much information from Microsoft - if any at all.

    Immortals Fenyx Rising will also not launch for me.

    We're working on a fix for a future flight. Appreciate your patience.

    -Eddie

    Was this answer helpful?

    0 comments No comments
  2. CrazyKats 19,680 Reputation points Volunteer Moderator
    2020-12-24T14:21:31+00:00

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2020-12-27T18:06:12+00:00

    I'm on an AMD build, with Nvidia graphics and zero intel components including the network card. I'm having this issue on the latest windows insider build. I thought it was my new computer until I realized that windows insider was the issue. It took googling "windows insider vahalla crash to desktop" for this to come up and I'm glad I did.

    It does not seem like common knowledge on the Ubisoft forums or steam community forums. Would be nice if Microsoft at least gave people a list of confirmed known problems with applications, suspect/reported problems with applications and finally also show those known and potential warnings on launch of the application in some way. The amount of time wasted is not something I plan on going through again and now you've lost valuable feedback from a tester because you don't have the infrastructure in place to support having the public be beta testers for your products. The lack of replies and attention to reported issues is also pretty concerning.

    For me, once WSL2 CUDA comes out, I'm done with windows insider. Between this and the chkdsk /f issue, bug in the alt tab behavior and I'm seriously concerned about the QA that Windows now has in place. One day I might have an update that not only corrupts data but also prevents me from logging in without reformatting. The chkdsk /f issue and alt-tab issues are in your latest non-insider builds - those plus other previous issues in the past all indicate you have major problems with this release cadence not causing issues in production.

    At some point enough paper cuts to enough people will erode trust in your brand. Circle the wagons and double up on how problems are reported. I also read - https://www.ghacks.net/2019/09/23/former-microsoft-employee-explains-why-bugs-in-windows-updates-increased/

    • that there use to be an internal Windows Test team - seems that removing them was a mistake. At the very least Microsoft should also comment about their current windows test process and improvements that will be made, it needs some major PR help as confidence is definitely eroding. Last thing you want is major PR nightmare before you then need to act to re-instill confidence in your brand and products.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2020-12-29T17:24:11+00:00

    Same issue, with AC Origins and Odyssey on 20279 https://aka.ms/AAapn2i

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2020-12-30T14:49:09+00:00

    Same issue with AC Valhalla on 21277.

    Was this answer helpful?

    0 comments No comments