Jump to content

Do You Have The "please Wait" Admonishment, Read Here.


5 replies to this topic

#1 Gremlich Johns

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 3,855 posts
  • LocationMaryland, USA

Posted 15 August 2013 - 01:10 PM

Alle,

I have been plagued by the AMD CPU and Avast issue since a hot fix and two patches ago. Others have been affected as well and not just those with my configuration. I submitted a trouble ticket. Twice. I got the most recent response:

The devs are working closely with Avast to resolve this issue as soon as possible. We invite you to contact Avast! directly to learn about the potential impact of disabling hardware virtualization. An update will be added to the thread as soon as we have more information that is concrete. We do not require any information from specific systems regarding this at this point however, thank you for the offer.

Now, according to some posters in the so named AMD CPU and Avast tread, it isn't limited to that configuration. In fact, there are some with that configuration who were not affected at all, without even using the two work-arounds players offered. So, I think the devs might want some other info from players.

With that in mind, respond to this thread if, and only if, you get the "Please Wait" after you press the "Play" button on the game launcher. To reiterate -- If you do not have this issue, please refrain from posting here. Again, PGI should know that even if they fix the AMD/Avast issue, there may still be some other configurations they have not considered.

What you should post is CPU, whether CPU is overclocked, mobo and mobo BIOS iteration, RAM (brand, quantity and speed), OS, what anti-virus you have resident, and any anti-spyware or anti-malware programs that are resident, and firewall (whether Microsoft's or something else, and MW:O version. If anybody else can come up with something reasonable to add to my list, please let me know.

CPU: FX-4100/socket 942 OC'd to 4.2 GHz
mobo: ASUS M5A97 rev 1.xx
BIOS American Megatrends ver 1605, 10/25/2012
RAM: 16 GB of G Skill F3-12800CL9-4GBRL
OS: Win 7 64-bit, current
AV: Avast internet Suite, program ver. 8.0.1489, virus def ver. 130814-0 (also my firewall)
Anti-spyware resident: Spybot search and destroy
Punkbuster is resident (stopping it had no impact)
No anti-malware resident
MW:O ver: 1.5.4.3

Edited by Gremlich Johns, 15 August 2013 - 01:12 PM.


#2 darkstar3825

    Member

  • PipPip
  • Philanthropist
  • Philanthropist
  • 23 posts
  • LocationFederation of Skye

Posted 15 August 2013 - 04:34 PM

CPU: FX-8350
MOBO: MSI 990FXA-GB80
BIOS: AMI v11.13 10/9/12
RAM: 16GB Kingston KHX1600C9D3K4/16GX
OS: WIN7 64bit
AV: Avast Internet Security v130815-1
MalwareByte PRO

#3 Gremlich Johns

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 3,855 posts
  • LocationMaryland, USA

Posted 16 August 2013 - 01:09 PM

bump

c'mon, they really do need to figure this out and with others NOT having avast and still getting the "please wait" means there is other code making the game not launch.

#4 Justin979271

    Member

  • PipPip
  • 20 posts

Posted 16 August 2013 - 01:57 PM

[color=#939393]OS Name Microsoft Windows 8 Pro [/color]
[color=#939393]Version 6.2.9200 Build 9200 [/color]
[color=#939393]Other OS Description Not Available [/color]
[color=#939393]OS Manufacturer Microsoft Corporation [/color]
[color=#939393]System Name JUSTINM [/color]
[color=#939393]System Manufacturer BIOSTAR Group [/color]
[color=#939393]System Model TA990FXE [/color]
[color=#939393]System Type x64-based PC [/color]
[color=#939393]System SKU None [/color]
[color=#939393]Processor AMD FX™-6100 Six-Core Processor, 3300 Mhz, 3 Core(s), 6 Logical Processor(s) [/color]
[color=#939393]BIOS Version/Date American Megatrends Inc. 4.6.4, 3/8/2012 [/color]
[color=#939393]SMBIOS Version 2.7 [/color]
[color=#939393]Embedded Controller Version 255.255 [/color]
[color=#939393]BIOS Mode Legacy [/color]
[color=#939393]BaseBoard Manufacturer BIOSTAR Group [/color]
[color=#939393]BaseBoard Model Not Available [/color]
[color=#939393]BaseBoard Name Base Board [/color]
[color=#939393]Platform Role Desktop [/color]
[color=#939393]Secure Boot State Unsupported [/color]
[color=#939393]PCR7 Configuration Binding Not Possible [/color]
[color=#939393]Windows Directory C:\Windows [/color]
[color=#939393]System Directory C:\Windows\system32 [/color]
[color=#939393]Boot Device \Device\HarddiskVolume1 [/color]
[color=#939393]Locale United States [/color]
[color=#939393]Hardware Abstraction Layer Version = "6.2.9200.16442" [/color]
[color=#939393]User Name JustinM\JUSTINM\Justin [/color]
[color=#939393]Time Zone Eastern Daylight Time [/color]
[color=#939393]Installed Physical Memory (RAM) 8.00 GB [/color]
[color=#939393]Total Physical Memory 7.98 GB [/color]
[color=#939393]Available Physical Memory 5.81 GB [/color]
[color=#939393]Total Virtual Memory 9.16 GB [/color]
[color=#939393]Available Virtual Memory 6.72 GB [/color]
[color=#939393]Page File Space 1.19 GB [/color]
[color=#939393]Page File C:\pagefile.sys [/color]
[color=#939393]Hyper-V - VM Monitor Mode Extensions Yes [/color]
[color=#939393]Hyper-V - Second Level Address Translation Extensions Yes [/color]
[color=#939393]Hyper-V - Virtualization Enabled in Firmware Yes [/color]
[color=#939393]Hyper-V - Data Execution Protection Yes

I also am having this issue. My patience are running out.
[/color]

#5 Gremlich Johns

    Member

  • PipPipPipPipPipPipPipPipPip
  • The 1 Percent
  • The 1 Percent
  • 3,855 posts
  • LocationMaryland, USA

Posted 18 August 2013 - 07:21 AM

Just got word from an Avast customer support rep.

Unchecking "enable hardware-assisted virtualization" in Avast Antivirus products will NOT compromise my computer's security.

So, Uncheck that option in the Avast AV troubleshooting section of "Settings", then restart your computer. You should be able to play the game. I have and I have had no issues yet.

This confirmation for my system to play MW:O, with an AMD/Avast configuration, does not let PGI off the hook. They still have to fix the issue, especially if there are others with the same problem but with different configurations.

Why PGI did not verify the option with Avast to begin with instead of waiting all this time (since the first workarounds were posted by players) for me to do it myself is beyond me.

While I am glad the workaround will not open my computer to threats, this really is unconscionable for a business to do - leave customers hanging about the one possible workaround that they could endorse for people who subscribe to Avast. I have no issues with IGP's rep Reppu (who was assisting me in this matter), considering he passes on issues to the PGI staff who is supposed to remediate player's game software issues.

This perceived lack of interest on PGI's part to follow through since the workarounds were posted is emblematic of their business model - get the money's and new players by providing a passable product with lots of distractions directing attention away from the games flaws.

#6 darkstar3825

    Member

  • PipPip
  • Philanthropist
  • Philanthropist
  • 23 posts
  • LocationFederation of Skye

Posted 18 August 2013 - 12:57 PM

Thanks for the info.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users