Guide: Optimized Image

Hellbovine

Well-Known Member
Messages
1,207
Reaction score
755
January 16th, 2026: A new update has been released, for version 2.0 of the Optimized Image guide. I still need more time to go through all my guides and update the instructions and uploads though, so this is kind of a soft launch. Many people have been patiently waiting, and now that W10 reached end of life Windows Update will unpause itself and run, which will undo some of the previous tweaks. The new guide update adds/deletes/modifies somewhere around 100 keys and is tailored to the latest Microsoft ISO labeled as, Win10_22H2_English_x64v1.ISO downloaded directly from their website. The uploaded tweaks folder contains the new files. I will eventually add a full set of before and after benchmarks to better show people what the benefits of this guide are. Version 3.0 of this guide is also in the works.
--------------------------------------------------​
This guide walks users through the creation of an optimized Windows 10 image designed for maximum performance, with general annoyances and telemetry addressed too. These tweaks have been thoroughly researched and tested to provide a safe and official Windows, suitable for gamers, power users, and everyday usage as well. The guide was tested on Home edition, which means it will work on every edition.

The goal here is to make a highly refined W10 image that can be used for years to come, until developers finally drop support and users are forced to migrate. This is a very popular strategy that countless users have settled on by jumping from XP > W7 > W10, since the in-between releases tend to flop with the masses. To be clear, Windows 11 is a flop with huge bugs, AI bloat, and worse performance.

FREQUENTLY ASKED QUESTIONS
- This guide is for Windows 10 version 22H2, build 19045.2965, but many of these tweaks will work elsewhere if you want to assume responsibility for adapting it to your needs. I won't troubleshoot something majorly off course, such as using Windows 11 with this guide, because it is a different operating system and still evolving, plus it needs tweaks that are not relevant to previous generations.

- Users have limited options in choosing an operating system these days, because companies are onboard with Microsoft's end of life road maps. Major platforms (Steam, Blizzard, Chrome, etcetera) have dropped support for older Windows, and there has been such a hard push between 2023-2025 that everything except Windows 10 and 11 is now obsolete and unsupported by most developers.

- My research and testing indicates that the latest official Microsoft ISO of 22H2_V1 is the best of the options available. While comparing Windows 10 to 11, it is easy to see that Windows 11 scores the same or worse in every benchmark and has higher DPC latency. I plan on testing Windows 10 against 11 again when the performance issues seem to be addressed and will update my guides accordingly. Windows 10 is the current winner though, with the latest benchmarks (link2) here. There's no need for anyone to remind me about Windows 11, as I'm already in the know and will migrate when I feel it's the right time.

- People often ask about using older versions of Windows 10 for performance, and it is time to put that discussion to rest now, as version 22H2 is stable, performs well, and includes some of the DPC latency patches I pushed for in the Nvidia (link3) thread. Older versions of Windows 10 are much buggier and less stable, plus the support for those older releases has been dropped by many game and software developers.

- Most performance enthusiasts pause or disable Windows Update. This guide pauses it forever, but it can be manually started and paused again by the user if desired, but I don't recommend using this feature at all. Instead, the optimal approach is for users to create a new image annually and install that with the latest tweaks I've uploaded, and cleanly install that. This reply (link4) explains things in more detail.

TWEAK METHODOLOGY
We need to define what optimized means, and why this custom Windows is unlike most others on the internet.

- This guide does not focus on component removals, instead it uses registry keys. This method ensures that nothing breaks in Windows, since all the keys are the same official method that Microsoft would use, and these tweaks can be reversed on a live install. No apps have been uninstalled, no dependencies lost, it is just much faster and stable with common annoyances resolved. In other words, Microsoft could release this as a "Gaming" or "Lite" edition of Windows 10.

- Every tweak has been meticulously tested to ensure they work for this operating system and version. They all integrate into a clean install, and apply to all users created too. This is important because many tweaks on the internet are not tested properly, since most people go by feel which is usually placebo. Basically, I try to never include tweaks if I cannot manually confirm they are doing something beneficial.

- This image was constructed in a modular way, meaning you can take pieces from it, or you could use the guide and layer it on top of other NTLite images to enhance one of the built-in templates or a user's custom preset. Always apply the Optimized Image guide after processing all other tweaking you plan on doing though, or else it can undo some of the tweaks in this guide.

