Hey guys 

so I have recently installed the new Nvidia 391.35 driver

 

and have noticed that P3d is not shutting down completely 

it is still runnning in thou not visible in task manager.

ive tried reinstalling driver and issue still remains.

i haven’t added any add ons

any help is appreciated 

thanks 

mike

Did you close the process in task manager? It is also important that you wait for a while. Then restart your PC and check if the process is still active. This is necessary because W10 automatically re-opens processes during the next boot when they have not been closed correctly before shut-down.

Edited April 3, 20188 yr by Nemo

14 minutes ago, Nemo said:

Did you close the process in task manager? It is also important that you wait for a while. Then restart your PC and check if the process is still active. This is necessary because W10 automatically re-opens processes during the next boot when they have not been closed correctly before shut-down.

Hi 

thanks for the reply 

I did wAit about 5 min

still running.

restarted pc then it was shut down

again fired up P3d and word not allowed it down. But still running thou not visible in task manager.

 

Cannot seem to figure this out.

anyone else please?

thanks

mike

Hello Mike

Try these steps one by one.........

1)  Regardless weather or not this will fix your Issue,  Delete the Shaders folder and the Prepar3D.cfg file and let Prepar3D generate these again when launched next.

2)  Do you have any FSDT Add On's,  If so please See Here

3)  Right click and Rename your 2 dll.xml files, the one in ProgramData and AppData\Roaming,  Then launch Prepar3D, Shut it down and test ?   Does this work ? 

4)  Right click and Rename your 2 exe.xml files, the one in ProgramData and AppData\Roaming.  Then launch Prepar3D, Shut it down and test ?   Does this work ? 

 

If Renaming any of these files resolved your Issue you can then look closer at your Utility Add On's 

You can just simply rename these files back again when you are finished 

1 hour ago, Poppet said:

Hello Mike

Try these steps one by one.........

1)  Regardless weather or not this will fix your Issue,  Delete the Shaders folder and the Prepar3D.cfg file and let Prepar3D generate these again when launched next.

2)  Do you have any FSDT Add On's,  If so please See Here

3)  Right click and Rename your 2 dll.xml files, the one in ProgramData and AppData\Roaming,  Then launch Prepar3D, Shut it down and test ?   Does this work ? 

4)  Right click and Rename your 2 exe.xml files, the one in ProgramData and AppData\Roaming.  Then launch Prepar3D, Shut it down and test ?   Does this work ? 

 

If Renaming any of these files resolved your Issue you can then look closer at your Utility Add On's 

You can just simply rename these files back again when you are finished 

Thank you

will test and report back.

 

I am not sure if I explained correctly. First, manually close the processes in task manager! Then wait one minute, then restart your system.

1 hour ago, Nemo said:

I am not sure if I explained correctly. First, manually close the processes in task manager! Then wait one minute, then restart your system.

That’s the thing I don’t see the P3d exe in task manager 

This may help.

http://tweaks.com/windows/39559/kill-processes-from-command-prompt/

'tasklist' should confirm whether P3D is actually running or not.

Cheers,

Mark

On 2018-04-03 at 11:53 AM, Poppet said:

Hello Mike

Try these steps one by one.........

1)  Regardless weather or not this will fix your Issue,  Delete the Shaders folder and the Prepar3D.cfg file and let Prepar3D generate these again when launched next.

2)  Do you have any FSDT Add On's,  If so please See Here

3)  Right click and Rename your 2 dll.xml files, the one in ProgramData and AppData\Roaming,  Then launch Prepar3D, Shut it down and test ?   Does this work ? 

4)  Right click and Rename your 2 exe.xml files, the one in ProgramData and AppData\Roaming.  Then launch Prepar3D, Shut it down and test ?   Does this work ? 

 

If Renaming any of these files resolved your Issue you can then look closer at your Utility Add On's 

You can just simply rename these files back again when you are finished 

Hi,

Thank you very much! It was indeed the fsdt live updater that needed to be run again , all is well now.

and thank you all for your help.

Mike