Recommended Posts

Delete all files from "C:\Windows\SoftwareDistribution\Download", I always do that and no harm is done, it's where windows downloads updates (setup files).

You can also reduce hibernation file, run cmd as admin and type "powercfg ?h ?size 50%", or disable it completely if you don't use it "powercfg ?h off".

Delete all files from "C:\Windows\SoftwareDistribution\Download", I always do that and no harm is done, it's where windows downloads updates (setup files).

You can also reduce hibernation file, run cmd as admin and type "powercfg ?h ?size 50%", or disable it completely if you don't use it "powercfg ?h off".

Thanks for the suggestion about the software distribution download folder. I already did reduce the hibernation file, it used to like 12GB before. :p

  • Like 1

I am not sure if you have done this already, but try Disk Cleanup to get rid of anything left over from a Windows 8 upgrade process, or installation temporary files, and all those system related files you do not need.

I think when I did the Windows 8 upgrade, I was able to clean out 15-20GB from Disk Cleanup.

Did you disable the paging file? With an SSD, the paging file is a waste of space.

I'm not sure I follow you there. The paging file is to swap things to and from ram. If you have enough ram ok fine, disable it. However, an SSD alone is not a reason to disable it.

Maybe you meant indexing?

  • Like 2

I'm not sure I follow you there. The paging file is to swap things to and from ram. If you have enough ram ok fine, disable it. However, an SSD alone is not a reason to disable it.

Correct.

I'd argue to leave the page file on the SSD, why page data from your super-fast RAM into your slower hard drive? Sounds like a performance hit.

You should probably leave the page file enabled IMO.

create a new shortcut that goes to "%SystemRoot%\System32\cmd.exe /c cleanmgr /sageset:65535 & cleanmgr /sagerun:65535" and run it as administrator. it's a more comprehensive version of disk cleanup. but don't check the Windows ESD Files - that's the refresh windows files.

Correct.

I'd argue to leave the page file on the SSD, why page data from your super-fast RAM into your slower hard drive? Sounds like a performance hit.

You should probably leave the page file enabled IMO.

That's not how it works...

Even if you turn the paging file off, Windows will allocate temporary space if it's needed.

The OP's sig says he has 12GB of RAM, so more than likely, Windows created a ~6GB paging file, which is basically wasted space.

On a regular HDD, disabling the paging file may cause your system to hang if Windows tries to allocate space, due to the long access times of HDDs. That problem doesn't exist on a SSD, so disabling it does nothing except save space.

I've disabled the paging file on all my PCs for years and years and never had a single problem.

The OP asked on how to save some space, and this is the simplest way to gain back a large chunk.

That's not how it works...

Even if you turn the paging file off, Windows will allocate temporary space if it's needed.

The OP's sig says he has 12GB of RAM, so more than likely, Windows created a ~6GB paging file, which is basically wasted space.

On a regular HDD, disabling the paging file may cause your system to hang if Windows tries to allocate space, due to the long access times of HDDs. That problem doesn't exist on a SSD, so disabling it does nothing except save space.

I've disabled the paging file on all my PCs for years and years and never had a single problem.

The OP asked on how to save some space, and this is the simplest way to gain back a large chunk.

No, Windows does not allocate temporary space if needed. This is myth.

Windows will simply fail malloc requests once OOM - this causes hilarious issues with poorly coded software.

Also, I have no idea how to use more than 9GB RAM.

Even running the worst coded game of all time (Minecraft - ~7GB RAM), doesn't send me to 10GB.

So the page file is not needed.

No, Windows does not allocate temporary space if needed. This is myth.

Windows will simply fail malloc requests once OOM - this causes hilarious issues with poorly coded software.

Also, I have no idea how to use more than 9GB RAM.

Even running the worst coded game of all time (Minecraft - ~7GB RAM), doesn't send me to 10GB.

So the page file is not needed.

