Going backwards. . .again!

falcon409

falcon409

Moderator
Staff member
I've uninstalled P3D_V2.1 and am going back to 2.0 which worked flawlessly. Even though 2.2 is about to be released I intend to wait that one out to see if it brings along the same amount of problems that 2.1 did. Now for the problem. . .I have uninstalled the program but when I try to install 2.0 it stops with a message that there is already a newer version installed. I have gone through the registry and removed any references to Lockheed/Lockheed Martin/Prepar3D/P3D. There is nothing remaining, yet the installer is still finding something. . .somewhere. Any ideas as to where else it might be seeing something?
 
Have you tried checking these folders where, for example, the Prepar3D.cfg file is ?
You know, these folders they recommend to delete when installing the 2.1 patch... names like %APPDATA%\Prepar3D...

EDIT:
%PROGRAMDATA%\Lockheed Martin\Prepar3D v2
%LOCALAPPDATA%\Lockheed Martin\Prepar3D v2
%APPDATA%\Lockheed Martin\Prepar3D v2
%USERPROFILE%\Documents\Prepar3D v2 Files
 
You should also check to make sure that the newer version doesn't exist in the Windows package cache (I'm betting it does). Assuming your system drive is c:, you'll find a bunch of cryptically named folders in c:\ProgramData\Package Cache. On my system, there are two such folders containing P3Dv2 files ... one for 2.0 and the other for 2.1. You'll probably need to delete the one on your system that contains the 2.1 installation files.

Good luck ... and proceed carefully,
Mike
 
mbmorgan said:
You should also check to make sure that the newer version doesn't exist in the Windows package cache (I'm betting it does). Assuming your system drive is c:, you'll find a bunch of cryptically named folders in c:\ProgramData\Package Cache. On my system, there are two such folders containing P3Dv2 files ... one for 2.0 and the other for 2.1. You'll probably need to delete the one on your system that contains the 2.1 installation files.

Good luck ... and proceed carefully,
Mike
Click to expand...
Mike, that was it. Amazing how many different places you'll find remnants of a program. I obviously had no idea that was even there. Thanks for the HU. Much appreciated!
 
Amazing difference! 2.0 just seems custom made for my rig. Just did some really enjoyable flying over sharp terrain, no blurries, autogen that extends beyond the limits I was seeing in 2.1. . .very smooth. I think that until such time as LM get's the sim really settled in, I'm sticking with 2.0. I know there are those who have had little or no problems with the transition to 2.1 and that's great, but aside from that irritating problem with the aircraft initially loading at full throttle, I never saw any of the problems others were seeing with 2.0. Ver 2.1 w/hotfix has been nothing but trouble to the point that it was no longer enjoyable to fly in. This is where I need to be until I see solid evidence that 2.2 isn't just another round of beta testing and new problems.
 
I just got back to my SA Quarters and you know what the Texas pest destroyed my I5 system err. Being on a tight budget I went to Wal Fart and bought a gateway AMD A6 Quad system. I upped the ram from 6 to 8 and then disconnected the DVD and hooked up the 1 TB drive for P3D no issues and then tossed in the Nvidia GT610 2GB card after going into Bio's due to W8 64 and UEFI to get legacy mode invoked and bingo works like a champ. So I am now going back to P3DV1.4 and I know 1.4 will work if I had it working once on a Intel Core2duo 2.93, 4gig and 1gig GT220. I also know the P3DV2.1 will work on this too. So back to 1.4 and forward inching baby steps for the Sweet Zone of my personal taste. When I get her locked into that 1.4 sweet then I start the locking in the V2.1 sweet zone. Why is San antonio full of Computer destroying Roaches errrr. Those ***'s have costed me 1000's already and the pest man is a jerk of a orkin yutz. I don't have this issue in Corpus??. Sorry for the rant.
 
You must log in or register to reply here.
Back
Top