NVidia Control Panel Windows 11 , with EL turned on

[Sergio Masone1709161115]

Hi,

I'm currently experiencing a behavior with windows 11 published templates on nutanix. Once I publish an image template that has elastic layering turned on, (without any layers attached), in my published image I cannot see the nvidia control panel, cannot open it, when i do it says no nvidia gpus are attached to the system... if  iI re-publish the same image with elastic layering turned off / none, the nvidia control panel is working and i can open it just fine.. All our vms are vGpu accelerated with nvidia , anyone else see this behavior? I would like to use elastic layering but im hesitant because of this problem as i dont know if it's hiding a bigger issue..

[Ryan Barrick1709163235]

This might be related - https://support.citrix.com/s/article/CTX241448-nvidia-control-panel-fails-to-launch-in-platform-layer-or-published-image?language=en_US

[Sergio Masone1709161115]

Just now, Ryan Barrick1709163235 said:

This might be related - https://support.citrix.com/s/article/CTX241448-nvidia-control-panel-fails-to-launch-in-platform-layer-or-published-image?language=en_US

Hi,

This is already in place for us, a layer with the alwaysonboot registry setting, with nvidia paths mentioned in the article, and is part of the published template.

however after checking in the final published template, i don't see it in the list, as if it got removed.. I do see a bunch of other entries, but not the nvidia ones.. Ill try recreating a new preserve nvidia layer and republish to see if it does the trick.
Thanks

[Sergio Masone1709161115]

3 hours ago, Sergio Masone1709161115 said:

Hi,

This is already in place for us, a layer with the alwaysonboot registry setting, with nvidia paths mentioned in the article, and is part of the published template.

however after checking in the final published template, i don't see it in the list, as if it got removed.. I do see a bunch of other entries, but not the nvidia ones.. Ill try recreating a new preserve nvidia layer and republish to see if it does the trick.
Thanks

Recreated a new layer with the alwaysonboot reg values set , doesnt seem to persist in the final image template, as this is the list of entries in the alwaysonboot that get populated after publishing, It either ignores my nvidia layer with this setting set, or its being overwritten for some reason.

C:\Program Files\Windows Defender Endpoint Advanced Threat Protection\
C:\ProgramData\Microsoft\Windows Defender Endpoint Advanced Threat Protection\
C:\Users\All Users\Microsoft\Windows Defender Endpoint Advanced Threat Protection\
C:\Program Files\Windows Defender Advanced Threat Protection\
C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\
C:\ProgramData\Microsoft\EdgeUpdate\
@C:\Program Files (x86)\Microsoft\EdgeWebView\
C:\Program Files (x86)\Microsoft\EdgeUpdate\
C:\Program Files (x86)\Microsoft\EdgeCore\
C:\Program Files (x86)\Microsoft\Edge\
@C:\ProgramData\Microsoft\Windows\AppRepository\
@C:\Program Files\WindowsApps\
C:\Windows\*\LogFiles\LSA\
C:\Windows\*\LogFiles\SAM\
C:\Windows\system32\drivers\mssecflt.sys
C:\Windows\system32\drivers\mssecwfp.sys
C:\Windows\Setup\Scripts\kmsdir\GenRandomQMID.log
C:\Windows\system32\perftmp.dat
C:\Windows\Setup\Scripts\envsetup.log
C:\Windows\Setup\Scripts\ActivateOffice_log.txt
C:\Windows\Setup\Scripts\kmsdir\StartCCMExec.log
C:\Windows\Setup\Scripts\kmsdir\runato.log
C:\Windows\Setup\Scripts\kmsdir\gposetup.log
C:\Windows\Setup\Scripts\kmsdir\kmssetup.log
C:\Windows\system32\perfi009.dat
C:\Windows\system32\perfh009.dat
C:\Windows\system32\perfd009.dat
C:\Windows\system32\perfc009.dat
C:\Windows\system32\wbem\repository\
C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\CloudAPCache\
C:\Windows\appcompat\programs\amcache.hve
C:\Windows\WindowsUpdate.log
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\
C:\Windows\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\
C:\Windows\system32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\
C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\
C:\ProgramData\Microsoft\SmsRouter\MessageStore\
C:\ProgramData\USOShared\Logs\
C:\Program Files\UNP\SystemLogs\
C:\ProgramData\Microsoft\Network\Downloader\
C:\ProgramData\Microsoft\EdgeUpdate\Log\
C:\ProgramData\Microsoft\Diagnosis\
C:\ProgramData\Microsoft\Windows\WER\
C:\Microsoft\Windows\LfSvc\Cache\
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\InstallService\
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Caches\
C:\Windows\System32\WDI\LogFiles\
C:\Windows\System32\winevt\
C:\Windows\Temp\
C:\Windows\Logs\
@C:\Windows\system32\catroot\{f750e6c3-38ee-11d1-85e5-00c04fc295ee}\
@C:\Windows\inf\
C:\Windows\*\SPP\Store\2.0\
@C:\Windows\*\DriverStore\
C:\Windows\*\drivers\wd\
C:\Windows\*\config\TxR\
C:\Windows\*\catroot2\
C:\Users\All Users\Microsoft\Windows Defender Advanced Threat Protection\
C:\Program Files (x86)\Windows Defender\
C:\Program Files\Windows Defender\
C:\Users\All Users\Microsoft\Windows Defender\
C:\ProgramData\Microsoft\Windows Defender\
C:\Windows\SoftwareDistribution\
C:\Windows\CSC\
C:\Windows\SMSCFG.INI
C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys\
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\
C:\MCSPersonality.ini
C:\Personality.ini
C:\Windows\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0
C:\Windows\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0
 

 