I fill up every bit of my 16GB when I use Adobe After Effects and some very very very large Photoshop documents like to take up quite a bit of RAM too. Would you leave page file turned on in those cases?

I would not say Minecraft is the worst coded game of all time. At least it runs. Last time I tried playing The Amazing Spiderman on Steam, it crashed every 30 minutes. I gave up fighting with it. I wasted $60.

I fill up every bit of my 16GB when I use Adobe After Effects and some very very very large Photoshop documents like to take up quite a bit of RAM too. Would you leave page file turned on in those cases?

I would not say Minecraft is the worst coded game of all time. At least it runs. Last time I tried playing The Amazing Spiderman on Steam, it crashed every 30 minutes. I gave up fighting with it. I wasted $60.

turning off page file is stupid in every case. there's a reason Windows doesn't already disable it automatically when it detects certain conditions, and the people who designed it that way sure as hell know a lot more about how Windows works than random people on the internet that repeat decades old snake oil advice. like _Alexander said, disabling the page file results in bad consequences when a poorly written program suddenly decides it needs it (not just because there's no memory left, some stuff uses the page file regardless). if you're finding that the space the page file takes up is a problem, what you need is a bigger drive.

turning off page file is stupid in every case. there's a reason Windows doesn't already disable it automatically when it detects certain conditions, and the people who designed it that way sure as hell know a lot more about how Windows works than random people on the internet that repeat decades old snake oil advice. like _Alexander said, disabling the page file results in bad consequences when a poorly written program suddenly decides it needs it (not just because there's no memory left, some stuff uses the page file regardless). if you're finding that the space the page file takes up is a problem, what you need is a bigger drive.

Reality check,

To write such a "poorly written program" you would have to explicitly research how to write to the page file.

Two additional things,

1. Running poorly written programs is generally not recommended for a variety of reasons.

2. Your lack of a concrete example of a useful piece of software that does this is contrary to your argument.

Reality check,

To write such a "poorly written program" you would have to explicitly research how to write to the page file.

Two additional things,

1. Running poorly written programs is generally not recommended for a variety of reasons.

2. Your lack of a concrete example of a useful piece of software that does this is contrary to your argument.

easiest thing you'd have to do is write a program that requests an insane amount of RAM despite not intending to actually use any, that's not exactly hard to do. the existence or lack of an example has no bearing on the truth of the statement, its absence merely fails to offer direct evidence for it, that doesn't contradict anything stated at all. I can't think of any examples off the top of my head, because a) I don't disable mine, and b) i try not to run ****ty programs. But you have to be dreaming to assume that every single thing that someone might need is properly written. in fact, is it not the case that the more niche and critical a piece of software is to someone's particular purpose, the more likely it is that it's poorly written? Not everything has readily available alternatives, and the ones that don't are especially likely not to be of high quality. Considering the fact that there's no benefit whatsoever in disabling the page, why would you go take such an unnecessary risk, whether it's likely to manifest or not? the bottom line is that it's pointless even if it's not harmful at all.

easiest thing you'd have to do is write a program that requests an insane amount of RAM despite not intending to actually use any, that's not exactly hard to do. the existence or lack of an example has no bearing on the truth of the statement, its absence merely fails to offer direct evidence for it, that doesn't contradict anything stated at all. I can't think of any examples off the top of my head, because a) I don't disable mine, and b) i try not to run ****ty programs. But you have to be dreaming to assume that every single thing that someone might need is properly written. in fact, is it not the case that the more niche and critical a piece of software is to someone's particular purpose, the more likely it is that it's poorly written? Not everything has readily available alternatives, and the ones that don't are especially likely not to be of high quality. Considering the fact that there's no benefit whatsoever in disabling the page, why would you go take such an unnecessary risk, whether it's likely to manifest or not? the bottom line is that it's pointless even if it's not harmful at all.

The lack of evidence allows me to discard your statement without any evidence.

