Thanks for mentioning the Legacy/CSM boot mode. That may be relevant to the driver-signing behavior, so I’ll keep that in mind when I reproduce the normal-mode tests. Regarding the NVIDIA Control Panel AppX: on Windows 10 1607 the AppX deployment system is supported, but 1607 LTSB does not include the same App Installer / Store integration as normal consumer editions. That is why double-clicking the .appx package may not work or may not be recognized. On 1607 LTSB, you can install the NVIDIA Control Panel AppX through PowerShell instead: Code: Add-AppxPackage -Path "C:\Path\To\NVIDIAControlPanel.appx" If the package requires dependency AppX files, those need to be installed as well. On normal Windows 10 1607 and newer editions, App Installer may allow installing the package through the GUI. The direct nvcplui.exe extraction method is mainly useful for 1507 and 1511, where the newer AppX package itself cannot be deployed normally. Also, thanks for the new screenshot. It confirms your RTX 3050 is running my 556.12 mod correctly on 1607 LTSB in Test Mode.
Last I checked, this thread was and is entitled: Resolve the issue of Nvidia’s latest win7 driver not working due to the signature！ You've generated lot of discourse here that has only the faintest hint of relation to that topic. Instead of hijacking a thread others (like me) are watching for updates that are actually relevant to the topic, why can't you create your own thread for discussing your own project?
I agree ! There were already discussions about modding Nvidia drivers in the Windows 10 Enterprise (N) LTSB 2016 thread, that started HERE so it could be a good idea to just continue there if you don't want to create a new topic.