AppVolumes 2.13.3 Office 2016

[RWTownsend]

Hello,

I am attempting to install O365 Office 2016 into an AppVolume, the install and provision is giving me no errors.  After assigning the APPVolume and then trying to launch any Office application I receive the following error:

The application was unable to start correctly (0xc0000142). Click OK to close the application.

Any Idea's on what may be wrong?

Thanks in advance,

Rick

[sjesse]

Is the machine used to capture office a direct clone of the parent minus the other agents like UEM and Horizon, without running sysprep? I've seen wierd errors in Microsoft apps where if the SID of the parent and the build machine was not the same.

[RWTownsend]

Hi SJesse,

Thanks for the reply, to answer your question, No the parent is not a direct clone, however it was built with the same version of Windows 10 and both machines are patched to the same level.  Over the weekend I did make some progress and found the issue for the Error.  The machine I was trying to run Office 16 on had a "writable" volume using the "UIA_ONLY" template.  When I switched the machine over to the "UIA_PLUS_PROFILE" template all the Office 16 launched and I did not get the "The application was unable to start correctly (0xc0000142). Click OK to close the application" Error.  At this point I have not put UEM into the build.

Rick

[Ray_handels]

Then sjesse was spot on.

What happens if you add a writable (at least the profile part) is that activation from the Office application takes place in the writable volume thus supressing the error.

I would suggest cloning the GI and remove the View agents. This way you can install office correctly.

To this day Office and Appvolumes is still an issue. To be honest it is not only due to Appvolumes but also due to the way Microsoft is doing it's new licensing model. It is not just a file you should exclude. It is way to much info being stored for as far as I can see... And also related to the SID of the machine...

[RWTownsend]

Hi Ray_handels,

Thanks for the reply.  As I am very new to "AppVolumes" and "UEM" my goal was to move away from using "Persona Management" and just use a "writable volume" in AppVolumes to store OST and user data.  I am using VMWARE View 7.2.0 non-persistent Link clones.

I also did a 2nd test, installing Office 16 directly on the Gold Master (instead of running it as an AppStack) and received the same error when a "writable volume" was attached with the "UIA_ONLY" template.  If I had no "writable volume" or used a "writable volume" with the "UIA_PLUS_PROFILE" template then the Microsoft applications launched with out the error.

From all the posts I am reading it does not look like this is a stable option.

Rick

[Ray_handels]

I also did a 2nd test, installing Office 16 directly on the Gold Master (instead of running it as an AppStack) and received the same error when a "writable volume" was attached with the "UIA_ONLY" template.  If I had no "writable volume" or used a "writable volume" with the "UIA_PLUS_PROFILE" template then the Microsoft applications launched with out the error.

That's strange. If you install Office in the GI and only have a writable attached it should work correcty.

We have Office installed in base and have it working without a writable attached so no idea why you are having these issues with only the GI and a writable.

[sjesse]

Are these fresh writables or have them been used before? Why I asked if for whatever reason something office related is saved in the writeable it can cause issues.