That is,

if you say "Although I have no evidence, Microsoft spies on its users through USB cameras" - there is no need for me to provide evidence for the contrary.

I can simply dismiss this assumption of yours without any evidence.

AFAIK malloc may actually allow a program to do that without allocating that amount of memory. That is it will only actually allocate that memory when it is being written to.

You said "suddenly decides it needs it (not just because there's no memory left" and now you are backing away from that statement.

"insane amount of RAM" is not explicitly manipulating the page file.

For a program swap and RAM are nothing more than a singular large pool of memory to use. I advocate only have the fast (RAM) memory without the slow (PF) memory for everyone who has a good or insane amount of memory.

When it comes down to it you are advocating running Windows in, essentially, "compatibility mode" to allow it to trash your HDD when a rouge and/or idiot made 64-bit application goes haywire instead of keeping the application entirely in memory

and killing it off sooner (before the Windows will start allocating more and more HDD space for the rouge application).

Thus, as an SSD and 32GB RAM user, I cannot agree with the statement that "there's no benefit whatsoever in disabling the page".

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • But building your own.. what? You can't build anything like the Steam Machine yourself. Even trying to get close costs a good deal more. Even just the CPU cooler in their price comparison is as big as the entire Steam Machine. If you want a regular gaming PC, then by all means, build that. If you want a a small console-like PC for the living room that is good for gaming, I'm not sure what else is a better deal. In the GN review, they only mentioned a small form factor Dell, which is like twice the size and hundreds of dollars more expensive.
    • Those are some popular multiplayer games. But hardly "all". Just those that don't work on Linux currently due to specific anti-cheat implementations. I think it's also fair to point out the literally thousands of games that don't work on the PS5. And it's not locked at 1080p. That's the default, which you can change.
    • Ubuntu Livepatch arrives on Arm64 to eliminate system reboots for kernel updates by Paul Hill Canonical has just announced that its Livepatch service now supports computers with Arm64 processors. For those who are not familiar, Livepatch allows users to apply important kernel updates without any service interruption or rebooting. While home users will benefit from this, it’s even more important for critical machines that absolutely should not be going offline at all. The feature is available as part of Ubuntu Core 26 for Arm64 and Ubuntu Core 20 and onwards for AMD64. According to Canonical, this will improve the security of systems that aren’t security-maintained daily or weekly, and it helps organizations work towards Cyber Resilience Act (CRA) compliance. If you are familiar with Ubuntu, you probably know that most packages can be updated without having to restart the system. There is one big exception to this, and that’s the kernel; it typically requires you to reload the system to boot into the new kernel. With Livepatch, Canonical has done something so that you don’t need to restart to begin using the new kernel. Aside from Ubuntu Core 26, users with Arm64 chips running Ubuntu 26.04 LTS can also use Livepatch. If you want to learn more about Livepatch, check out its product page. There, you can also find a button to join Ubuntu Pro (it’s free for several home devices) so that you can enable Livepatch. By linking your computer to Ubuntu Pro, you will also extend the life of your Ubuntu install from five years to ten years. If you are running Ubuntu, let us know in the comments if you have been looking forward to this feature on your ARM-based computer. If you’ve had a compatible AMD64 machine for a while and never used this feature, let us know why in the comments!
  • Recent Achievements

    • One Month Later
      nates earned a badge
      One Month Later
    • Week One Done
      Almohandis earned a badge
      Week One Done
    • Rookie
      dorf went up a rank
      Rookie
    • First Post
      mike_rumble earned a badge
      First Post
    • Dedicated
      tuben earned a badge
      Dedicated
  • Popular Contributors

    1. 1
      +primortal
      499
    2. 2
      +Edouard
      206
    3. 3
      PsYcHoKiLLa
      97
    4. 4
      Michael Scrip
      89
    5. 5
      neufuse
      71
  • Tell a friend

    Love Neowin? Tell a friend!