- This guide was first posted on August 23rd, 2022 and no issues have been discovered so far. The problems in the thread replies have been determined to be inaccurate or unrelated, which is a common occurrence on forums, since people add their own tweaks and tools while using a guide then randomly place the blame when things break. It is safe to say this image works perfectly when users follow the instructions.

KNOWN ISSUES
There are no known issues with this custom image, but some notes are below.

- The Xbox Game Bar will not run from the start menu, which is by Microsoft's design and is not intuitive. If you need to use the Game Bar just go to Start > Settings > Gaming > and toggle it on, then the Game Bar will run from the start menu.

- Microsoft intentionally alters power settings so that instead of turning off when "Shut down" is clicked, it silently goes to sleep instead. This concept happens to a number of power settings, with many of the overrides being nonsensical. See these posts (link5, link6) for workarounds, until I can figure out how to prevent the overrides. This is Microsoft's fault, and the issues are worse on laptops and W11.

- The Microphone is initially off, but can be turned on by going to Start > Settings > Privacy > Microphone > toggle "Allow access to the microphone on this device" followed by "Allow apps to access your microphone" and then "Allow desktop apps to access your microphone" last. Some programs require all three settings to be enabled.

- I tried to avoid group policy tweaks unless it was required, but I had to use about a half dozen in total. This is not a bad thing, but the downside to policies is that they lock settings so the user cannot toggle them in the Windows interface, until the policy is deleted from the registry. I will work to eliminate all policies in the future.

- Defender and Firewall have been turned off for gamers (easily enabled again), but security is not as scary as some people say. Use a good browser (Chrome), practice common sense (download from reputable sources), and install a good ad-blocker (uBlock Origin Lite) to improve security/performance, while also eliminating ads. Also, do not connect a computer to the internet without a router with NAT enabled.

RELEASE NOTES
August 23, 2022: Released version 1.0 with 584 total registry keys. It took about 640 hours over 8 months to create it, and versions 2.0 and 3.0 are planned out. Quality testing is time consuming, so each new version takes several months or more to complete. If anyone finds any issues, those will be fixed and the guide updated with a minor version change.

December 28, 2022: Updated to version 1.1 after adding a tweak that prevents Windows from forcibly downloading and installing a display driver, even if Windows Update was paused. Also, cleaned up the guide's formatting and added information about the release of 22H2.

January 16th, 2026: Released version 2.0 and included a changelog file in the uploads to document that.

STEP 1: GETTING STARTED
Note: The Optimized Image guide should be applied as the final set of tweaks to an image, because ordering matters in Windows and NTLite. See the Quality Control (link7) guide and Choosing a Preset (link8) guide to learn more.

Before you begin, check that you have everything you need in advance.

1A) Download the attachments. The "Screenshots" folder contains images showing the Task Manager and LatencyMon results. Compared to a stock install, this image has 20% fewer processes, 35% fewer threads, 25% fewer handles, memory usage down to 1.0 gigabyte, and many tweaks that improve the user-experience which do not have a way to be measured by a tool. The "Tweaks" folder contains the layout and registry files. After downloading the folders, right-click and "Extract All" then choose a destination, click "Extract" and delete the original zipped folders.

1B) Exit out of all open programs and reboot.

1C) Temporarily disable any antivirus, such as Defender, since they slow down NTLite and may cause image corruption.

1D) Right-click on NTLite and select "Run as administrator".

1E) In NTLite, click on the "Main menu" button on the top left (signified by 3 horizontal lines), then "Check for updates" and then click the first "Update" button, under the "Tool" header. If it is grayed out then you are on the latest version already.

STEP 2: START MENU, TILES, AND TASKBAR
This step prevents all the bloat from getting installed, such as games and apps you did not ask for, and other ads and sponsored software. You can still use live tiles and customize that panel, this tweak just cleans up the stuff that many users do not like.

2A) Load an unmodified, official, Windows 10 image into NTLite by going to "Add" then choosing "Image directory" and select the Windows image folder you want to use and NTLite will refresh. Now double-click on "Windows 10 Home" or whichever edition you have a license for and it will begin loading. If you do not have an image, check other guides (link9) for instructions.

2B) After the image has finished loading it automatically moves into the "Mounted" section, which means we can begin editing. Right-click on the "Windows 10 Home" that has a green circle and select "Explore mount directory".

