A technical writer's notes and PowerShell scripts for optimizing a new Windows 11 Pro PC for VFX workflows.
- Perform initial benchmarks
- Manually uninstall middleware
- Run VFX.ps1
- Perform manual optimizations
- Perform midway benchmarks
- Install RTX 3060
- Set up scratch/cache SSD
- Configure Substance and Resolve
- Perform final benchmarks
The scripts are documented in-place. The best way to understand what optimizations are performed & why is to read the .ps1 files, starting with VFX.ps1.
VFX.ps1 contains a list of$Subscripts. I tried to keep each one tightly focused so they're easy to comment out and skip. Broadly, the subscripts fall into 2 categories - common and build-specific.
Common optimizations for any Windows 11 PC:
- These are Group Policies and Registry keys that set/disable many of the controls available in the Settings app.
- Aimed at disabling telemetry and background permissions.
- Include common GUI preferences for the Start menu, Taskbar, and File Explorer.
Build-specific optimizations:
- These include Group Policies, Registry keys, Services, and Tasks.
- Aimed primarily at Intel Core Ultra 7 265K and the Arrow Lake tile architecture.
- The Registry keys target options that are in obscure places or not exposed by a GUI.
VFX.ps1 has a few handy features:
- It can backup
.regand.polfiles. - It can set a System Restore point.
- It has a validation mode that's useful both after running the script for the first time, and after Windows & other updates.
- It creates human-friendly logs with helpful information about the optimizations performed.
VFX.ps1 doesn't perform every optimization needed for the best VFX experience - manual configurations are required.
VFX.ps1 does not de-bloat Windows Apps or 3rd-party stubs. Installed middleware varies greatly depending on the vendor and OS build. I decided it was easiest and fastest to simply uninstall what was present on my specific build.
VFX.ps1 is aimed at a solo VFX workstation with 1 user. It doesn't deal with networking or enterprise-type configurations or optimizations.
VFX.ps1 does not create ghost keys (directories). While it's normal to add missing values (!properties), the key paths exist even on clean installs. A missing path almost always indicates a typo or case of mistaken identity.
- See Console.ps1 for command line exploration of keys, tasks, and services.
| Category | Tool | New OS | Post Script | Post RTX |
|---|---|---|---|---|
| DPC Latency | LatencyMon | 616µs | 112µs | 140µs |
| CPU Clocking | Cinebench | 1941 pts | 7823 pts | 7728 pts |
| GPU | Cinebench | NA | NA | 34686 pts |
| Random 4K I/O | CrystalDiskMark | Read 62.6 MB/s | Read 79 MB/s | 74.2 MB/s |
| Write 43.3 MB/s | Write 143.1 MB/s | 142.0 MB/s |