AppV 5.1 Sequencer – Not capturing all registry keys

AppV 5.1 Sequencer – Not capturing all registry keys

2016-09-20
/ /
in Blog
/

Video of this issue:

https://theorypc-my.sharepoint.com/personal/trententtye_theorypc_onmicrosoft_com/_layouts/15/guestaccess.aspx?guestaccesstoken=vq4pmhseZam8zGPBh6Q8bn%2bgvaZrVuFc4fXo%2fziYmeA%3d&docid=08e53da35fa314929a7ce6578c69bf5c5

The issue is when sequencing an application (100% reproducable on Epic and the VMWare Hypervisor) and then you add a large ‘update’ (for Epic this is the client pack) then not all registry keys are captured. Β At 8:20 seconds you can see keys that are present in the local registry are not present in the package.

appv_bug

 

Notice the “0”, “win32” and FLAGS keys are missing in the AppV package.

This is the script I used to compare the local registry vs the package:

 

3 Comments

  1. Alex Sweserijnen 2016-09-21 3:15 am

    What happens when you use the Custom Installation option instead of the Select installer to install option right before monitoring?

    Reply
    • trententtye 2016-09-21 9:34 am

      Same result. Not all registry keys are captured.

      Same thing happens if you go through and manually install everything with the mouse. “Next Next Next” wait “Next Next Finish” etc. πŸ™

      Reply
  2. Pingback: AppV 5.1 Sequencer – Not capturing all registry keys – Update – Trentent Tye – Microsoft MVP

Leave a Reply to Alex Sweserijnen Cancel reply

Your email address will not be published. Required fields are marked *

*

This site uses Akismet to reduce spam. Learn how your comment data is processed.