2C) Left-click twice in the blank space of the address bar, to the right of "NLTmpMnt" and add the following text exactly as shown below:

\Users\Default\AppData\Local\Microsoft\Windows\Shell\

Make sure it is one long address now, combined with the previous address, and no white spaces between anything, then press enter and it should take you to a folder that has 1 file inside.

2D) Next, copy and paste the DefaultLayouts.xml and LayoutModification.xml files into this mounted Shell directory, choose the option to "Replace the file in the destination" when prompted, and then hit "Continue" on both screens to approve the action.

2E) Exit the mounted shell window now, but leave NTLite open.

STEP 3: UPDATING POWER PLAN
This registry file is going to be integrated into all four parts of the Windows image (Install, PE, Setup, Recovery) which changes the default power plan from Balanced to High performance in each of those. This greatly increases the speed at which Windows installs, reducing the total time by about 50%. This also fixes a bug in Windows which causes some older SSDs to hang or be extremely slow during Windows Setup.

3A) Click "Registry" from the left menu, then "Add", choose "Registry files" and select the Reg_0_Setup file you downloaded earlier and NTLite will refresh to show that those keys were added.

STEP 4: UNINSTALL COMPONENTS
This step is optional, but I strongly urge everyone to do it. Here we are removing the only component in this guide--OneDrive. There are several reasons to do this, the biggest one being that it is a resource hog, and it is not integrated into Windows, instead it is a standalone installer that gets added to Windows when the first user is created.

Even if you want OneDrive, it is better for users to directly access the OneDrive cloud via their web browser than to use the app, because the app adds substantial resource usage to the background of Windows, and you will inevitably experience syncing issues and/or file corruption. It makes more sense to adjust how you use OneDrive, than it does to try and optimize this unnecessary app.

4A) Click "Components" from the left menu, then expand the "Remoting and Privacy" tree and also expand "Cloud Files API" so that you can now uncheck "OneDrive".

Note: This is the only tweak that require a paid NTLite license, while everything else works on the free edition. However, a license is worth it, because it gives you more power to do additional component removals and such. You will also be supporting the huge amount of work that has gone into the NTLite program, while indirectly supporting the volunteers, since the community and tool grow in relation to each other.

STEP 5: APPLY AND PROCESS (PART ONE)
At this point we are done with the first set of tweaks and ready to process this image into something we can install Windows with. You could stop after this step and have a great base image to do your own tweaking with, or continue with this guide.

5A) Click "Apply" from the left menu, then select "Save the image and trim editions" which will eliminate all the unused editions, such as Pro, Education, and Workstation, without affecting the edition that you have currently loaded in NTLite.

5B) Now expand "Reapply tasks across editions" and check the box for "Integrate - Registry".

5C) On the top left menu bar select "Process" to begin creating the customized image.

Note: It will take several minutes to process the image and a message will appear when complete. Do not try to combine this step with the ones below. It is best practice to integrate registry keys after processing the removal of components, otherwise it can undo some tweaks.

STEP 6: IMPORT REMAINING REGISTRY FILES
To finish this custom image, we need to take the previously processed image and add a few more layers into it.

6A) Click "Image" from the left menu, then double-click on the same "Windows 10 Home" option from earlier to load it again, and it will now include all the tweaks we added. If you previously stopped after step 5C and are returning to this guide to add more tweaks, the image may not be visible in NTLite, so you may need to repeat step 2A again. After it loads, click "Registry" from the left menu and then continue below.

6B) Click "Add" and choose "Registry files" to select "Reg_1_Power" for integration. Repeat this step until Reg_2_Security, Reg_3_Settings, Reg_4_Control, Reg_5_Apps, and Reg_6_Other are all added.

Below are highlights of the tweaking each file does. Right-click and edit a registry file from within Windows File Explorer to read the comments inside. If you do not want a certain tweak, simply delete them from the files before integrating them. I highly recommend trying everything as-is for a week though, to give this curated product a fair try, so that you can see how it was intended to be.

Reg_1_Power: Disables hibernation (saves several gigabytes of space, while still keeping sleep available), disables fast startup, converts the High performance power plan into a better version of Microsoft's Ultimate and Bitsum's power plans. All of the power saving features are a big reason modern operating systems perform worse than older ones, like XP.

