Before you hand out a script like that, it might be worth going over what its actually doing.
One that immediately stands out is this:
setx PackagesDirectory “C:\MSFS” /M
What does that do, and more to the point what does it do if that isn’t your packages directory?
I don’t have that environment variable set, and the sim works for me, so what does that actually achieve?
This command doesn’t exist:
powercfg-duplicatescheme
But this does:
powercfg /duplicatescheme
That commands creates a new power scheme. Without looking it up I assume that GUID is a known one because what I have now is this, second from bottom is “(Ultimate Performance)”:
powercfg /list
Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High performance) *
Power Scheme GUID: 9586727e-69c1-49d0-89ef-ec5792e71457 (Ultimate Performance)
Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a (Power saver)
The next command, to set it to active, will most likely fail because you can see that what the previous command did is “duplicate” that GUID that refers to “Ultimate Performance” into a new power scheme with a different GUID. Without knowing what that new GUID is going to be, there is no way that command could be listed…unless you could refer to it by its description instead of its GUID.
The time to wait before initiating a forced shutdown of applications is specified by the following registry key. HKCU *Control Panel* *Desktop* *HungAppTimeout*
This alters the delay before a menu appears
WaitToKillAppTimeout
When shutting down, how long Windows waits, in milliseconds, before killing an unresponsive task.
This key contains a REG_DWORD value named SystemResponsiveness that determines the percentage of CPU resources that should be guaranteed to low-priority tasks.
Still working through them, but so far most of these are just going to make changes to the way OS handles background tasks, and some UI performance increases, so not must MSFS specific performance gains.
“MinVmProcessorCount”
“MinVmMemoryCount”
No hits for these ones at all, which is quite rare.
There is an enormous amount of confusion on the internet regarding this function. The setting only affects the portion of the kernel known as the executive, and then only to the portions that are pageable. There are other parts of the kernel that are completely unaffected by this setting.
If you have a “decent” amount of RAM, this setting will have no effect.
And from the OS itself:
fsutil behavior set disableLastAccess
Usage: fsutil behavior set disableLastAccess <0-3>
Controls if file systems will update the Last Access Time when a file is
read.
Values: 0x0 - User Managed, Last Access Time Updates ENABLED
0x1 - User Managed, Last Access Time Updates DISABLED
0x2 - System Managed, Last Access Time Updates ENABLED
0x3 - System Managed, Last Access Time Updates DISABLED
- When "System Managed" is enabled it allows the system to enable/disable
last access time updates based on system policy.
- When group policy controls this setting the "System Managed" state can not
be set and is not displayed.
This operation takes effect immediately (no reboot required)
This could make a tiny amount of improvement to the speed at which files are accessed on disk, as it won’t write to this attribute each time a file or folder is accessed.