Hi,

Also posted over at LM forum...............

I have tried many times to apply the latest patch V6.1.11 to my V6.1.9 installation but with no success.
It goes through all the motions and says it has been succcessful but it is'nt.
I am still left with V6.1.9.

My installation is in D:/Prepar3d V6/ and the patch installer "sees" it there, says it's going to update it, takes about 15mins or so, reports that it was
successful but I'm still left with the old version.

I have tried both auto update and manual installation.
I have tried "repair" also after successful reporting of patch installation.
I am using Admin mode.
Complete P3D dir. excluded from Win Defender.

Why is it not updating?

All help/suggestions appreciated.

TIA.

Maybe uninstall and download entire full package from LM?

I thought of that but the full version is only V6.1.9 so would still have to install the patch and I have already re-installed that version.

 

Is the patch an msi file ?

If so you should be able to run it via a cmd with logging enabled which might provide a clue.

https://community.flexera.com/t5/InstallShield-Knowledge-Base/Logging-an-MSI-Installation/ta-p/4323

https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/msiexec

Another thing is the locale and language, often MSI's might be expecting a particular language or locale like English USA.

Cheers

 

Sorted folks!

After un/re-installing V6.1.9 yet again and the update failing again (but reports successful, as before) I decided to "Take ownership" of the entire P3D folder and then applied the patch and 'Hey Presto!' it worked.

So, I assume some file somewhere was being prevented from writing to somewhere ???

Will never fully get to grips with MS and their OTT permissions/security/UAC and all this, with me as the only user on the PC and obviously with full admin rights !!!

What a palava..........😁

 

Edited February 20, 20242 yr by Sparkrite

Where is your P3D installed ?

I avoid the "Program Files" paths due to just this sort of thing.

I also remove the Creator/Owner user group from the root folder as it tends to hide account access issues due to the Creator/Owner having full control over files the account creates. I've even seen corporate files locked out from anyone's access, and user "A" being able to run a program and user "B" not able, all due to the local I.T. crew not understanding how NTFS and the various user groups permissions align, ahh the perils of NTFS (and outsourcing to the lowest bidder).

Also MS have a funny system of admin rights.

For instance the very first local user created on the computer will have admin rights.

But not just any old admin rights, more like admin rights without UAC.

Anyway, I always disable that user account after creating a specific admin account and a separate user account, where in my case a policy places it in the local admin user group.

And even though the user account is located in the local admins group, it will actually run as a standard user account until admin rights are required, where upon it will request a grant of elevation of rights to perform the admin task.

Cheers

 

@rogan

22 hours ago, Rogen said:

Where is your P3D installed ?

As per first post:-

On 2/19/2024 at 8:23 PM, Sparkrite said:

My installation is in D:/Prepar3d V6/

Thanks for the info on user accounts and is something I must try.

I know it takes time, setting it all up again but may be worth it......MS certainly don't help trying to insist that new user accounts also register with them as well.

Thanks again.

Edited February 21, 20242 yr by Sparkrite

Hey @Sparkrite,

My bad, I obviously missed the path mention...

Yeah MS has a habit of forcing their internal business plans upon their user base, MS was always jealous of Apple's cloud based walled garden just chock full of user accounts ripe for mining and sales income.

And so they make it seem like the only way forward is to create a login to a walled garden of their own making, plus they've pulled many sneaky tactics over the years where clicking no meant yes or skip meant yes or close meant yes.

Also those MS "Feature" updates do have a tendancy to reset your privacy settings back to default.

Cheers