The typical App-V error code consists of 2 x 4 bytes in the form hexadecimal: "0x000000-0x000000". The first six characters refer to the App-V source code and can be ignored. For error analysis the last 10 characters are interesting. So "00-0x000000". The first two characters show the type of error and the source. The last eight characters are the actual error code. Once an error code is returned as a decimal number, then this decimal number must be converted to a hexadecimal value for analysis.

Months have passed since our first blog on the topic (Recipe: Virtualize Edge with App-V). During this time the Edge has proven to be a very stable App-V application. If I read from time to time that a new critical vulnerability is emerging, the virtual Edge can react quickly. At this point I would like to point out that we regularly create the Edge and other browsers for our customers. This is done with known AppV bugfixes and with customer specific settings. If you are interested please contact me. For example on Twitter @Nickinformation

The old recipe for SSMS 17.x was a nice success for me with about 1000 hits. Especially the comments were enlightening. The licensing problem could be solved with a simple registration key. With 18.5 there is nothing more to do here.