Problem Installing Patch
Posted: Sat Sep 22, 2012 11:11 am
Hello,
I have been having problems installing the 4.1.1.1 patch, whether manually or via the in game updater. The error I am getting is "Error applying patch to D:\Config.Msi\PT34DF.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor." I have the choice of Retry, Ignore, Cancel. Retry gets me nowhere, Ignore goes through and the patch appears to have run fine, but the game version is still 4.1.0.5. Cancel, well, cancels it. I have tried patching a few different times and the filename is not always the same and if I choose ignore I find that it stops with this error on several files.
I have made sure that I have full NTFS permissions on the Config.Msi folder. I am installing using an administrator account. I have disabled my antivirus when running the patch. The Config.Msi folder itself is created when starting the patch, and is removed when the patch terminates so there aren't any old files stuck in there that can conflict.
Out of ideas. Anyone out there have something I haven't thought of yet?
HeadHunter
I have been having problems installing the 4.1.1.1 patch, whether manually or via the in game updater. The error I am getting is "Error applying patch to D:\Config.Msi\PT34DF.tmp. It has probably been updated by other means, and can no longer be modified by this patch. For more information contact your patch vendor." I have the choice of Retry, Ignore, Cancel. Retry gets me nowhere, Ignore goes through and the patch appears to have run fine, but the game version is still 4.1.0.5. Cancel, well, cancels it. I have tried patching a few different times and the filename is not always the same and if I choose ignore I find that it stops with this error on several files.
I have made sure that I have full NTFS permissions on the Config.Msi folder. I am installing using an administrator account. I have disabled my antivirus when running the patch. The Config.Msi folder itself is created when starting the patch, and is removed when the patch terminates so there aren't any old files stuck in there that can conflict.
Out of ideas. Anyone out there have something I haven't thought of yet?
HeadHunter