Blog Posts by apptopack

Ask a question

Virtual Google Chrome and Local o365 issues - Solution

After publishing Google Chrome App-V package in windows 7, logging into 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


If it doesn't work try in wow6432Node registry.

Windows Registry Editor Version 5.00


Solution 2:

If Solution 1 doesn't work , try with the latest App-V 5.1 Hot Fix. Always make sure to use the latest App-V 5.1 Hot Fix. (A minimum of Hot Fix 4 is required for this issue to be resolved.)

You can download the latest Hot Fix here: KB4018510

Tested the same scenario in Windows 10 1607, only the AllowJitvInAppvVirtualizedProcess registry key is required.

NOTE: Fixes that are delivered to the “out-of-box” versions of App-V and UE-V are first delivered for the “in-box” versions of App-V and UE-V in the monthly Windows 10 cumulative updates.Since updates are provided to windows 10 in-box App-V client first, it will not require the installation of the latest Hot-Fix.

From Windows 10 1703, this AllowJitvInAppvVirtualizedProcess registry key will be automatically added when any of the Office product starts.
Be the first to comment

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

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.


< Configuration>
 <Product ID="O365ProPlusRetail" >
 <Language ID="en-us" />
<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
< Display Level="None"/>
< Logging Path="c:\temp\" Name="Uninstall.log"/>
< /Configuration>


Place  the  <Property Name="FORCEAPPSHUTDOWN" Value="True" /> part after  the <Remove>... </Remove> tags. If it is placed in between <Remove>... </Remove> tags, then it wont work.

You can use the below online configuration xml editor to avoid issues when editing the XML file.
Be the first to comment

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

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.

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.



Microsoft has released an update earlier today which is supposed to fix this registry mapping issue.

We can clearly see that they have made use of the temporary fix to change the registry virtualization to use the VREG instead of the modern CREG that was mentioned earlier to permanently fix this issue.


Apart from the registry fix, this update also fixes many other App-V issues which can bee seen below.


This update will be downloaded and installed automatically from Windows Update. If you would like to use the standalone package for this update, download it from the below link.

NOTE: This fix is supposed to be only for windows 10 1709. The article haven't mentioned anything about windows 10 1703. Will do a check in windows 10 1703/1709 and update how the fix has really helped to solve the issue.

Update: This issue is also fixed in windows 10 1703 with the new hotfix released.

Link -

Be the first to comment

Online Office 365 ProPlus Configuration XML Editor

Microsoft Office 2016 365 click to run application needs to be packaged using ODT.

Download link for ODT -

When you download ODT, a configuration.xml file will be also downloaded along with the setup.exe. This file is required to make further customization to the package.

To know more about configuration.xml check this link -

When you edit the configuration file, you might find it quite difficult to make it work proper. In order to avoid this you can use the online configuration editor available from Microsoft.

Check the Microsoft official link to create Configuration XML. This link makes the work easy.


View comments (1)

How to specify whether or not Adobe Acrobat to take ownership of the default PDF file extension when Adobe Reader is already present

We can use properties to set Adobe Acrobat not to take ownership of the default PDF file extension, by leaving Adobe Reader as the default PDF reader.

For version 10.0 & higher use the property LEAVE_PDFOWNERSHIP=YES

YES - prevents the new installation from taking over PDF ownership. 
NO - allows the new install to own opening PDFs. 

For version 11.0 & higher use the property OWNERSHIP_STATE=0.

0: Do not take ownership.
1: Take ownership for the current user. 
2: Take ownership for all existing and new users.
Be the first to comment
Showing 1 - 5 of 16 results

Top Contributors

Talk About Repackaging