My advise - keep, at least, WindowsStoreClient (only back-end component of the Store) and DesktopAppInstaller (correct me if I missed something) This time you were lucky with NVCPL. The message from @shhnedo to you was absolutely correct (if you want have a deal with other DCH drivers or offline apps installations in the future). For example, Synaptics TouchPad driver (DCH) for some NB models or whatever else might need Store infrastructure working (at least, basic functionality).
@evildjkay He may be a high-end gpu user, which more often than not means that he'll benefit from newer drivers, and newer drivers are currently(and will only be) offered in DCH package.
I kept the two components you kindly advised me to retain and rebuilt my x64 image and reinstalled it on my spare SSD. This time Windows 10 21H1 x64 Enterprise installed NVCPL automatically. I then tried to use NVSlimmer v0.12 to install 496.49-desktop-win10-win11-64bit-international-dch-whql. When I pressed the "Install NvCpl" button I still received the message "You'll need a new app to open this ms-windows-store link". NVCleanInstall was able to install NVCPL without issue.
AVs will be triggered by lots of files these days, when you know the source and its intentions, consider it a false positive.
@Feartamixg That's a good question. Now I can recall that I had such messages too. Probably we need some other components besides WindowsStoreClient and DesktopAppInstaller to do installations via UI. While PowerShell commands do the job. But you always must prepare a proper command that sometimes may need possible dependent packs, licenses, etc. (not handy, but works in most cases without that stuff). I'm too would like to know other dependent components / working config and how to achieve back-end to work via UI without Store itself. That's an old issue, may be @MSMG can give us some advises. Summary, M$ apps it's a true a$$pain I hate very much. And shame to NVIDIA, btw (for their telemetry, overbloat and now for the apps s**t).
@ ALL Seems like I was right requesting ASAP support for the Server 2022 LTSC. Make the right conclusions. And later don't say you didn't know. I beleive Server 2022 LTSC should be one of main goals for Toolkit development in this case. (On my opinion).
@Yanta When you move from classic drivers to DCH, you MUST remove everything fIrst time + REBOOT. For this "exodus" I highly recommend to use DDU (one time) for cleaning OS from old classic drivers. Then install DCH drivers. From our discusson above I can resume that very new DCH drivers now containing NVIDIA Control panel. If still error, give people a PowerShell command to install. Or, at least, they may prepear / install package using working "NVCleanInstall" software. Yes, this is because of trimmed Store. P.S. (about future life with apps / future ISO configs) As I said before, it would be nice to know working config of the Store back-end component (plus the rest dependent parts) for successful apps installation over UI... Then trimmed OS without Store will (should) install apps as usual (as designed by M$ by default, but offline). (Or it may appear impossible and trimmed OS with back-end by @MSMG anyway need PowerShell commands). Lets ask @MSMG
I'm sorry if this is a little off topic, but wasn't the point of Microsoft forcing vendors to split their drivers to force people to use their store? I know they ranted on about how it was more secure or some such, but that just sounded like Microsoft double-speak. So if the latest dch drivers include the control panel what do we need the store for? Or perhaps I should ask it this way - if the dch drivers include the control panel what is the difference between dch and standard? I've downloaded the latest dch, and I've got the appx bundle from store-rg-adguard.net. I agree, ddu to uninstall the first time. Then install in normal mode. Will give it a try and see what happens. thanks