Blogs from TMurgent
Today we have a couple of releases for Microsoft App-V tooling. With the cancellation of the End-Of-Life for the App-V Sequencer and Client, we are updating our tooling to catch up on a few things.
AppV_Manage is our free community tool, typically used by someone packaging applications into App-V and wants a quick way to test …
TMEdit (not T
MEditX) is our App-V package editor tool, used to improve packages for Microsoft App-V. It’s been a while since we had a release and I had been sitting on a few fixes requested by customers. But rather than just some bug-fixes, we have something new here.
First, TMEdit 2.0 is being released as an MSIX package. Why? …
TMEdit is the licensed and more capable tool for fixing up App-V packages (the application virtualization system that actually works) since it doesn’t have to depend on the Microsoft Sequencer Tool to create the final package. TMEdit Download (tmurgent.com)
The TMEdit tool analyzes and fixes App-V packages. This release contains the following changes:
Now that I’m back in the lab I’ve had a chance to test the latest ADK Sequencer for App-V. Here are the results:
I’ve noticed lately a few people complaining that they needed to go back to the Windows 10 ADK 1803 sequencer in order to get some applications to work. Recently, a student came to one of our App-V Training Classes and brought with him a reproducible application that demonstrated the problem. Based on what we learned in the class debugging it, and …
If you have been Sequencing for Microsoft App-V on Windows 10, you have probably noticed a lot more garbage in your packages.
While the App-V Sequencer has a really awesome capture algorithm that automatically ignores changes made by pre-existing Windows background processes, under Windows 10 there are many, many, more background events that generate new processes, resulting in more crap …
I suddenly seem to be getting asked by a number of software vendors to help them support customers that are using App-V. This is fantastic! Vendors that want to support App-V? We have dreamed of this for 15 years now. I am thinking that four is perhaps more than just a blip, maybe it is a trend. I certainly hope …
Last year I wrote an article on App-V and .Net Native Images and how they didn’t work with App-V.
I was wrong, but it wasn’t my fault. It turns out that the trusted tooling that I used, the Microsoft SysInternals ProcessExplorer, was lying to me.
One of the uses of ProcessExplorer is to view the modules (fancy name …