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

    • Microsoft releases PowerToys v0.100.1, fixes a bug that made remapped keys misbehave by Ivan Jenic Microsoft just released PowerToys v0.100.1, a patch update that addresses several stability and behavior issues found in v0.100.0. The v0.100.0 patch was a significant update for PowerToys, as it introduced all sorts of new features and additions, such as a rebuilt Shortcut Guide, a Command Palette Extension Gallery, webcam overlay support in ZoomIt, and more. However, the v0.100.0 version also introduced some bugs and stability issues. And now, Microsoft is addressing these issues in the new patch. The most impactful fix in this release perhaps is in Keyboard Manager, where remapped modifier keys were being delivered as system-key events, causing unexpected behavior in apps. The clearest example of this was Alt-to-Backspace remaps, deleting whole words instead of a single character. So, if you thought there was an issue with your keyboard, Microsoft just confirmed that it was PowerToys. Beyond the Keyboard Manager fix, v0.100.1 also addresses several other issues. It fixes a bug with Power Display that was preventing monitors from waking from standby correctly. Additionally, the new update patches Quick Access crashes on launch, and resolves a Shortcut Guide crash that occurred when switching between sidebar sections. Here’s the full changelog: Color Picker Fixed a bug where the main Color Picker window could appear inside the zoomed-in picker view Command Palette Fixed Run history initialization in AOT builds Fixed a bug where the Performance Monitor dock item could show ??? after restart Fixed the Hibernate command using the Sleep icon Limited the "pin to dock" dialog to displays where the dock is enabled Keyboard Manager Fixed modifier keys remapped to non-modifier keys being delivered as system-key events, which caused unexpected behavior in apps such as Alt-to-Backspace deleting whole words Power Display Fixed a bug where selecting On in the monitor power-state control did not wake a monitor from standby Fixed built-in display detection and brightness control on dual-GPU laptops where the internal panel is driven by the discrete GPU PowerToys Run Fixed VS Code Workspaces discovery after VS Code moved recently opened workspace data to shared storage Quick Access Fixed Quick Access flyout crashes caused by unhandled XAML exceptions during launch or page navigation Shortcut Guide Fixed a crash when navigating between Shortcut Guide sidebar sections Fixed number-key rendering in shortcut manifests and added a Postman shortcut manifest Updated bundled shortcut manifests to use the literal number-key token so number keys render correctly across apps ZoomIt Fixed a race condition in audio initialization for ZoomIt video recording You can download PowerToys v0.100.1 from the official GitHub releases page.
    • OBS Studio 32.2.0 Beta 2 by Razvan Serea OBS Studio is software designed for capturing, compositing, encoding, recording, and streaming video content, efficiently. It is the re-write of the widely used Open Broadcaster Software, to allow even more features and multi-platform support. OBS Studio supports multiple sources, including media files, games, web pages, application windows, webcams, your desktop, microphone and more. OBS Studio Features: High performance real time video/audio capturing and mixing, with unlimited scenes you can switch between seamlessly via custom transitions. Live streaming to Twitch, YouTube, Periscope, Mixer, GoodGame, DailyMotion, Hitbox, VK and any other RTMP server Filters for video sources such as image masking, color correction, chroma/color keying, and more. x264, H.264 and AAC for your live streams and video recordings Intel Quick Sync Video (QSV) and NVIDIA NVENC support Intuitive audio mixer with per-source filters such as noise gate, noise suppression, and gain. Take full control with VST plugin support. GPU-based game capture for high performance game streaming Unlimited number of scenes and sources Number of different and customizable transitions for when you switch between scenes Hotkeys for almost any action such as start or stop your stream or recording, push-to-talk, fast mute of any audio source, show or hide any video source, switch between scenes,and much more Live preview of any changes on your scenes and sources using Studio Mode before pushing them to your stream where your viewers will see those changes DirectShow capture device support (webcams, capture cards, etc) Powerful and easy to use configuration options. Add new Sources, duplicate existing ones, and adjust their properties effortlessly. Streamlined Settings panel for quickly configuring your broadcasts and recordings. Switch between different profiles with ease. Light and dark themes available to fit your environment. …and many other features. For free. At all. OBS Studio 32.2.0 Beta 2 changelog: Beta 2 Changes Fixed a CI deployment issue. There are no application changes since Beta 1. 32.2 New Features Replaced add source dropdown with new dialog [Warchamp7] Improved FPS selector UX [jcm93] Added missing file support for filters [exeldro] Added ability for plugins to set custom icons for new source types [cg2121] Included .webp files when adding a directory to Image Slide Show source [TarunCore] Added copy paste functions to frontend API [exeldro] Added filter to compose SDR into HDR [jpark37] Added delete as a hotkey to delete sources on macOS [PatTheMav] Added dynamic bitrate support to multitrack video [lexano-ivs] 32.2 Changes Forced Intel-based installations to update to Apple Silicon version on macOS [PatTheMav] This change means that OBS Studio versions built for Intel-based Macs but running on Apple Silicon Macs will automatically update to OBS Studio built for Apple Silicon Macs. If an installation was using third-party plugins, those plugins will no longer load until replaced with Apple Silicon versions. Fixed audio mixer state getting out of sync when changing settings via websockets or plugins [Warchamp7] Added theming for checked QToolButtons [glikely] Improved OpenGL performance slightly on low-end machines [kkartaltepe] Set minimum size for color source to 1 pixel [exeldro] Added minimum width to spinboxes [Warchamp7] Disallowed overwriting the crash handler [sebastian-s-beckmann] Applied process mitigation policies for Windows [notr1ch] Adjusted description of multitrack video [jhnbwrs] Changed new capture devices to use fallback frame rate by default [PatTheMav] Improved DLL loading behavior on Windows [notr1ch] Limited multitrack video config to Custom service [PatTheMav] 32.2 Bug Fixes Fixed OAuth and dock state save corruption [PatTheMav] Fixed group bounds not resizing when removing items [howellrl] Fixed canvas mixes not being restored after video reset [dsaedtler] Fixed some erroneous crashes during shutdown [Warchamp7] Fixed display capture sometimes capturing black after a duplicator failure [ThrowTop] Fixed color of controls dock output buttons in System theme [shiina424] Fixed virtual camera reset failures [stephematician] Fixed potential crash when user discards changes in the settings window [suogesi] Fixed incorrect return value in virtualcam filter [xtfo] Fixed source toolbar buttons not working after dragging a source into a group [Warchamp7] Fixed properties hint icon spacing [Warchamp7] Fixed potential crash when a video device reconnects on macOS [jcm93] Fixed an issue where PipeWire could fail on NVIDIA GPUs [hoshinolina] Fixed obs_canvas_get_video_info returning incorrect framerate [dsaedtler] 32.2 Deprecations Deprecated obs_properties_add_button [sebastian-s-beckmann] Download: OBS Studio 32.2.0 Beta 2 | Portable | ARM64 | ~200.0 MB (Open Source) View: OBS Studio Homepage | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Is a fast food restaurant a good metric to compare against?
    • Grand Theft Auto VI pricing revealed alongside Ultimate Edition and pre-loading details by Pulasthi Ariyasinghe Last week, Rockstar revealed Grand Theft Auto VI pre-orders will be starting soon, and just a day ahead of that, now the studio has announced the official pricing for the highly anticipated game. This has been a hotly debated topic among fans and industry veterans for a long time, considering the game is expected to be the biggest entertainment product launch ever. The confirmed pricing for the Grand Theft Auto VI standard edition is $79.99, which Rockstar says gives access to the "single-player experience set in the biggest, most immersive evolution of the series yet." This follows what most of our readers thought would happen with the pricing too. At the same time, a $99.99 Grand Theft Auto VI: Ultimate Edition has been confirmed as well, which lands with "an exclusive collection of premium vehicles, weapons, apparel, and action threaded across all aspects of Jason and Lucia’s story." Pre-ordering will also give fans extra bonuses, including a Vintage Vice City Pack of cosmetic items as well as a free month of GTA+. Head to the official website of the game here to check out all the cosmetic rewards the Ultimate Edition and pre-orders bring. Interestingly, the studio does not mention Grand Theft Auto VI multiplayer at all in today's announcement. Perhaps this will arrive later, following the campaign launch, or the studio is keeping that reveal for a later date. Digital pre-orders for Grand Theft Auto VI will begin on June 25, 2026, at midnight local time across regions for Xbox Series X|S and PlayStation 5. The title is slated to launch on November 19 on those same platforms. Pre-loading for Grand Theft Auto VI will kick off on November 12, giving players a week to get the game ready on their consoles. As for the physical edition, Take-Two has confirmed that this will be available without a disc, with the box only containing a download code inside. This will be purchasable starting November 12, giving players who take this route time to pre-load the title as well.
  • Recent Achievements

    • One Year In
      OHI Accounting earned a badge
      One Year In
    • First Post
      Almohandis earned a badge
      First Post
    • Rookie
      DaviKar went up a rank
      Rookie
    • Dedicated
      HidekoYamamoto94 earned a badge
      Dedicated
    • One Month Later
      timbobit earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      474
    2. 2
      +Edouard
      172
    3. 3
      PsYcHoKiLLa
      122
    4. 4
      Michael Scrip
      83
    5. 5
      Xenon
      72
  • Tell a friend

    Love Neowin? Tell a friend!