Use the Task Manager to see how much memory the current cell is actually using in EnbHost.exe. Just don't pretend that it will actually cache more data because you give it a big number. So, my advice for 8GB of RAM is to ignore STEP's recommendation and set VideoMemorySizeMB to a large value such as 4096. The only thing setting it to a value smaller than it needs will accomplish is to force the data to be loaded from disk instead of the cache. Any value larger than one cell's worth of data won't have any affect anyway. If your organization is setting up BitLocker with Intune for the first time, you can test it with a pilot group. In this step, we will deploy BitLocker policy by assigning it to devices. It often went over 2GB but never got close to 3GB. In Step 1, we created BitLocker policy in Intune and in Step 2, we configured the BitLocker policy settings.

Then, as you run around, it loads data to VRAM from the cache instead of disk. With DisablePreloadToVRAM=false, every time there is a cell transition (loading screen) EnbHost.exe discards the entire cache and loads the cache with all data for the new cell - up front.

I used Task Manager to see how much memory EnbHost.exe was using. Neither of STEP's recommendations really make sense to me.

Step enb settings