OK thanks Saul, actually emailed licensing (like last time when I bought new 2.5 3 days before v3 came out!) I guess they'll pass on . .

OK the problem is when trying to purchase via the v3 opening screen where it says your license has expired. Going direct to the store without trying to open P3D v3 has worked - at last. Never had this problem up to 1.4 and all the versions 2.x Now I just need to get the unwanted, unordered v2.5 lice...

This gets worse. I have just sent the following to licensing: Please read all the below Re the below email. To be exactly correct, I opened v3 and it said license expired. I clicked on the purchase link and it took me to a Prepar3D v3 Professional purchase page I clicked on 6 months non-recurring I ...

Just renewed a developer subscription 6 month for v3 and when attempting to activate, I get: Error: Invalid ProductID (5010) Done this re-activate before, no problems. No changes to computer. Yes, I've emailed licensing, but we know how long that can take, and anyway it's Sunday ;-( Before someone s...

just in case anyone missed, seems cleared with latest FSUIPC - at least for me

I got it without touching anything after clicking close - but anyway, 4.496 is now up (though still says 49.44 on the link of course!) as of today, checking it out . . .

Look at the install log which is in the modules folder of any sim it did install into . The log lists where it's looked for sims in the registry sometimes tries several places - first HKEY_LOCAL_MACHINE then CURRENT_USER for example, then uses setpath or apppath or what it finds. Does this search fo...

So I removed the dll.xml from Appdata, which only had the FSUIPC entry, and no error on exit, so it definitely seems to be FSUIPC - but how fatal error, faulting module, ntdll.dll in SysWOW64, when its not there? Any ideas or is it just wait for Pete?

Now it's complicated. I'm getting this, first with nvapi.dll, but in SysWOW64, so I deleted nvapi and next time exited OK. The weirdness is, I'm now getting the ntdll.dll error like above BUT still in SysWow64 (notsys32!). So I deleted it there. Worse, I'm still getting the fatal error with ntdll.dl...

Saul, more or less clear on above except scenery. I have all add-on scenery either in an "external to P3D" Addon Scenery folder (scenery, texture) or dedicated folders within the Addon Scenery or dedicated folders for large stuff like FS Global. I then add the Scenery Library entries in th...

Well I created a restore point, then used the uninstaller via Guru3d, in Safe Mode. Then used the previously downloaded 355.60 to install only the graphics driver and PhysX. The restart after install went straight to the same BSOD from the login screen, no desktop or anything. Any attempt to start i...

Others have reported about a 10% FPS increase with these new drivers, I can't confirm. I'd suggest you use DDU tool ( http://www.guru3d.com/files-get/display-driver-uninstaller-download,20.html ) to do a full driver wipe (via Safe Mode) and then install latest nVidia drivers (be sure to download th...

FWIW this 355.60 driver made my Office 2007 apps go straight into BSOD - any app every time - including Outlook. (2x670 Sli) Faulting was nviddmkm.sys - no idea why and seemed only Office apps. Tried to roll back driver and not possible. Possibly an incorrect install I guess (was via GeForce Experie...

If this IS new machine though - very important - did you uninstall from old machine?

<t>Thanks Walter. K et al - Going to do as suggested but not holding breath. Similar was advocated on A**** and got 30-40 replies, sorry - lot more replies but from same people "voices" 30-40 as in people nagging nVidia. . . This one ain't millions of users (yet) sadly. What is un-understandable is ...