[Sergio Masone1709161115]

On 11/25/2024 at 8:47 PM, Sergio Masone1709161115 said:

Recreated a new layer with the alwaysonboot reg values set , doesnt seem to persist in the final image template, as this is the list of entries in the alwaysonboot that get populated after publishing, It either ignores my nvidia layer with this setting set, or its being overwritten for some reason.

C:\Program Files\Windows Defender Endpoint Advanced Threat Protection\
C:\ProgramData\Microsoft\Windows Defender Endpoint Advanced Threat Protection\
C:\Users\All Users\Microsoft\Windows Defender Endpoint Advanced Threat Protection\
C:\Program Files\Windows Defender Advanced Threat Protection\
C:\ProgramData\Microsoft\Windows Defender Advanced Threat Protection\
C:\ProgramData\Microsoft\EdgeUpdate\
@C:\Program Files (x86)\Microsoft\EdgeWebView\
C:\Program Files (x86)\Microsoft\EdgeUpdate\
C:\Program Files (x86)\Microsoft\EdgeCore\
C:\Program Files (x86)\Microsoft\Edge\
@C:\ProgramData\Microsoft\Windows\AppRepository\
@C:\Program Files\WindowsApps\
C:\Windows\*\LogFiles\LSA\
C:\Windows\*\LogFiles\SAM\
C:\Windows\system32\drivers\mssecflt.sys
C:\Windows\system32\drivers\mssecwfp.sys
C:\Windows\Setup\Scripts\kmsdir\GenRandomQMID.log
C:\Windows\system32\perftmp.dat
C:\Windows\Setup\Scripts\envsetup.log
C:\Windows\Setup\Scripts\ActivateOffice_log.txt
C:\Windows\Setup\Scripts\kmsdir\StartCCMExec.log
C:\Windows\Setup\Scripts\kmsdir\runato.log
C:\Windows\Setup\Scripts\kmsdir\gposetup.log
C:\Windows\Setup\Scripts\kmsdir\kmssetup.log
C:\Windows\system32\perfi009.dat
C:\Windows\system32\perfh009.dat
C:\Windows\system32\perfd009.dat
C:\Windows\system32\perfc009.dat
C:\Windows\system32\wbem\repository\
C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\CloudAPCache\
C:\Windows\appcompat\programs\amcache.hve
C:\Windows\WindowsUpdate.log
C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\
C:\Windows\ServiceProfiles\LocalService\AppData\LocalLow\Microsoft\CryptnetUrlCache\
C:\Windows\system32\config\systemprofile\AppData\LocalLow\Microsoft\CryptnetUrlCache\
C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Notifications\
C:\ProgramData\Microsoft\SmsRouter\MessageStore\
C:\ProgramData\USOShared\Logs\
C:\Program Files\UNP\SystemLogs\
C:\ProgramData\Microsoft\Network\Downloader\
C:\ProgramData\Microsoft\EdgeUpdate\Log\
C:\ProgramData\Microsoft\Diagnosis\
C:\ProgramData\Microsoft\Windows\WER\
C:\Microsoft\Windows\LfSvc\Cache\
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\InstallService\
C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft\Windows\Caches\
C:\Windows\System32\WDI\LogFiles\
C:\Windows\System32\winevt\
C:\Windows\Temp\
C:\Windows\Logs\
@C:\Windows\system32\catroot\{f750e6c3-38ee-11d1-85e5-00c04fc295ee}\
@C:\Windows\inf\
C:\Windows\*\SPP\Store\2.0\
@C:\Windows\*\DriverStore\
C:\Windows\*\drivers\wd\
C:\Windows\*\config\TxR\
C:\Windows\*\catroot2\
C:\Users\All Users\Microsoft\Windows Defender Advanced Threat Protection\
C:\Program Files (x86)\Windows Defender\
C:\Program Files\Windows Defender\
C:\Users\All Users\Microsoft\Windows Defender\
C:\ProgramData\Microsoft\Windows Defender\
C:\Windows\SoftwareDistribution\
C:\Windows\CSC\
C:\Windows\SMSCFG.INI
C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys\
C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\
C:\MCSPersonality.ini
C:\Personality.ini
C:\Windows\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-0.C7483456-A289-439d-8115-601632D005A0
C:\Windows\system32\7B296FB0-376B-497e-B012-9C450E1B7327-5P-1.C7483456-A289-439d-8115-601632D005A0
 

 

I fixed my issue, in the platform layer under the RSD_P1<ID> hive, there was a "AlwaysOnBoot" reg value there with a bunch of weird characther's, which I'm assuming is a delete token, so the nvidia values were not being added because someone most likely tried this in the platform layer, than deleted the reg keys, which made the PL have priority and overwrite the other layers with the same value... after deleting that from the virtual registry, and republishing with that version, the Control panel works as expected, and i can see the "AlwaysOnBoot" nvidia paths are appended to it.