Windows 10 IoT LTSB and UWF / removing volume from UWF configuration RRS feed

  • Question

  • Back in WES7/FBWF times there was a possibility to permanently delete volume configuration from FBWF by using

    FBWFMGR /removevolume V: 0|1

    Now, with UWF there seems to be no way to remove volume, only to un-protect it, but it will still listed in UWFMGR. Am I missing something? Even a way to delete all UWF configuration will do.

    For example UWF_Volume.Unprotect documentation says:

    "Unprotecting the volume does not remove the UWF_Volume entry or any configuration settings from the UWF configuration registry. This means that you can unprotect a volume, and then protect it again later, while keeping any file exclusions or volume configurations that you have defined."

    Thursday, October 17, 2019 2:10 PM

All replies

  • Hello MKN_RM,

    You might try to run the command 'uwfmgr.exe Volume Unprotect <volume>' on your device.  This command will remove the specified volume from the list of volumes that are protected by UWF. UWF stops protecting the volume after the next system restart. At the same time, this command will update the UWF_Volume.Unprotect configuration setting.

    Best Regards,


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Monday, October 21, 2019 3:27 AM
  • Hello Michael,

    I'm sorry, have you tried to read my question? Let me quote myself:

    "Now, with UWF there seems to be no way to remove volume, only to un-protect it, but it will still listed in UWFMGR."

    The key for me is to remove any signs that some volume was protected at some time in the past and so remove clutter from the uwfmgr status output.

    BTW: current uwfmgr status is significantly less readable and requires carefull inspection of all contents to find out what is the current state of the filter. Having multiple unprotected volumes from the past makes it even less readable.

    fbwfmgr from WES7 on the other hand was so much easier, just a quick glance was enough - short output - the filter is off, long output - the filter is on.

    • Edited by MKN_RM Monday, October 21, 2019 12:28 PM
    Monday, October 21, 2019 6:20 AM
  • OK, for all of you looking for an answer - I managed to find out the location of the UWF configuration in registry. Go to HKLM\SYSTEM\CurrentControlSet\Services\uwfvol\Parameters\Static\Copy0\Volumes and you'll find there keys 0, 1, 2 etc - depending on how many drives have been already added to the UWF configuration. There's also a value named NumVolumes which holds numer of keys.

    Then there's HKLM\SYSTEM\CurrentControlSet\Services\uwfvol\Enum with similar values and two more values: Count and NextInstance.

    What I did is deleted all these 0, 1, 2 etc and set the mentioned counter values to 0. It seems that part of registry is not protected by UWF, so it doesn't have to be disabled.

    Of course, this is editing the registry, so be careful and expect that some side effects might occur (although I haven't noticed anything).

    Friday, December 6, 2019 9:15 AM