4 replies to this topic

[newplar]

Hello,

 

all was fine for 6 months til yesterday when i tried and successfully validated my game files (they were missing 1.4mb ish) - I did this because I though my game was corrupted as for the last few days I've been seeing 2d cows in a matrix/array floating on top of water

 

anybody have any idea why the auto-updater would close when trying to unpack the files?

 

I downloaded it and extracted it into downloads as once I'd validated the troll-patch had gone. 

I ran updater 101 (as admin also later) and it recognised the game file location than asked to install and i said yes,

it downloaded then tried to unpack then immediately closed and my game no longer has the mount&siege launch screeen. 

I've also tried disabling win defender but it makes no difference. 

 

I have a feeling my computer/hard-drive or memory is about to crap out as it doesn't recognise all drivers anymore but in the meantime I was wondering if anyone has some suggestions about this...

 

GG

[LizardWizard]

Hi.

 

Do you have admin rights over the folder where you use the updater ? It would be useful if you could record the whole process with a screen recorder and send me the video link in a pm.

 

PS. The auto-updater goes through a cleanup process after it installs the patch, meaning it will delete your troll-patch archive and everything else related to it (this includes any old trollpatch archives you might have in the same folder as the updater when you run it).

I guess I should add an option to ask the user if he/she wants to cleanup.

[LizardWizard]

I tried the updater today to make sure it's working:

 

Warband launcher after using the patch. It seems the problem is on your side.

screenshot

 

I will help you but I need more details. Let's move this conversation to a PM so we can better pinpoint the problem.

[BlackDeath]

About cows: https://community.tr...-water/?hl=cows

you are not alone

[LizardWizard]

The problem was caused by placing the troll_updater.exe inside the Native directory and running it. The updater attempts to overwrite the Native directory while it is still being run from inside the folder. This breaks the updater's routine and terminates the process.

 

To avoid this do not place the updater inside Native. The updater can be run from any other location on the hard disk as it does not rely on a relative path to the Warband installation directory.

 

In order to prevent situations like this one we will also add this bit of info in the download section of the updater as well as in a readme.txt file that will be attached to the updater zip.

If there are any more bugs / issues that you would like to report, please send them to me via PM.

 

Topic closed.