Reg_2_Security: This file has to do with the Windows Security center app, it disables Defender, firewall, and many of the security features which interfere with gaming, especially multiplayer. This is where most gaming issues come from, and is the reason why older operating systems performed better overall, because they lack these features.

Reg_3_Settings: All of these are options a user can toggle from within the Windows Settings interface. There are tweaks that fix DWM and theme management in Windows, disables Microsoft syncing, disables telemetry, pauses Windows Update out of the box and extends it.

Reg_4_Control: Everything inside this file has to do with settings in the Windows Control Panel. A lot of annoyances are addressed here, such as disabling user tracking, organizing the user interfaces, basic keyboard and mouse tweaks for gamers, and disables UAC nagging.

Reg_5_Apps: This file contains the settings that handle all the apps and stops them from running in the background, but still allows them to work in case someone actually wants to use any of them.

Reg_6_Other: Miscellaneous settings are here, such as desktop and taskbar tweaks. It disables prefetch, disables superfetch, disables indexer, disables file compression, and a number of other similar tweaks.

STEP 7: APPLY AND PROCESS (PART TWO)
For the last step all we have to do is process the addition of these remaining registry files.

7A) Click "Apply" from the left menu, then select "Process" to begin creating the image.

7B) Once processing has finished, exit NTLite and copy the Windows files onto the root of a USB drive, then boot into that drive and install your custom Windows! If you are unfamiliar with this, see my other guide (link10) for instructions on how to do it.

Note: Unplug from the internet before installing Windows or it will force you to use a Microsoft account during setup, as well as potentially downloading updates that could undo some tweaks. This will be resolved in a future update of this guide.

Visit the Gaming Lounge to find more guides like these.
 

Attachments

Last edited:
ernesto7, I do not have Windows 8.1 to test, sorry.

Windows 8.1 reaches end of life on January 10th, 2023. I talk more about the operating systems in the introduction to this guide. If you want to test this optimized image on 8.1 though, it would only take a couple of hours, since all the registry keys are commented on what they do and tell you where to find the settings.

Also, here is some data to consider:
https://store.steampowered.com/hwsurvey/Steam-Hardware-Software-Survey-Welcome-to-Steam

Steam has over 120 million users, and of those, 69.06% of them are on Windows 10 64-bit, while 23.78% of them are on Windows 11 64-bit, with just 00.51% on Windows 8.1--This is the type of data that companies are using to determine when to drop support. It is getting harder these days to stay on older operating systems than it was in the past.
 
Last edited:
I see virtual memory off in the registry. I think this option is wrong, virtual memory can be set to auto, but he can't be without.
Some games use virtual memory, for example: Chinese online games, https://www.yjwujian.cn/

The computer memory is 16GB, and I set the virtual memory to 16GB. The game will use 30%~40% of the virtual memory all the time. In-game usage has not been calculated yet.

World of Tanks, requires 1.8+% in game

Virtual Memory Guidelines https://www.minitool.com/lib/virtual-memory.html
 
