Settlers New Allies crashing and won't start


Recommended Posts

When launching Settlers New Allies (via Ubisoft Connect) it won't launch.

The splash screen sometimes appears, then a 'black' The Settlers window and that it crashes/vanishes.

Do you guys also experience this? I have submitted a request at Ubisoft, but they are (as it looks like) very busy and not responding.

I also uninstalled Settlers New Allies, deleted the cache, restarted my computer, updated to latest nvidia drivers and Windows Update etc etc.
It's a Windows 11 24H2 machine (see sig)

 

image.png.b436fd510fbb6be8343ae962e13d7b16.png

image.thumb.png.1fbddf7ffdfdd35205c7e6571910e0bc.png

On 28/02/2025 at 17:33, Schabang said:

Register here just so i can say that you are not alone.
Not what you want to hear but i have the exact same thing happening to me.

Sent reports and sent question about it to Ubisoft two days ago.

I don't see a link with 'register here' in your post. Am I correct?

Update:
With KB5051987 reinstalled Settlers not working and launching.

So apparently it has something to do with the Microsoft's update.... any ideas if this will be fixed in the March "patch Tuesday", because I don't really like an unpatched W11 24H2.

On 01/03/2025 at 03:59, kiddingguy said:

Interestingly to see that Windows Update is now downloading KB5051987 (and thus skipping 5050094).

Hopefully Settlers is playable after installing this 5051987 update. Otherwise, I know where to look...

It’s not all that interesting. That what happens when an update is superseded by another update.

KB5051987 is from February. You should be installing KB5053598 if you want to keep your system updated.

Apparently your post was from February. My apologies. KB5053598 would have superseded KB5051987

On 12/03/2025 at 06:00, TheGhostPhantom said:

It’s not all that interesting. That what happens when an update is superseded by another update.

KB5051987 is from February. You should be installing KB5053598 if you want to keep your system updated.

Apparently your post was from February. My apologies. KB5053598 would have superseded KB5051987

I have installed KB5053598.

However, not uninstalled the previous (previews) KB-updates (e.g. KB5052093). But since these are cummulative... does that really matter?

On 12/03/2025 at 02:20, kiddingguy said:

I have installed KB5053598.

However, not uninstalled the previous (previews) KB-updates (e.g. KB5052093). But since these are cumuulative... does that really matter?

KB5052093 was a Preview cumulative update. I would revert to KB5051987 rather than stay on KB5052093. Since there are problems with KB5051987 I would then rollback to KB5050009. It's very likely problem is with Ubisoft's software not necessarily at fault of Microsoft's patch.

Reverting and restoring to previous KB-updates led to an unusable and corrupt Windows :angry: [the all-known BSOD when booting]

I had to reinstall everything. But even with the new installation set, and all current monthly updates... no playable The Settlers: New Allies.

And still a crash, and crash report to be sent.

On 3/13/2025 at 4:23 PM, kiddingguy said:

Reverting and restoring to previous KB-updates led to an unusable and corrupt Windows :angry: [the all-known BSOD when booting]

I had to reinstall everything. But even with the new installation set, and all current monthly updates... no playable The Settlers: New Allies.

And still a crash, and crash report to be sent.   

KB5052093 was a Preview cumulative update. I would revert to KB5051987 rather than stay on KB5052093. Since there are problems with KB5051987 I would then rollback to KB5050009. It's very likely problem is with Ubisoft's software not necessarily at fault of Microsoft's patch to play here

It might be a good idea to temporarily disable Windows updates and test it again. If the game runs smoothly on earlier updates, then the issue is likely related to the recent Microsoft patches

  • 3 weeks later...
On 08/04/2025 at 18:45, kiddingguy said:

Nope. Not even with the latest KB5055523 April Patch Update installed.

Dunno if someone has mentioned this before but have you tried it on windows 10. I had an issue with star wars outlaws and installed Windows 10 on a separate partition until they fixed it. 

On 08/04/2025 at 19:58, Som said:

Dunno if someone has mentioned this before but have you tried it on windows 10. I had an issue with star wars outlaws and installed Windows 10 on a separate partition until they fixed it. 

It DID run on Windows 11 24H2 before the January KB5050094 update earlier this year [see also above]. So technically up until end of January 2025, and thus also 2024 and earlier.

All other updates after that didn't make the game work again.
I have no W10 machine to try it on.

On 08/04/2025 at 19:02, kiddingguy said:

 

All other updates after that didn't make the game work again.
I have no W10 machine to try it on.

You don't need another machine, partition around 20 gigs on your current machine, install windows 10, or an early version of windows 11 there. It really is quite simple.. you can keep your current os for everything else

On 08/04/2025 at 20:24, Som said:

You don't need another machine, partition around 20 gigs on your current machine, install windows 10, or an early version of windows 11 there. It really is quite simple.. you can keep your current os for everything else

Like I said… it did work. I even uninstalled these KB’s and got it working again.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Yes, it was amusing at the time because even then dbrand was well known for stealing the designs of products from other companies. That’s what they do.
    • Didn’t Dbrand once complain that Casetify was ripping off their designs a well? seems pretty bad of them to try and get around Valve’s copyright this way with that in mind.
    • Dbrand thought they could get away with this Steam Machine case, Valve disagreed by David Uzondu Image via Dbrand Dbrand has cancelled its highly anticipated Companion Cube enclosure for the Valve Steam Machine, which it teased back in November of last year with a concept render and sign-up page, because it did not ask Valve for permission first before manufacturing the case. According to Dbrand, it took the "backwards approach" of building the product first before asking for permission from the copyright holder. Seven months of work went into the project, requiring over a thousand engineering hours from the design team. Workers developed forty-four sets of injection molding tools, making a unique mold for each sub-component of the crate. When the Companion Cube went live on Monday last week, it, according to Dbrand, quickly became the second-fastest-selling product in the company's fifteen-year history, racking up orders for hundreds of thousands of units. Customers eagerly bought the $129.95 deluxe edition or the bare-bones $99.95 version, which the manufacturer cheekily branded as the "Poverty Cube". It was around this time that the legal eagles at Valve descended on the accessory maker with a formal demand. The developer pointed out that the iconic block design remains protected intellectual property from the game Portal, so unlicensed sales had to stop. Dbrand said that all its pleas to salvage the project with the Valve team, including proposals to run a properly licensed release under official terms "with their blessing", fell on deaf ears, so it had no choice but to obey and remove every trace of the product from the internet. If you bought the enclosure, the company said that banks will process your refund by the end of this week, but if it still hasn't arrived in your account by then, you should not hesitate to contact support. The Steam Machine itself is a high-performance console that Valve designed directly to bring PC gaming into the living room. It was announced on 12th November 2025 (the same day Dbrand announced the Cube) and runs on the Linux-based SteamOS, the same OS that powers the Steam Deck. As for the price, due to the shortage of memory and storage chips, the hardware cost landed much higher than people were expecting, starting at $1,049 for the 512 model (without a controller) or $1,128 with the new gamepad. The premium 2 TB model pushes those prices even higher, selling at $1,349 for the standalone console and hitting $1,428 if you want the bundle.
  • Recent Achievements

    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      534
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      97
    5. 5
      macoman
      57
  • Tell a friend

    Love Neowin? Tell a friend!