App-V 5.1 HF2 und App-V 5.0 SP3 HF3 ist nun als Hotfix zu haben

Hallo zusammen,

hier nun der neueste Hotfix für App-V 5.1 und auch 5.0 SP3

Schönen Gruß

Sebastian Gernert - Escalation Engineer App-V

Comments

If your Application will not native run on Win 10 - App-V can not help as it's not a Compatibility Tool.
Technical speaking - if you copy (overwrite) that DLL while Sequencing or add it into the System32 Part of teh App-V Package that DLL must be used.
If teh Application is Bitness aware - you must create two Packages one on 32 Bit one on 64 Bit. Just from the Info above, it should be possible to bring that Application in App-V to live. Kind regards Sebastian

Anonymous
February 29, 2016
Hi Sebastian Is it possible to instruct the appvclient to inject a custom dll into our virtual process? I know that the appvclient injects the AppVEntSubsystems32.dll or AppVEntSubsystems64.dll into the virtualprocess depending on the bitness, but if for some reason it doenst inject the dll, what could be the problem? As i asked before, if i put a shell32.dll into the virtual environment, i can see in procmon that the appvclient first always injects the shell32 from the outside system, and only after it loads the image dll from the outside system, it loads from the bubble causing conflicts and ordinal errors. Any way to force custom dll injection?
Anonymous
March 07, 2016
What exactly does the following mean? Enable users to create multiple instances of Office 2016 Click-to-Run apps.
Anonymous
March 07, 2016
Hi Frank, If you use Office 365 (O2016) as C2R Version and have App-V installed you getting an error if you try create multiple instances of Excel as example. it works for one, two but at some point creating new instances show an error. Kind regards Sebastian