Posts

Solution for Error 17002 when uninstalling Office 365 (2016) when apps like word, excel, outlook are open

Image
When uninstalling office 365 silently, it is failing only when any applications like word, excel are kept open. This is because during uninstall, office checks for any running applications and prompts the user to close it which is not happening in silent uninstall. When uninstalling in UI mode, it prompts to close when any office apps are open. Since in silent mode office is not able to do this, it fails with an error code 17002. You can check in the log file for the error code 17002. To overcome this just add the property FORCEAPPSHUTDOWN with Value="True" in the uninstall config.xml file. This property will force shutdown any running office apps. Example: <Configuration>  <Remove>  <Product ID="O365ProPlusRetail" >  <Language ID="en-us" />   </Product>  </Remove> <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Display Level="None"/> <Logging Path="c:\temp\" Name...

App-V: Virtual Packages works in win 10 1607 but fails in windows 10 1703/1709

Image
Many packages that completely worked in inbox App-V in windows 10 1607 failed after upgrading to windows 10 1703 and 1709 versions. The reason for failure is due to Microsoft changed the way to load registries in containers CREG instead of usual virtual registry VREG. To know about this change do have a look at the below articles from Tim Mangan. http://www.tmurgent.com/TmBlog/?p=2692 http://www.tmurgent.com/TmBlog/?p=2733 There was a temporary fix which was available and Roy Essers posted it in twitter a long back. It was adding the below registry entry manually in the 1703/1709 machines. [ HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\AppV\Client\Compatibility] "RegistryCompatibilityMode" = dword : 00000001 Microsoft has released an update earlier today which is supposed to fix this registry mapping issue. https://support.microsoft.com/en-us/help/4074588 We can clearly see that they have made use of the temporary fix to change the registry virtualization to use the VREG instead of...

Virtual Google Chrome and Local o365 issues - Solution

Image
After publishing Google Chrome App-V package in windows 7, logging into portal.office.com and opening a word or excel document and trying to edit it with locally installed Office 0365 fails. When checked with procmon, we can see that Google Chrome virtual package is able to see the local o365 package and tries to open it but the winword.exe process closes soon with exit code 1. As in last blog,  I have detailed about the same issue happening with Appv-d Mozilla Firefox package and local o365.The solutions are still the same for the current scenario too.  Solution 1: Create the  AllowJitvInAppvVirtualizedProcess  registry key as shown below to fix this known issue. Windows Registry Editor Version 5.00 [ HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\ClickToRun\OverRide] "AllowJitvInAppvVirtualizedProcess" = dword : 00000001 If it doesn't work try in wow6432Node registry. Windows Registry Editor Version 5.00 [ HKEY_LOCAL_MACHINE \SOFTWARE\Wow6432Node\Microsoft\ClickToRun\OverR...

Mozilla Firefox Virtual package and Local office 0365 failure

Image
After publishing Mozilla Firefox App-V package in windows 7, logging into portal.office.com and opening a word or excel document and trying to edit it with locally installed Office 0365 fails. When checked with procmon, we can see that Mozilla Firefox virtual package is able to see the local o365 package and tries to open it but the winword.exe process closes soon with exit code 1. Solution 1: Create the  AllowJitvInAppvVirtualizedProcess  registry key as shown below to fix this known issue. Windows Registry Editor Version 5.00 [ HKEY_LOCAL_MACHINE \SOFTWARE\Microsoft\ClickToRun\OverRide] "AllowJitvInAppvVirtualizedProcess" = dword : 00000001 If it doesn't work try in wow6432Node registry. Windows Registry Editor Version 5.00 [ HKEY_LOCAL_MACHINE \SOFTWARE\Wow6432Node\Microsoft\ClickToRun\OverRide] "AllowJitvInAppvVirtualizedProcess" = dword : 00000001 Solution 2: If Solution 1 doesn't work , try with the latest App-V 5.1 Hot Fix. Always make sure to use the...

Adobe Acrobat error 16 & UAC - App-V 5.1

Image
After converting Adobe Acrobat standard 10.0 application from App-V 4.6 to App-V 5.1 using powershell commands, it throws an error 16 when launching the shortcut. Reason: This is due to UAC and the application requires to be run as administrator. Solution: To test manually Click Start > All Programs. Right click on the Adobe Acrobat X Standard product and click Run As Administrator.The shortcut will launch without any error. So how to resolve this in the App-V 5.1 package? We need to suppress the UAC prompt when run as administrator. Check my another blog for more information to solve this issue  here

Sequence SPARX Enterprise Architect 13.5 - AppV 5.1

Image
Select create a new virtual package. Select create package. Select standard package. Select custom installation. Type the name of the virtual package as Sparx Enterprise Architect 13.5. Click Next and Install the application. Remove the desktop shortcut. Select I am finished Installing. If you need to do any post install configuration like adding new registration key,Launch the shortcut “Enterprise Architect” and do it here.Once done click Next. Click Next and save the Package. Publish and test the sequenced package in  the latest windows 10 environment.

Solution: COM Addin failure with Locally installed MS Office 2016 c2r

Image
These days I see many queries in Microsoft technet forum related to COM Addin's not getting loaded into locally installed MS Office 2016 c2r version. So to help others, I have listed the possible solutions which I have gathered from my experience and from other blog posts in a single article below. ISSUE: 1. Sequence Microsoft Office 2016 addin's using App-V 5.1 Sequencer 2. Publish the sequenced addin's package in the client side which has App-V 5.1 client and  Microsoft Office 2016 c2r locally installed 3. Launch the Microsoft Office 2016 c2r Word/Excel using /appvve: or RunVirtual registry key to load them into the  published addin's virtual environment to test the addin's. 4. we see that the addin is not loaded. You can find a similar possible reason for failure in the below link. https://support.microsoft.com/en-us/help/3159732/click-to-join-fails-to-invoke-skype-for-business-on-computers-that-us "The ProcessesUsingVirtualComponents  registry value speci...