This is the official thread for any issues that are preventing you from LAUNCHING the game. If you're experiencing such an issue or have a solution to such an issue, please post and discuss it here.
UPDATE [March 12, 10:20pm MST]:
Thanks for your patience everyone. We released a BETA patch this afternoon that fixed a number of these release-control related issues as well as an issue where the game would ask for non-existent drives. Also, we have further updates and workarounds for a number of these issues. Hopefully this will get the bulk of you up and running in time for the weekend. If you are still affected, please continue to post and help each other out and we'll continue to make these blocking issues a priority.
The primary culprits for many of these issues remain out of date video drivers, interference from antivirus software, Windows administration rights, and errors within users' Windows setups. We're continuing to investigate these issues and are identifying fixes and workarounds wherever possible.
EV#52959 – Some are getting “The application will not run on a Windows guest account or an account with insufficient privileges” error, regardless of Admin status.
- We have confirmed internally that this issue is not resolved by the BETA patch.
- We believe this to be a result of WMI misconfiguration in a user's
system. You can see if this is the case if your Windows is unable to see
your system's hardware components (ie. processor, RAM, etc). You can
verify if you are in this situation by doing the following:
1) Right click on My Computer and click on Properties
Incorrect information will be displayed for your system's Processor and
potentially other hardware components in the bottom right
1) Go to the Control Panel
2) Click on System.
3) You should see something similar to this: http://i.imgur.com/HN86i.jpg
this is what you're seeing, your WMI configuration has been corrupted.
As a result, Windows is unable to determine your Processor and other
hardware components and therefore DA2 is unable to determine your
hardware components during activation.
To fix this, you will need to rebuild your WMI repository. I
want to stress that this fix is not for users who are not running as
Administrators. You must be logged in as an Administrator. In
addition, if you are at all uncomfortable with the process of touching
your system's WMI files, please wait for a more official fix.
Download the WMI Diagnosis Utility from Microsoft's site and execute the VBS script within. http://www.microsoft...1E-4C64192AE97D
1) Open a Command Prompt (Windows Key + R, then enter 'cmd')
2) Within the command prompt, execute the following command: ' net stop winmgmt ' without quotations.
3) Rename your Repository folder (%SystemRoot%\\System32\\WBEM\\Repository) just in case you wish to restore it.
4) Within the command prompt, execute the following command: 'winmgmt /salvagerepository' without quotations.
5) The above command will rebuild the repository if it is corrupted and then restart the WMI service.
After your WMI repository has been rebuilt, please try and activate DA2. If you're still seeing the same symptoms, it could be that you're running on an older BIOS that needs to be updated. We've also had user reports of having to enter "c:\\>net localgroup administrators NetworkService /ADD" in the command prompt as a final step. Another user reports that their winmgmt service was disabled. They were able to run msconfig and enable it, then start winmgmt from the command prompt, which finally fixed it for them.
- Users have confirmed that this issue is not resolved by the BETA patch.
- Some (but not all) users have been able to resolve this issue by installing the latest ATI or Nvidia beta drivers. For more
info about graphics drivers, see the DX11 thread -
- Early reports suggested that this was due to an outdated version of the Windows .NET Framework, but we no longer believe that to be the case. Instead, we now believe it to be related to Admin accounts. Some users are reporting that the issue is resolved by creating a new user with Admin rights in the Users control panel, then logging under that account to install and validate the game. After having done that, they were able to log back into their regular account to play the game.
- We believe this is related to interference from anti-virus software.
Users are reporting that the issue resolves if you turn off all
anti-virus software as well as your Windows firewall and then reinstall.
- User reports suggest that this has to do with Administration privileges. Under Windows 7, you will need to run an elevated command prompt (basically run cmd.exe as administrator). Then you have to enable the hidden built-ina dministrator account for Windows 7 using the following command prompt: "C:\\windows\\system32>net user administrator active:yes" ...Then log off of your account and log into the built-in administrator account where Dragon Age II should now run successfully. If you need more detailed instructions on the built in administrator go here - http://www.sevenforu...le-disable.html ...Windows Vista is essentially the same process - see http://support.microsoft.com/kb/555910
- User reports suggest this is resolved with the 1.01 BETA patch.
- For Steam users unable to access the BETA patch, previous reports suggested that it might be tied to interference from AVG or other anti-virus software. Other reports suggest it might be related to graphics drivers.
to close. We are sorry for the inconvenience." error
- We have more reports of this but are still trying to identify the cause.
- User reports suggest that it might be tied to interference from AVG or other anti-virus software. We're continuing to investigate.
- A lot of users are reporting success from the following procedure: Under AVG settings, go to the "exceptions" tab
under Resident Shield then unblock the activation software by adding this line to the "add path" tab:
C:\\Users\\Username\\AppData\\Local\\Temp\\mtka_tmp ...It's possible this file is causing problems with other forms of anti-virus software as well.
- Definitely grab the latest ATI and Nvidia beta drivers, as described in the DX11 thread - http://social.biowar...0/index/6420212 ...Turn your settings down to DirectX9 if you can. If you can't run the launcher or config utility, there is a DX11 line in the DragonAge.ini file which you can set to UseDirectX11Renderer=0 - it doesn't exist until you run the game, however. Depending on when you're failing, you may not have an *.ini file to edit.
Edited by Rob Bartel, 13 March 2011 - 05:22 AM.