
Windows does a loooot of testing, as they must (remember they’re forcing us to download these patches whether they work or not!).

and ENBHost.exe could access up to 4 GB of memory (RAM and VRAM). If you were on Windows 8/10, TESV.exe could access up to 4 GB of VRAM (I think). ENBHost.exe could hold things that TESV.exe could use, freeing up VRAM and generally making the game run more smoothly.

What this means is … if you were on Windows 7 (where it worked correctly), TESV.exe could access all your VRAM, and ENBHost.exe could access up to 192 GB of memory (RAM and VRAM). We recently received news (via screenshots of a reddit private conversation) that Windows devs have confirmed a patch for the dx9 VRAM allocation bug in Windows 8/10 and that it will be in the next insider build.
