Can anyone check their P3D4.3 Appdata Roaming Directory?

[Guest]

34 minutes ago, Skywolf said:

I did this with 100% clean windows installation and only Prepar3d.

Did you delete all 6 related P3D folders after you uninstalled V4.2?

The install path for ...\Lockheed Martin\Prepar3D v4

C:\ProgramData\Lockheed Martin

C:\Users\[YourUserName]\Documents\Prepar3D v4 Add-ons

C:\Users\[YourUserName]\Documents\Prepar3D v4 Files

C:\Users\[YourUserName]\AppData\Local\Lockheed Martin

C:\Users\[YourUserName]\AppData\Roaming\Lockheed Martin

I've done several hundred clean installs with V4.3 thru-out the beta cycle and not experienced that error.  My only other suggestion is to use DDU to remove nVidia Drivers, download the lastest nVidia drivers from their website, and then install the drivers manually.

Cheers, Rob.

 

[fghdgdfdfgfgf 111]

4 hours ago, Skywolf said:

Can anyone check their Prepar3d v4 Roaming directory and tell me if they are seeing 2 files being created right after shutdown?

Should I worry about why they are created.  I did not see these error files in 4.2 and before.  They only came up if the sim crashed.

 

Current Config

Zero addons and just the latest Windows 10 Pro Build 1803 with latest patches.

P3Dv4.3 works fine, but every time I exit.  I do see dxDiag and Prepar3D.cfg (text Document version) is created. It seems P3D4.3 is not exiting cleanly.

I know the hardware is fine, b/c none of these errors were every produced in any other build of P3D. 

Should I just ignore it and start adding my addons and enjoy the sim. Or is there something else going on.

Thanks,

skywolf

What does the generated report say? Is it complete?

I looked at mine, and the report complained about not being able to get my system info, otherwise everything passed. So for kicks and giggles, I went to the Windows Experience index app and it said my system info and index were no longer valid and need to updated. I re-ran the index with Addon Manager and viola P3d closed with out error, BUT! I still got a report. The report was clean and it had all my system info in the report.

 

Edited June 27, 2018 by FunknNasty

[Skywolf 992]

55 minutes ago, Rob Ainscough said:

Did you delete all 6 related P3D folders after you uninstalled V4.2?

The install path for ...\Lockheed Martin\Prepar3D v4

C:\ProgramData\Lockheed Martin

C:\Users\[YourUserName]\Documents\Prepar3D v4 Add-ons

C:\Users\[YourUserName]\Documents\Prepar3D v4 Files

C:\Users\[YourUserName]\AppData\Local\Lockheed Martin

C:\Users\[YourUserName]\AppData\Roaming\Lockheed Martin

I've done several hundred clean installs with V4.3 thru-out the beta cycle and not experienced that error.  My only other suggestion is to use DDU to remove nVidia Drivers, download the lastest nVidia drivers from their website, and then install the drivers manually.

Cheers, Rob.

 

Yes Sir,

I did all of that.

It is just strange 4.2 doesn't give me a weird report and 4.3 does.  I also reinstalled windows this afternoon.  I mean its a real clean build (I am quite a pro with P3d installs too, I have to get to LM's beta team somehow... 😉).

 

For example, 

I have this part at the end of the dxdiag file.  but I do not have 4.2 client installed (at all...it is complete 4.3).  Now lets say I uninstall the 4.3 client only and downgrade with 4.2 client.  Error just do not show up

 

 

 

Windows Error Reporting:
+++ WER0 +++:
Fault bucket 2222782207043961316, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.2.21.24048
P3: 10.0.17134.2.0.0
P4: 
P5: 
P6: 
P7: 
P8: 
P9: 
P10: 

+++ WER1 +++:
Fault bucket 2276974447974145495, type 5
Event Name: StoreAgentDownloadFailure1
Response: Not available
Cab Id: 0

Problem signature:
P1: Acquisition;RuntimeBroker
P2: 8024001e
P3: 17134
P4: 112
P5: Windows.Desktop
P6: V
P7: 
P8: 
P9: 
P10: 

+++ WER2 +++:
Fault bucket 1478241538906225710, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1
P2: 80070643
P3: 3F2BFD37-5F26-4B2C-87E4-92ABC22B1539
P4: Install
P5: 200
P6: 0
P7: 800705b4
P8: UpdateOrchestrator
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

+++ WER3 +++:
Fault bucket 1399730516166492312, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 8024500b
P8: Device Driver Retrieval Client
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

+++ WER4 +++:
Fault bucket 1250809733622942912, type 5
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1
P2: 800704cf
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 0
P8: Device Driver Retrieval Client
P9: {8B24B027-1DEE-BABB-9A95-3517DFB9C552}
P10: 0

