LibreOffice 4.1 - Fatal error App-V 5.0

When launching Libre office in the App-V client, it shows fatal error.


Solution:
Check Dan Gough's blog where he has explained the cause for the failure and his workaround Here

Comments

Post a Comment

Popular posts from this blog

Add custom scripts in AppxManifest.xml file using App-V 5.1 Sequencer

Image
In the Package editor under advanced tab, you can see the Manifest file tab which has been introduced in App-V 5.1. This doesn't exist in earlier versions of App-V. Using this tab, you can export or import the AppxManifest.xml file. Earlier if we want to do any custom changes we have to edit the deploymentconfig or userconfig.xml file(for adding scripts, editing FTA's etc). App-V 5.1 provides advanced way to edit those changes within the AppxManifest.xml. To do so, click on export as highlighted below in the Manifest file tab. This will export the AppxManifest.xml file to the local machine. choose the destination and click on save. Open the exported AppxManifest.xml using AppVManifestEditor. You can download the tool from here AVME AVME is a simple yet powerful tool to edit the AppxManifest file.My recommendation is not to edit the AppxManifest file manually. After opening the file using AVME,you can select the checkbox on left hand side to enable the type of script you want(Ma...
Read more

UAC and App-V 5.0 Demystified

Image
There are some methods through which we can suppress UAC prompts when virtualizing using App-V 5.0. You can try the below methods which ever suits your need. 1. SET __COMPAT_LAYER: Edit the sequenced shortcut and add the below command. cmd.exe /c “SET __COMPAT_LAYER=RunAsInvoker & START Appname.exe” Note: There is a space in between SET and __COMPAT_LAYER. If you didn't leave any space it will throw an error. "SET' is not recognized as an internal or external command. 2. Registry Method: Right click on the shortcut and select properties-compatibility-privilege level- run as admin-apply. This will create a registry entry in the HKCU\HKLM based upon User/Machine selection. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers (or) HKEY_Current_User\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\AppCompatFlags\Layers Export the registry key and add it in the deployment config file and register it in the local machine. NOTE: Enable script exec...
Read more

Decrypting how Microsoft Teams new MSI works

Image
Microsoft has released a windows Installer MSI for Microsoft Teams for deployment through SCCM.You can download it here As per Microsoft Statement: "The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of Teams application will be installed in that user's appdata folder. If a user already has the Teams app installed in the appdata folder, the MSI installer will skip the process for that user." NOTE: Don't change the install location as it will break the process. In this blog, I will explain how this happens by opening MSI using Installshield. 1. To Install Microsoft Teams, it first requires .net 4.5 or later to be installed in the machine. This check happens using Launch condition which also does a system search for .net registry to be present in the machine. 2. The MSI has only one file which is Teams.exe that gets installed to [ProgramFilesFolder]Teams Installer locat...
Read more