Jump to content


Disabling the launch of World of Tanks on pre-release versions of Windows 10?


  • Please log in to reply
41 replies to this topic

Catch21 #1 Posted Jul 23 2017 - 18:10

    Sergeant

  • Players
  • 29746 battles
  • 155
  • [DOG5] DOG5
  • Member since:
    05-19-2013

Can anyone confirm the above posted at the Russian Forum? (Translation: "Yesterday, in micro-patch 9.19.1.1, Wargaming implemented a very controversial decision: it disabled the launch of World of Tanks on pre-release versions of Windows 10.".

 

I've been posting and searching in vain for a fix to a "Windows ucrtbase.dll has wrong version" after trying to load the game (with Win 10 Build 16241) and crashing, including sending in a ticket with all required info.



Brick94 #2 Posted Jul 23 2017 - 18:23

    Captain

  • Players
  • 37590 battles
  • 1,537
  • Member since:
    08-03-2013
I haven't had any troubles with windows 10.  Not sure what you are experiencing, try upgrading windows 10.

Solustein #3 Posted Jul 23 2017 - 18:36

    Staff sergeant

  • Players
  • 11680 battles
  • 432
  • [F-3] F-3
  • Member since:
    02-14-2012
ive been running win10 since its release and never did i have an issue with WoT launching or running. 

caramel #4 Posted Jul 23 2017 - 18:43

    Major

  • Players
  • 7990 battles
  • 3,674
  • [MLPVA] MLPVA
  • Member since:
    05-11-2011
I've not been having any issues either and I use pre-release win 10.

GWyatt #5 Posted Jul 23 2017 - 19:13

    Corporal

  • -Players-
  • 1858 battles
  • 18
  • [VAN] VAN
  • Member since:
    11-23-2015
Are you talking about the creator (I think that is what it is called) that insiders are getting right now (public release sometime in the fall)?
 

Catch21 #6 Posted Jul 23 2017 - 19:17

    Sergeant

  • Players
  • 29746 battles
  • 155
  • [DOG5] DOG5
  • Member since:
    05-19-2013

View PostGWyatt, on Jul 23 2017 - 18:13, said:

Are you talking about the creator (I think that is what it is called) that insiders are getting right now (public release sometime in the fall)?
 

 

Yes, apologies should have been more specific, but Win 10 Build 16241 IS the Creator's++ Edition. And more generally the quote refers to ANYONE on the Insider Preview tracks, i.e. any non-production RTM version of Win 10.

phattai91 #7 Posted Jul 24 2017 - 01:48

    Private

  • -Players-
  • 0 battles
  • 1
  • Member since:
    02-26-2014
"Windows ucrtbase.dll has wrong version".... same problem here, after upgrading to "

pre-release versions" of windows 10:arta: i try to restore but it still fall when launching game, and only in WoT:(



black_colt #8 Posted Jul 24 2017 - 02:13

    Captain

  • -Players-
  • 3360 battles
  • 1,846
  • Member since:
    01-11-2015

View PostCatch21, on Jul 23 2017 - 09:10, said:

Can anyone confirm the above posted at the Russian Forum? (Translation: "Yesterday, in micro-patch 9.19.1.1, Wargaming implemented a very controversial decision: it disabled the launch of World of Tanks on pre-release versions of Windows 10.".

 

I've been posting and searching in vain for a fix to a "Windows ucrtbase.dll has wrong version" after trying to load the game (with Win 10 Build 16241) and crashing, including sending in a ticket with all required info.

 

Pre-release means that the APIs have not been finalized and are constantly moving. 

 

Do you seriously expect WarGaming to support their app on a system in which the APIs have not been finalized?  

 

There are reasons for Gold Masters - that tells the developer that this is the final code base for you to test against - otherwise the developer could be spending time trying to code for something that is not in the final release.

 

How is that controversial?  

 

You chose to install the Pre-release software and agreed to [This means that you may experience occasional crashes and data loss. To recover, you may have to reinstall your applications, the operating system, or re-flash your device.] which is in the Program Agreement - Windows Insider Program.

 

WarGaming owns the app and can set limits on how the app is used at anytime. However if they are limiting the app to certain systems then they should advise users of that in advance as a good practice.

 

Perhaps that version of the OS is not secure.  Do you want WarGaming to support you and when your private information is taken are you going to come back screaming at them - how can you release my private information?

 

So you took a gamble and installed an OS that is not available to the general public knowing that there may be issues and want the app provider to suddenly support you?  Support costs money - are you suggesting that WarGaming spend money supporting something that is constantly changing?

 

Just roll back to a the last publicly released version of MS Windows and play the game with that OS. 

 

Or do like I do on my Mac - install the pre-release in a different partition from the public release so you can try it out and if you have issues then boot back into the public release partition and keep playing.

 

 

 

 


Edited by black_colt, Jul 24 2017 - 02:39.


Mixai1l #9 Posted Jul 24 2017 - 19:04

    Corporal

  • -Players-
  • 6 battles
  • 13
  • Member since:
    07-24-2017

View PostCatch21, on Jul 23 2017 - 18:10, said:

Can anyone confirm the above posted at the Russian Forum? (Translation: "Yesterday, in micro-patch 9.19.1.1, Wargaming implemented a very controversial decision: it disabled the launch of World of Tanks on pre-release versions of Windows 10.".

 

I've been posting and searching in vain for a fix to a "Windows ucrtbase.dll has wrong version" after trying to load the game (with Win 10 Build 16241) and crashing, including sending in a ticket with all required info.

I'm that guy from RU forum :)

 

Confirming this in two ways:
1. This line is stored in new WoT client, you can use IDA Pro or similar tool to check this.
2. I've got confirmation from some devs in Minsk office.

 

The only known way to bring WoT in working state back is to revert Windows 10 to release 15063 build.

 

Also, you can try to use pre-micropatch WorldOfTanks.exe (not tested) http://openwg.net/do...01/0.9.19.82.7z



Yankee #10 Posted Jul 24 2017 - 19:08

    Major

  • -Players-
  • 33068 battles
  • 9,674
  • [-G-] -G-
  • Member since:
    08-02-2010
This seems like a very reasonable decision actually.

Mixai1l #11 Posted Jul 24 2017 - 19:33

    Corporal

  • -Players-
  • 6 battles
  • 13
  • Member since:
    07-24-2017

View PostYankee, on Jul 24 2017 - 21:08, said:

This seems like a very reasonable decision actually.


Don't sure that I can disclosure the real reason of Windows 10.162xx baning but for me it looks as very nonprofessional move. They could solve this problem in a less painful way.



Catch21 #12 Posted Jul 24 2017 - 23:31

    Sergeant

  • Players
  • 29746 battles
  • 155
  • [DOG5] DOG5
  • Member since:
    05-19-2013

View Postblack_colt, on Jul 24 2017 - 01:13, said:

 

Do you seriously expect WarGaming to support their app on a system in which the APIs have not been finalized? How is that controversial? So you took a gamble and installed an OS that is not available to the general public knowing that there may be issues and want the app provider to suddenly support you?  Support costs money - are you suggesting that WarGaming spend money supporting something that is constantly changing?

 

Just roll back to a the last publicly released version of MS Windows and play the game with that OS.

Yes, I'm aware rollback is a (final) option. Please don't kill the messenger, I'm just reporting that WG has disabled even trying to launch WoT on Insider Preview versions of Win 10 without letting us know. Previously WG has worked with players and MS- along with the graphics card manufacturers- on helping get WoT to work with beta builds of Win 10. If nobody does this type of testing, everyone will eventually have problems.

 

My real issue is not informing us they were going to do this- if it's the case in my OP- when as advance testers of Win 10, we're spending our good time trying to make sure it eventually all works for others. And a lot of time wasted, including in WG's own support area, when possibly even they're not aware this is now the case.



Baseline #13 Posted Jul 25 2017 - 01:40

    Private

  • Beta Testers
  • 6524 battles
  • 6
  • Member since:
    09-14-2010

Well I really appreciate this being brought up here as I was starting to beat my head against the wall wondering if anyone at MS or WG was even aware of the issues Insiders were encountering with the latest evaluation builds since 16199. 

 

I completely agree with Catch21 WG could have just let us know they were doing this and saved me hours of frustration and wasted time.

 

Being a beta tester means no good deed goes unpunished lately.



Catch21 #14 Posted Jul 25 2017 - 14:06

    Sergeant

  • Players
  • 29746 battles
  • 155
  • [DOG5] DOG5
  • Member since:
    05-19-2013

View PostBaseline, on Jul 25 2017 - 00:40, said:

Being a beta tester means no good deed goes unpunished lately.

Worse, what seems to be happening is that Win 10 beta testers are opting out of the Insider Preview "Fast Ring" because of problems like this and going to the "Slow Ring" (I did), where there's (in theory) been more testing (Fast Ring builds eventually become Slow Ring builds which eventually become Production/RTM builds). 

 

Microsoft's answer to fewer "Fast Ring" testers seems to be to push "Fast Ring" builds to the "Slow Ring" quicker to compensate... The logical end result is "Slow Ring" testers bail out too....

 

And to WG wasting time, my ticket eventually got escalated to WoT's Product Manager- after 2, days, 6 back and forth messages by 4 separate WoT Technical Staff (all trying hard to sort and TVM BTW!).

 



AlphaGhost141 #15 Posted Jul 26 2017 - 15:33

    Private

  • -Players-
  • 5334 battles
  • 1
  • [BRRLS] BRRLS
  • Member since:
    12-21-2016
I too have the same issue after updating to build 16241, No Support from Both WG and MS...  Going back to the Previous Build if it is the only option.

Mixai1l #16 Posted Jul 27 2017 - 10:57

    Corporal

  • -Players-
  • 6 battles
  • 13
  • Member since:
    07-24-2017

JFYI, the error is related to the incorrect calculation of the square root in 16xxx versions of ucrtbase.dll

 

reconstructed code from Worldoftanks.exe

Spoiler

 

WoT will be starting again after the fix from Microsoft.

 

P.S. Why do I do what a community manager should do?


Edited by Mixai1l, Jul 27 2017 - 11:48.


FeelMy_APCR #17 Posted Jul 27 2017 - 12:46

    First lieutenant

  • Players
  • 28830 battles
  • 786
  • [BRVE] BRVE
  • Member since:
    05-30-2012
If I have to chose between WG and Microsoft... Screw WG.

Mixai1l #18 Posted Jul 27 2017 - 14:32

    Corporal

  • -Players-
  • 6 battles
  • 13
  • Member since:
    07-24-2017

Good news, everyone. I've made a fix!

 

Unpack to WoT folder and run Wargaming_WIP_Launcher.exe

Attached Files

  • Attached File   Wargaming_WindowsInsiderPreview_Fix_1.0.zip   20.77K

Edited by Mixai1l, Jul 27 2017 - 14:36.


Marek_Marcin #19 Posted Jul 27 2017 - 15:38

    Private

  • -Players-
  • 0 battles
  • 1
  • Member since:
    07-27-2017

View PostMixai1l, on Jul 27 2017 - 14:32, said:

Good news, everyone. I've made a fix!

 

Unpack to WoT folder and run Wargaming_WIP_Launcher.exe

 

Thaks man gg 

Mixai1l #20 Posted Jul 27 2017 - 16:33

    Corporal

  • -Players-
  • 6 battles
  • 13
  • Member since:
    07-24-2017

Can somebody post this fix in EU thread? http://forum.worldof.../topic/637972-/

 

250 battles are too much for me :)






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users