Anyone else on 26H2 getting this?
I've had the same problem since last week, and have been unable to complete weeklies since then. It's very common on 26H2, more a server side issue, though it's probably not related to WMIC and the .NET 3.5 Framework being removed. If it was the anti-cheat, there would be an 0:85011S error right after it, or before it, as well.
There's a high chance it's associated with the way the game loads assets in the background and spawns entities, though I've noticed it has no correlation with texture quality, any other graphics setting, or even packet loss ( it doesn't look like a network issue. ) I logged back on to see that EA still doesn't have a fix, even after the reset, though there are probably not that many people with 26H2 to test this out.
This other error that can accompany it, doesn't show up now, though it was there when they had really high server load at the start of the event, yet none of my settings have changed since last week. It was more common during the Open Beta, though I wonder if it's kicking players because it can't spawn more entities: ERROR CODE DiceOnlineError_Unknown [223012S] P:829691231
Update: I rolled Windows back from 26H2 (26300.9711) to 25H2 (26200.9168) and I’m still getting 0:85009S
Update: I rolled Windows back from 26H2 (26300.9711) to 25H2 (26200.9168) and I’m still getting 0:85009S
I thought of doing that once, though I didn't try it, given that Microsoft changed the servicing stack in 24H2, so that any patch / cumulative update brings you to the same revision level as the newest versions of Windows 11 ( such as 26H2. ) Eventually anyone on 25H2 will encounter the same error after updating, though it's a staggered release, unless you use WUSA and the Microsoft Update Catalog to install it like I did.
DISM /Online /Get-CurrentEdition
Deployment Image Servicing and Management tool
Version: 10.0.26100.9549
Image Version: 10.0.26300.9725NOTE: If you go back to the RTM Image / ISO / Installation Media for 25H2, you won't have the MS Store updates ( for WinUI 2 / 3, or the 2023 UEFI secure boot update, which is baked into 26H2, ) so you won't be able to run the game properly either, and you might run into the 0:85009S error for another reason. If you try to roll back, you'll be forced to update, even if you're on 25H2, so you'll end up with the latest cumulative update and the secure boot update.
They don't explicitly describe this in the requirements, but EA Desktop itself uses WinUI 2 / 3 and Microsoft Edge WebView2 ( Webview2 .NET API ), aside from the game itself. They also separated the MS Store Updates from the cumulative updates. If you're missing the VC++ runtimes ( Visual C++ v14 Redistributable ), the .NET 8.0 / 10 Desktop Runtime, and Automatic Certificate Trust List (CTL) updates from Windows Update, it won't install properly. Smart App Control can also interfere with the installation as well. If you want broad compatibility with most games on Windows 11 and EA Desktop, especially older EA titles, you have to install / update the following MS Store Apps provided by Microsoft, though some of them are included with the operating system itself:
App Installer
Windows Application Compatibility Enhancements
WinAppRuntime.Singleton
WinAppRuntime.Main.1.8
WinUI 2 Gallery
WinUI 3 Gallery
Windows Community Toolkit Gallery
OpenCL, OpenGL, and Vulkan Compatibility Pack
Community ManagerThank you for your detailed and technical reply, much appreciated! EA_Barry.
