Chris,

I had exactly the same issue as you. The steps I carried out were exactly as you described and always ended up with blank screens, un-clickable buttons and switches and no landing gear.

As a last resort I put an exclusion, in the anti-virus software, for the folder containing the PMDG Operations Center.

I then went through the whole updating process again and this time it worked. All updated OK and flew a 7 hour flight with no problems.

This is on Windows 10, P3D and Windows built-in anti-virus software.

Hope this assists you.

Best Regards

John Fairman

2 minutes ago, johnfairm said:

As a last resort I put an exclusion, in the anti-virus software, for the folder containing the PMDG Operations Center.

I then went through the whole updating process again and this time it worked. All updated OK and flew a 7 hour flight with no problems.

Thats  the  same  thing  as  disabling  your  av

Peter,

I had already disabled the av with no success whatsoever. So this was my last throw of the dice before submitting a support ticket. It was at about 1.30am last night and it worked. I,like Chris had spent many hours trying to get the update to work, and finally, for me it did.

Best Regards

John

 

9 hours ago, funkyhut1 said:

Kyle,

With respect sir, listen to your community!

I have been doing that for some 7+ hours. Same result EVERY time. Quoted below from the last post to my open ticket after multiple tries at this, EVERY one following the procedure set out below.

"

Chris Stanley

Today at 09:10

Latest Update (18 files)

OK folks at PMDG, here I go!
After a hiatus of 9 hours to get some sleet (sic sleep) I returned to my PC again to try to resolve this per your instructions.
This is what I did:
1. Started my PC.
2. Turned off AVG, AVG Firewall and Windows Firewall
3. Installed the Base Pack of the 744 (as Admin)
4. Re started my PC (which also restarted the AVG and Firewall stuff)
5. Ran FSX, loaded the 747- 400 RR variant. It worked just fine.
6. Exited FSX
7. Re started my PC
8. Turned off AVG etc. etc.
9. Started OPS as Admin and got the update message
10. Ran the update which went without any hitches in about 5 minutes
11. Exited OPS
12. Re started my PC
13. Ran FSX and loaded the same RR varient
14. NO CLICK SPOTS, NO GEAR, NO SET UP COUNTDOWN.

15. Follow Ryan's delete instructions per an earlier post to this ticket, to the letter, turn off my PC and go back to 1. above..........

Now totally fed up.
Want my money back in return for my assurance to you that I've deleted everything per your instructions relating to this plane and will never waste my time ever trying to install it and run it.
I'll stick with PSX and run it linked to the standard FSX 744.
If I want eye candy I'll fly the 777.
Thank You."

just by off  chance just wondering  if  your  av  had  some  how  quarantined   the   download  and  its  still  there, which  some  how  is preventing the install, if it  there  just  delete it  and  do the  same  steps above, just a thought.  Since  had the  same  issue  with ut2   once it  quarantined the  exe   and   coudnt  find  out  why it  wouldn't  run until i deleted  from the  quarantine folder and  excluded  the exe   from scanning

12 minutes ago, johnfairm said:

Peter,

I had already disabled the av with no success whatsoever. So this was my last throw of the dice before submitting a support ticket. It was at about 1.30am last night and it worked. I,like Chris had spent many hours trying to get the update to work, and finally, for me it did.

Best Regards

John

 

glad it  worked  out  for  you  but most likely  it  was just coincidence   that it  worked  out  that way,  anyways  the main thing  its  has  solved  your  issue

On 14/03/2017 at 10:06 AM, rsrandazzo said:

Chris,

You sound a bit frustrated- and I get that.  We are working pretty much around the clock on the other sie of this to sort out why about 3% of customers appear to be having trouble.

What we have narrowed it down to thus far is three things:

1) Needing updated visual studio runtimes (which is covered in another post and I do not think applies to you here.)

2) Exceptionally poor download quality to some sectors of the world (asia primarily... we are enlisting Amazon's help to resolve this.)

3) User installed anti-virus software causing file corruption and/or simply absconding with files coming in via the updater.

If I was going to bet on your condition right now- I'm going with #3.  We are in the process of building out a machine in house that has some "after market" A/V packages installed to see if we can't trip up the system and replicate the issue.  Bottom line is that none of us are using these aftermarket products primarily because they tend to be rather invasive for very little gain...  and if I can be political about AV products- they HAVE to catch some things and throw around quarantines in order to keep you thinking they do a good job and thus convince you to reinvest.  The reality is that the tools provided by MS with/for window10 will do an exemplary job for almost all users unless a particular user is intentionally involved in some dodgy parts of the internet...

So- stick with us here.  We are working to sort out some changes to smooth out the rough edges.  If you like, simply reinstall the base package and when we think we have a solution you can update at that time.

 

I seem to have fixed it and have posted what I did for others to share. You guys at PMDG are class and the way you're handling this simply confirms that. Thank you.