Hi all,

I've tried patching via the game launcher and by manually downloading the 2.0 patch. Both times I'm getting errors even after multiple downloads and attempts. I've attached one error message below and the other one involved an error in the patcher's temporary directory at - \temp\pat37a.tmp and mentioned line 20879016.

Anyone else having similar issues or error messages?

Intel E6600
XFX Radeon HD4890
Intel D975XBX2
4GB DDR2
320GB 7200.10 HDD
X-Fi ExtremeMusic
Windows XP Pro 32-bit
Plenty of HDD space, latest drivers, ect.

Look like a user rigths problem to me.
Have you tried to login as administrator and then install?

All attempts at downloading/patching have been done as an administrator.

I think you may have put me on the right track. I managed to get the game patched, but I took sort of a "shotgun approach" and I'm not 100% what ultimately did it. My initial install attempts were done via an admin account, but I did not use the run as admin command.

Here's how I finally managed to get patched in the hopes it will help someone out there:

First, I excluded both my install directory and my \My Documents\Witcher 2\ directories in my Antivirus/Security Suite just to ensure this wasn't causing issues. I had previously and temporarily disabled it, but perhaps this alone was not enough.

Next, I ran the "patch2_0_INT.exe" (the appropriate patch file for me, may vary for others) under an admin account with the run as admin command with the "protect my computer..." option unchecked. This attempt actually did produce another error, but read on.

Realizing that the patch2_0_INT.exe file basically unzips a file called patcher.exe into \My Documents\Witcher 2\Downloads, I then went there and used the run as admin command with the "protect my computer..." option unchecked on patcher.exe.

After all this, the patching process did successfully finish. I booted up the game, noticed the new options, and then loaded up a save. Everything is looking good.

Thanks for the replies folks. I'm glad to be up and running, and it's much appreciated!

It could have been the lack of running the .exe as admin (which sometimes is required even when on an admin account) or your AV getting in the way of the install process or a combination of both.

Either way it's good to kow it's up and running now, happy monster slaying ;)