VIP 2.0 Custom Content Location Bug (Win10x64)

Setting a custom location for content is not recognized by VIP. Using Process Monitor, I see VIP try to read the "pluginmaps" folder from the default location (C:\ProgramData\VIP\pluginmaps). Custom location was set during install and verified as set in registry key ("pluginmapsPath" @ HKLM\SOFTWARE\VIP\2.0). Tested only on VIP 64-bit (not 32-bit) under Win10 Pro 64-bit. Moving "pluginmaps" folder back to default ProgramData folder from Documents allows maps to be used once again. This is a problem for users who do not want the >1GB folder stored on what could likely be a very small SSD system drive.
1 person has
this question