+++ WER5 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1
P2: 80070643
P3: 3F2BFD37-5F26-4B2C-87E4-92ABC22B1539
P4: Install
P5: 200
P6: 0
P7: 800705b4
P8: UpdateOrchestrator
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

+++ WER6 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1
P2: 80070643
P3: 3F2BFD37-5F26-4B2C-87E4-92ABC22B1539
P4: Install
P5: 200
P6: 0
P7: 800705b4
P8: UpdateOrchestrator
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

+++ WER7 +++:
Fault bucket 1934885900210683650, type 5
Event Name: MpTelemetry
Response: Not available
Cab Id: 0

Problem signature:
P1: 0x800705b4
P2: ValidateUpdate
P3: N/A
P4: 1.1.14500.5
P5: mpsigstub.exe
P6: 4.18.1806.18062
P7: Microsoft Windows Defender (RS1+)
P8: 
P9: 
P10: 

+++ WER8 +++:
Fault bucket , type 0
Event Name: LiveKernelEvent
Response: Not available
Cab Id: 0

Problem signature:
P1: ab
P2: 2
P3: 80
P4: 0
P5: 4
P6: 10_0_17134
P7: 0_0
P8: 256_1
P9: 
P10: 

+++ WER9 +++:
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0

Problem signature:
P1: 10.0.17134.1
P2: 8024402c
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 0
P7: 8024500b
P8: Device Driver Retrieval Client
P9: {9482F4B4-E343-43B6-B170-9A65BC822C77}
P10: 0

 

 

 

[Skywolf 992]

30 minutes ago, FunknNasty said:

What does the generated report say? Is it complete?

I looked at mine, and the report complained about not being able to get my system info, otherwise everything passed. So for kicks and giggles, I went to the Windows Experience index app and it said my system info and index were no longer valid and need to updated. I re-ran the index with Addon Manager and viola P3d closed with out error, BUT! I still got a report. The report was clean and it had all my system info in the report.

  

Can you tell me what windows app is this.  Did you re-ran the index with Addon Manager? Is this FSDreamTeam Addon manager? 

[fghdgdfdfgfgf 111]

Yes

5 minutes ago, Skywolf said:

Can you tell me what windows app is this.  Did you re-ran the index with Addon Manager? Is this FSDreamTeam Addon manager? 

I don't think i'm helping here. sorry.  I'm on Win7 Pro ...if you're on Win10 you may not have a Windows System Index utility.

Oh, and half expected ....I did receive another  """something prevented P3D from closing"""" box upon closing P3D....and yes it was with ADDON MANAGER active. But Hey!  The DXDIAG report came perfectly clean.

[WarpD 824]

1 hour ago, Skywolf said:

P1: Prepar3D.exe
P2: 4.2.21.24048
P3: 10.0.17134.2.0.0

That says you're running v4.2 not v4.3

[Skywolf 992]

19 minutes ago, WarpD said:

That says you're running v4.2 not v4.3

Yes...that is the bizzare part.  

so this is what I did.

1) Wipe out complete SSD - Reinstall Windows 10 Pro (I have my usb key)

2) Install 4.3

3) I get the error

4) Uninstall the Client only and reinstall 4.2 client to test

5) No error

6) Uninstall the 4.2 client (everything else is still 4.3), and install 4.3 client only

7) Get Error

8 Uninstall the whole Sim, and reinstall 4.3 from full installers

9) Get error files - and for some reason it shows 4.2 at the end of the DxDiag file.

Weird day 

Edited June 27, 2018 by Skywolf

[Skywolf 992]

Rob from Prepar3d just replied to this thread.

It is okay for now about the files being created (cause no harm while sim is in operation).  It will be fixed in the next update

https://prepar3d.com/forum/viewtopic.php?f=6312&t=129955&p=181985#p181970

 

[mikeymike 357]

Has this been resolved? 

[Skywolf 992]

1 hour ago, mikeymike said:

Has this been resolved? 

Hi,

I was like wait - I created this thread a while back - Yes, it got fixed in 4.4 and now with 4.5HF2 (no issues), now if some addon crashes or something - sometimes those files are created.  LM confirmed the issue with me at the time the thread was created here.

Hope it helps.

 

 

[mikeymike 357]

4 hours ago, Skywolf said:

Hi,

I was like wait - I created this thread a while back - Yes, it got fixed in 4.4 and now with 4.5HF2 (no issues), now if some addon crashes or something - sometimes those files are created.  LM confirmed the issue with me at the time the thread was created here.

Hope it helps.

 

 

I see, well I guess I’ll be disabling addons and figuring  which one it is 

[mikeymike 357]

Well I can’t figure it out 

I have disabled all addons via the lorby organizer tool

and still can’t figure it out.

Reinstalled drivers also

Edited January 31, 2020 by mikeymike