As a rule, virtual memory should be equal or larger than physical memory. Sometimes, performance increases when you add more virtual memory (not because it's required), but because Windows assigns some resources based on percentage. The larger the virtual memory, the more it will assign to specific memory buffers.

But increasing it too much will stop making a difference. 1.5X - 2X of physical memory is usually a good rule.
 
As a rule, virtual memory should be equal or larger than physical memory. Sometimes, performance increases when you add more virtual memory (not because it's required), but because Windows assigns some resources based on percentage. The larger the virtual memory, the more it will assign to specific memory buffers.

But increasing it too much will stop making a difference. 1.5X - 2X of physical memory is usually a good rule.
Yes, virtual memory can be automatically managed, Microsoft only gives a very small amount. But he cannot do without, because some software really needs the existence of virtual memory.
 
I went through all the registry notes, what I call basic settings.
Thank you for taking the time to look through it all. The goal of version 1.0 was to get a safe and effective baseline to calm down the OS, without breaking anything. I've got a ton more planned for v2.0 and 3.0, but because I test and research all the keys first, it just takes a long time to get through thousands of keys. More often than not stuff turns out to be snake oil, or is highly circumstantial and so it doesn't make the cut.

If you have registry keys that you really like, and you didn't see them here, please send them my way! If you could mail me them through the forum I'd appreciate that, and will add them all to my todo list.
 
Last edited:
Thank you for taking the time to look through it all. The goal of version 1.0 was to get a safe and effective baseline to calm down the OS, without breaking anything. I've got a ton more planned for v2.0 and 3.0, but because I test and research all of the keys first, it just takes a long time to get through thousands of keys. More often than not stuff turns out to be snake oil, or is highly circumstantial and so it doesn't make the cut.

If you have registry keys that you really like, and you didn't see them here, please send them my way! If you could mail me them through the forum I'd appreciate that, and will add them all to my todo list.
I like it very much.
Looking forward to your next 2.0~3.0
Follow your ideas, send it to you now will increase your troubles, believe me, I have experienced it.
 
Last edited:
Re: Pagefile

This is a discussion that has been around for ages, and tends to be a polarizing topic, so I'm just going to give a quick summary and then some options for everyone, that way they can choose what's right for them. If anyone wants to discuss it in depth though, I'd be happy to start a dedicated thread we can all dive into.

The vast majority of all programs, including Windows, run perfectly without a pagefile. It is not best practice, nor is it common practice, for a program to absolutely require a pagefile to function. It is safe to disable the pagefile, and is something countless gamers and performance enthusiasts have done forever. However, there's always some developer out there that wants to be difficult, so we need solutions for those cases.

Windows gives you three options for the pagefile. It can be disabled, set to a static size (non-changing), or set to a dynamic size (adjusts automatically). Manually changing the pagefile through the Windows user interface is really easy, just follow this navigation:

Start > Settings > System > About > Advanced system settings > Advanced > Performance (Settings) > Advanced > Virtual memory

If you prefer registry keys instead (useful for integrating into an image or a post-install script), I made those options available below:

; Disable Pagefile
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):00,00,00,00

; Static Pagefile 2048-2048 (2 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,32,00,30,00,34,00,38,00,20,00,32,\
00,30,00,34,00,38,00,00,00,00,00

; Static Pagefile 4096-4096 (4 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,34,00,30,00,39,00,36,00,20,00,34,\
00,30,00,39,00,36,00,00,00,00,00

; Static Pagefile 8192-8192 (8 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,38,00,31,00,39,00,32,00,20,00,38,\
00,31,00,39,00,32,00,00,00,00,00

; Static Pagefile 16384-16384 (16 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,31,00,36,00,33,00,38,00,34,00,20,\
00,31,00,36,00,33,00,38,00,34,00,00,00,00,00

; Static Pagefile 32768-32768 (32 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,33,00,32,00,37,00,36,00,38,00,20,\
00,33,00,32,00,37,00,36,00,38,00,00,00,00,00

Note: I cannot recommend a dynamic pagefile (automatic) because it leads to unecessary fragmentation and resource usage as it shrinks and expands. I also cannot guarantee these hex keys work on anything other than Windows 10, which is what this guide is written for. You will need to reboot after changing the pagefile.
 
Last edited:
Re: Pagefile

This is a discussion that has been around for ages, and tends to be a polarizing topic, so I'm just going to give a quick summary and then some options for everyone, that way they can choose what's right for them. If anyone wants to discuss it in depth though, I'd be happy to start a dedicated thread we can all dive into.

The vast majority of all programs, including Windows, run perfectly without a pagefile. It is not best practice, nor is it common practice, for a program to absolutely require a pagefile to function. It is safe to disable the pagefile, and is something countless gamers and performance enthusiasts have done forever. However, there's always some developer out there that wants to be difficult, so we need solutions for those cases.

Windows gives you three options for the pagefile. It can be disabled, set to a static size (non-changing), or set to a dynamic size (adjusts automatically). Manually changing the pagefile through the Windows user interface is really easy, just follow this navigation:

Start > Settings > System > About > Advanced system settings > Advanced > Performance (Settings) > Advanced > Virtual memory

If you prefer registry keys instead (useful for integrating into an image or a post-install script), I made those options available below:

; Disable Pagefile
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):00,00,00,00

; Static Pagefile 2048-2048 (2 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,32,00,30,00,34,00,38,00,20,00,32,\
00,30,00,34,00,38,00,00,00,00,00

; Static Pagefile 4096-4096 (4 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,34,00,30,00,39,00,36,00,20,00,34,\
00,30,00,39,00,36,00,00,00,00,00

; Static Pagefile 8192-8192 (8 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,38,00,31,00,39,00,32,00,20,00,38,\
00,31,00,39,00,32,00,00,00,00,00

; Static Pagefile 16384-16384 (16 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,31,00,36,00,33,00,38,00,34,00,20,\
00,31,00,36,00,33,00,38,00,34,00,00,00,00,00

; Static Pagefile 32768-32768 (32 GB)
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\Memory Management]
"PagingFiles"=hex(7):63,00,3A,00,5C,00,70,00,61,00,67,00,65,00,66,00,69,00,\
6C,00,65,00,2E,00,73,00,79,00,73,00,20,00,33,00,32,00,37,00,36,00,38,00,20,\
00,33,00,32,00,37,00,36,00,38,00,00,00,00,00

Note: I cannot recommend a dynamic pagefile (automatic) because it leads to unecessary fragmentation as it shrinks and expands. I also cannot guarantee these hex keys work on anything other than Windows 10, which is what this guide is written for. You will need to reboot after changing the pagefile.
In today's SSD use, there is no need to care about fragmentation.
 
It's not just fragmentation you have to consider, it costs resources to adjust the pagefile too, it's a literal file that sits on the drive and it's not free, it has consequences in the form of overhead. If you need a pagefile, a static pagefile gives you the exact same functionality as auto, but without constantly adjusting the file on the disk. This is why I didn't want to dive into it here, because there's far more nuances to consider than just the regurgitated articles on the web.
 
Pagefile is absolutely required if you expect to capture BSOD (blue screen) dumps, to analyze why your device driver or kernel exception has crashed the system. Most people DGAF about it. It's well known Windows can run w/o any pagefile, but it's not the NEED for a pagefile that matters but you cannot increase virtual memory without a page file present. That's not how operating systems work.

Again, if you have a percentage-based resource allocation and it's not based on a fixed value -- how else are you going to adjust that setting?
 
  • Like
Reactions: sbz
On spinning disks, it's not so much fragmentation but inefficient disk seek if your pagefile wasn't allocated all at once. When Windows first installs, its creates a continuous pagefile so the probability of random seek is very small. If you assign or resize the pagefile later, on a "dirty" system then there's no guarantee the new pagefile's blocks are near each other. Thus increasing random seek.

Now if you have the crappiest 5400 RPM laptop drive, it matters more than a M2 SSD drive. These are all guidelines; without understanding OS design principles, you can always argue for one advice or another unless you know exactly how the system is built.
 
I am interested in what everyone has to say, I'm open minded and will gladly go back to the drawing board and re-test things and do further research. I just don't want to keep discussing pagefile in this thread, because it will undoubtedly spawn many pages of replies since it has historically been a hot topic. Let's please continue over here:

https://www.ntlite.com/community/index.php?threads/pagefile.3099/
 
Last edited:
Hello! I will now test your method, because in my opinion the gameros preset is too aggressive. I will then tell you about my experience.
 
Here I am again! In the meantime I was able to purchase a Windows 10 LTSC 2021 license and got a suitable ISO. What improvements do you think I could adopt from your guide?
 
Here I am again! In the meantime I was able to purchase a Windows 10 LTSC 2021 license and got a suitable ISO. What improvements do you think I could adopt from your guide?
I've never used an LTSC version myself, but most, if not all of the registry keys should work still, since I designed everything around Home edition, which is the most difficult version to work with. It's unlikely you will come across something that works for Home edition, but doesn't work on others, as it's usually the other way around.

The big difference most people notice with LTSC versus Home/Pro is that it comes already stripped down quite a bit, so there isn't nearly as much stuff running in the background by default, compared to other editions, which just makes it easier and faster to tweak and reach a place you're satisfied with. The only real reason LTSC isn't more popular is just because of how difficult it is to acquire a legitimate copy.
 
Okay I'll try some of your tweaks.

LTSC just wasn't that hard to come by. The license cost me about $35. In my opinion Windows should only be sold like LTSC. Windows 10/11 by default are really a disaster.


Unfortunately you are right! For gaming you need Windows, because Linux is just not really suitable for it. Even though it has gotten better thanks to Proton, there are always problems with performance, stability and generally one has to hope that the game will run.
 
Back
Top