You must deliver a legacy engineering application that installs kernel-mode drivers and shell extensions to users in a pooled Windows 11 Enterprise multi-session host pool. Updates are infrequent, performance is critical, and sign-in time must be minimized. What should you do?

Installing the application directly into the session host master image is the correct approach because kernel-mode drivers and shell extensions require deep integration with the operating system. MSIX app attach (and App-V streaming) are designed for user-mode applications and cannot handle these types of components, which need to be present at the OS level. Directly embedding the application ensures optimal performance and minimizes sign-in time by having the application readily available. Updating the image when the app changes is a standard practice for managing applications in persistent environments. Publishing only through the web client does not address the underlying installation requirements of kernel-mode drivers and shell extensions.