Win10 IoT: Persisting User Registry Settings

Tagged: , ,

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #107720
    coligher
    Participant
    • Total Post: 5
    • Newbie

    Hello!

    I am trying to figure out how to persist registry settings in the HKEY_CURRENT_USER hive across reboots on Win10 IoT thin clients.

    I have carved out several exclusions in the UWF for monitor settings, time zones, etc., but those are all HKEY_LOCAL_MACHINE settings so adding UWF exclusions is easy.  However – Microsoft documentation states that you cannot add UWF exclusions for the HKEY_CURRENT_USER or HKEY_USERS sections of the registry.

    Specifically, I am trying to allow some VMware Horizon client settings to persist – these particular settings write their preferences to the HKCU:\Software\VMware, Inc. key and subkeys.

    What I don’t want to do is hard code these settings, nor do I want to have to turn off the UWF for production thin clients.  These clients are Wyse 7020QQ and 5070 running Win10 IoTE versions 2015 LTSB and 2019 LTSC respectively.  They are managed by WMS.

    Has anyone come up with a solution to allow HKCU settings to persist?

     

    Thanks!

    Chris

    #107724
    EyeZeek
    Participant
    • Total Post: 10
    • Regular Joe
    • ★★

    Hey Chris, unfortunately there doesn’t seem to be a method that I’ve found to do this. UWF seems to only support HKLM exclusions and that’s likely not to change. Kind of a shame tbh.

    #107726
    coligher
    Participant
    • Total Post: 5
    • Newbie

    Thanks for your reply.  That is too bad.

    I’ve been poking around in the UWF docs, and I was going to try a workaround with a logoff script that would commit certain settings, but according to comments I found on github, it appears to be unwilling to touch HKCU settings even on a manual commit.

    Oh well – users are going to just have to unpin the connection bar every time they log in. 🙂

    Thanks,
    Chris

     

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.