World of EUC

Don't know whether it's linked but all of my App-V packages seem to have this weird brown icon on all of the files within them, not sure what that is

Then you should check that app is calling which URL in the backend or application team can help you here....

You can added that URL to IE2Edge Compatibility List and it's done :+1:

maybe run a procmon trace on the first run and 2nd run

if its not appv related then maybe ipconfig /flush and clear routing table, netsh clear arpe cache

I think I had a similar problem once.

Check if the following registry key contains the correct path for the user SID.

%USERPROFILE%\AppData\Local\Microsoft\AppV\Client\VFS

<@U02E1R7JK55> which registry key do you mean exactly?

sorry...
That is the key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppV\Client\Virtualization\LocalVFSSecuredUsers

The path in the registry is correct, looks like this doesn't impact the issue. I opened a support ticket a couple weeks ago, but so far I haven't made much progress...

2023-02-16 14_45_27-Citrix Workspace - [InPrivate] - Microsoft Edge.jpg

Has anyone got MSIX integration to Citrix Cloud working on CVAD Server VDA? I have ran the MSIX packaging tool for something simple (notepad++) - saved the msix file to a network share and then published via Citrix Cloud, but get the following error:

Has anyone received an issue with App-V packages where the FilesystemMetadata.xml gets corrupt when the package is mounted? We've been using the same App-V package for years without issue. We rebuilt two image over the weekend, and now the App-V app won't start, and I traced it back to being a corrupt FilesystemMetadata.xml. I can't even open the file in notepad, but it opens fine on the previous build.

image.png

So I've got a bunch of App-V applications that all install fine on any Windows 10 machine......except for one package. Whenever I run this package locally, all I get is the following error -

Which is obviously weird because this is a Windows 10 client with the App-V client enabled so it doesn't need the App-V client installing.......am I missing something obvious here? Is there some fundamental setting missing in the package?

You could open the package on the sequencer and see which OS is listed in the deployment tab

You might also find it was sequenced on a 32 bit sequencer

Hmmm, listed as "any OS" in the sequencer program....how to tell if it was sequenced on a 32-bit platform?

from the change history properties page you can get the history of the sequence and see what OS/machine it was sequenced on

whats the below saying on the client ? PS U:\> Get-AppvStatus

Key                      Value
---                      -----
AppvClientEnabled         True
AppvClientRebootRequired False

Let me check the Properties page tomorrow

Looks like a hella old sequencer and version of the software - and the machine no longer exists - so I'm thinking you're right, it's a 32-bit sequence job

Is it possible to use MSIX App attach for Windows Store apps? A client wants to run a Windows Store app on Server 2022 and asked me if he could use app attach for this.
Not sure if that even works or if it's even the right approach?

Is it possible to do office addin’s with msix? I’m pretty sure the answer is no, but just checking.

App-V client and sequencer not EOL!  <https://learn.microsoft.com/en-us/microsoft-desktop-optimization-pack/app-v/appv-support-policy>

Is there a new end of support date for the App-V client and sequencer?
No, the App-V client and sequencer have moved to <https://learn.microsoft.com/en-us/lifecycle/policies/fixed#extended-support|fixed extended support> and is no longer deprecated.
Are the App-V server components still deprecated?
Yes, the App-V server components are still deprecated and support will end in April 2026. Only the client and sequencer have moved to <https://learn.microsoft.com/en-us/lifecycle/policies/fixed#extended-support|fixed extended support>. <https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-overview|App-V app attach> allows you to use your App-V packages with Azure Virtual Desktop without needing to run your own server. There are also non-Microsoft server products that you can use with your existing App-V packages.
Should I migrate away from App-V?
If the current feature set of App-V works for you, there's no need to migrate away. If you choose to migrate from on-premises to the cloud, <https://learn.microsoft.com/en-us/azure/virtual-desktop/app-attach-overview|App-V app attach> allows you to use your App-V packages with Azure Virtual Desktop. However, since the client and sequencer have moved to <https://learn.microsoft.com/en-us/lifecycle/policies/fixed#extended-support|fixed extended support>, development will be constrained to bugs and security fixes, not new features.

Thanks, <@U06TW61P12A> This was good news.  We;ve been working hard on migrating away from App-V and maybe now we can reassess our plans.