Be XXX if Im going through an other 6 hour download session, XXX around with all the registry XXXX. Uninstall for good.
Think the grand I have dropped into this game they might make things easier.
Critical error?
Started by
miles1991
, Jun 20 2012 - 14:05
186 replies to this topic
#162 Posted Jun 21 2012 - 23:16
Meatvan, on Jun 21 2012 - 23:10, said:
Be XXX if Im going through an other 6 hour download session, XXX around with all the registry XXXX. Uninstall for good.
Think the grand I have dropped into this game they might make things easier.
Think the grand I have dropped into this game they might make things easier.
I am still waiting for my premium refund however.
#163 Posted Jun 22 2012 - 00:31
dekk01, on Jun 21 2012 - 23:16, said:
The registry BS actually isn't that long. Don't think it took me more than 5 minutes. What did take me long (over 6 hrs) was deleting and re-downloading the game 3 times before they sent me the final solution.
I am still waiting for my premium refund however.
I am still waiting for my premium refund however.
Actually, the final solution was discovered right here in this thread by a player, not by WOT tech.
#165 Posted Jun 23 2012 - 05:05
Ardraug, you are the man. 4 downloads later, a 2 minute fix is all I needed to begin with. Props to you for finding out how to fix the game. If I see you in a game I will gladly take a shell for you. Going to send you a friend request.
#167 Posted Jun 30 2012 - 18:44
i got it fixed using this solutions thanks !! looks like it mostly affects Vista user .
#170 Posted Jul 03 2012 - 01:58
kodan19, on Jun 21 2012 - 15:49, said:
this is how to fix it To open the Registry Editor, click the Start button and type “regedit.exe” (without the quotation marks) and press the ENTER key. If you see the User Account Control dialog box appear, click Continue.
On the left side, expand the tree structure until you find the registry key that starts with "HKEY_LOCAL_MACHINE\COMPONENTS\Winners\x86_policy.9.0.microsoft.vc90.crt_".
Expand the key above.
Below that key, you should see a 9.0 key. Select the 9.0 registry key.
In the right pane, make note of the number you see in the Data column for the row where the Name is set to (Default), in case you need to revert to this number later.
Look through the list of numbers in the Name column and find the highest number.
Double-click the (Default) string value to open the Edit String dialog box.
Replace the number in the "Value data" box with the highest number you saw in step #6. Click OK.
On the File menu, click Exit to close the Registry Editor.
After completing step #8 the issue may be resolved. If you continue to see the same problem restart the computer. You may also need to follow the steps below to correct the file association error message.
On the left side, expand the tree structure until you find the registry key that starts with "HKEY_LOCAL_MACHINE\COMPONENTS\Winners\x86_policy.9.0.microsoft.vc90.crt_".
Expand the key above.
Below that key, you should see a 9.0 key. Select the 9.0 registry key.
In the right pane, make note of the number you see in the Data column for the row where the Name is set to (Default), in case you need to revert to this number later.
Look through the list of numbers in the Name column and find the highest number.
Double-click the (Default) string value to open the Edit String dialog box.
Replace the number in the "Value data" box with the highest number you saw in step #6. Click OK.
On the File menu, click Exit to close the Registry Editor.
After completing step #8 the issue may be resolved. If you continue to see the same problem restart the computer. You may also need to follow the steps below to correct the file association error message.
had the side by side error again today. this post is a good summation of arduang's original fix- handy if you have to double check yourself like i do.
#171 Posted Jul 03 2012 - 17:00
i also had a repeat of this issue today, dont know why. ardraug's fix worked again though many thanks
Edited by sidcixel, Jul 03 2012 - 17:02.
#173 Posted Jul 03 2012 - 19:20
had it, Ardruag's fix still works. side note the numbers went back to the same when it last had the error????
#174 Posted Jul 03 2012 - 22:12
ardraug, on Jun 21 2012 - 05:47, said:
PRYAN - mine was much simpler, but I think I know which one you should look at.
Run WOT so you get the error and it will be at the top of your events
Go to windows search - find the Event Viewer
Run it
In the left column is an option called "Windows Logs"
Click it
In the same column click "applications"
In the middle of the program a list of application errors should display with the Side by Side one at the top
Open it
Should tell you which registry folder is involved.
Run WOT so you get the error and it will be at the top of your events
Go to windows search - find the Event Viewer
Run it
In the left column is an option called "Windows Logs"
Click it
In the same column click "applications"
In the middle of the program a list of application errors should display with the Side by Side one at the top
Open it
Should tell you which registry folder is involved.
#177 Posted Jul 10 2012 - 12:29
PRYAN - mine was much simpler, but I think I know which one you should look at.
Run WOT so you get the error and it will be at the top of your events
Go to windows search - find the Event Viewer
Run it
In the left column is an option called "Windows Logs"
Click it
In the same column click "applications"
In the middle of the program a list of application errors should display with the Side by Side one at the top
Open it
Should tell you which registry folder is involved.
I got that much but what do i do when I get the folder that I need?
Edited by eagames645, Jul 10 2012 - 12:30.
#178 Posted Jul 26 2012 - 09:22
This is what i did and it works.I found this in my side by side error reporting which you need to go into "event viewer" which for me in Win Vista 64 bit it is in the admin tools folder. Once in event viewer you click on the tab "Window logs" and click on "Application". You will see the side by side error click on that and it will give you the program that is cuasing the trouble. Mine was:
Activation context generation failed for "C:\Program Files (x86)\Windows Live\Messenger\msnmsgr.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_none_5090ab56bcba71c2.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada.manifest.
I edited the regedit feature in the file: WinSxS\manifests\x86_microsoft.vc90.crt like others were doing but this did not work for me. All i did was deleat Windows Live Messenger which i do not use and World of Tanks is working again!
Activation context generation failed for "C:\Program Files (x86)\Windows Live\Messenger\msnmsgr.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4148_none_5090ab56bcba71c2.manifest. Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.1_none_e163563597edeada.manifest.
I edited the regedit feature in the file: WinSxS\manifests\x86_microsoft.vc90.crt like others were doing but this did not work for me. All i did was deleat Windows Live Messenger which i do not use and World of Tanks is working again!
#179 Posted Jul 26 2012 - 20:38
Nobody should be editing registry, it's unnecessary. I feel bad for some of you that listened to the bs being tossed around because you don't know any better.
All you have to do to fix this is download and install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
All you have to do to fix this is download and install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
#180 Posted Jul 28 2012 - 20:49
misscleo, on Jul 26 2012 - 20:38, said:
Nobody should be editing registry, it's unnecessary. I feel bad for some of you that listened to the bs being tossed around because you don't know any better.
All you have to do to fix this is download and install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
All you have to do to fix this is download and install Microsoft Visual C++ 2008 SP1 Redistributable Package (x86).
I did this and it didn't work (Vista 64). Once in awhile I have to edit the registry (after server updates). What happens is that the Reg file/path that WoT uses, value is higher that the the default value for Vista users. If WG wanted to they could easily correct it with a simple script but either they choose to ignore it or figure that they'll leave it to us.








