Patch Tuesday Surface Update - Now I have tons of free space - 2.5 gb to ~9


Recommended Posts

32GB Surface here. Did the Patch Tuesday Updates last night and went from 2.5gb free space (moved recovery partition to USB to get that!) and after updating I now have 9.9 GB of space left. My tablet is heavily used by 3 users with tons of apps/email/web surfing - did Microsoft consolidate the App storage space to share between users? fix some renegade caching that may have caused some apps to grow or fix something with un-installs to actually clean them up? Either way, i'm happy! Am I the only one that got not just some space back but GIGS of space back. I did double check that compression wasn't enabled either - curious if that helps/hurts performance on these things - anyone try that?

I noticed that as well. Nice to see that Microsoft are doing everything they can to fix the issues with Surface, I also noticed that the performance hit when Surface runs low on space is fixed as well. Some people are just impatient though and expect it to be perfect straight away.

Not Surface-specific, but some users were affected by a problem where cached app packages or updates were not cleaned up properly. One of the January updates fixes this problem and cleaned up anything erroneously left behind by the bug before.

I noticed that as well. Nice to see that Microsoft are doing everything they can to fix the issues with Surface, I also noticed that the performance hit when Surface runs low on space is fixed as well. Some people are just impatient though and expect it to be perfect straight away.

In all fairness, its not like MS is new to the OS market. I would kind of expect it to be past the stage of taking up so much space, at least by the time they launch.

In all fairness, its not like MS is new to the OS market. I would kind of expect it to be past the stage of taking up so much space, at least by the time they launch.

I'm not going to disagree with you but this is a bug that's been fixed by Microsoft relating to cached app packages and updates that weren't cleared up properly as Brandon mentions in the post above yours.

Seems a bit of an understatement to call it a caching bug when it returned over half of our available space on the device. :rolleyes:

I don't understand what you mean. The impact on a specific user doesn't change the nature of the bug. If you hit the bug and did a lot of app installs/updates, the cumulative size of those downloaded packages stuck in the cache can be quite large.

So is this just surface specific or does it extend to Rt and 8 in general through some other non-firmware patch?

This was already answered in this very thread. This was not a firmware change.

I don't understand what you mean. The impact on a specific user doesn't change the nature of the bug. If you hit the bug and did a lot of app installs/updates, the cumulative size of those downloaded packages stuck in the cache can be quite large.

Except I don't know anyone that had ever installed anywhere near the size of the freed space. (ie I had about 2GB of apps installed and still got 8+GB back. On our other one that is shared by two people, it had maybe 500MB of apps per user and still saw the exact same 8GB+ returned space.) ie use of the device seems to have little to no bearing on the amount returned or we wouldn't have all seen roughly the same amount.

Except I don't know anyone that had ever installed anywhere near the size of the freed space. (ie I had about 2GB of apps installed and still got 8+GB back. On our other one that is shared by two people, it had maybe 500MB of apps per user and still saw the exact same 8GB+ returned space.) ie use of the device seems to have little to no bearing on the amount returned or we wouldn't have all seen roughly the same amount.

How are you judging the size of installed apps? Are you counting updates? (including the inbox apps?) Oh, and their dependencies (i.e. VC++ libraries, etc).

The other thing to remember is that the system cleans up things like WU updates and rollback data on a regular basis (i.e. every 10 days). So it may have happened that you saw the effect of that at the same time.

  • 2 weeks later...

This thread made me realize something something else.

Isn't the Surface(or rather Windows8/RT tablets) the only one to natively offer proper multi user support.

No. Android 4.2 added native multi-user support to tablet versions of the OS.

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

    • No registered users viewing this page.
  • Posts

    • With the current hardware prices Microsoft should lift the restriction. Then if you have the correct TPM then allow you to use X feature, if you don't have the correct TPM then don't but still actually let you run windows. 11. With a disclaimer during install that X features would be unavailable.
    • It's good for recycling of course. But commence inflation of a second hand RAM bubble and price gouging on DDR 4 inventory in 3... 2... 1...
    • Bypassed Windows 11 shows surprising stability on ancient, completely unsupported hardware by Sayan Sen When Windows 11 was first released, one of the most complained-about issues with the new desktop Microsoft OS was its higher system requirements, which pushed many relatively modern and powerful processors and devices onto the officially unsupported list. Thankfully, they have not been updated again for the base OS, though systems require four times the memory and storage if they want to run AI-powered apps and features. As such, Windows 11 technically runs on 4GB of memory, and there is no imposed restriction on the generation of memory it supports. Speaking of memory, prices are extremely high nowadays for hardware, especially DDR5 and DDR4 kits due to the current silicon shortage, and there are also reports of it affecting DDR2 as well, and it might only be a matter of time before even DDR1 gets affected. Before that could happen, an enthusiast took an ancient DDR1-based system and decided to try out Windows 11 on it to see how well the modern OS would fare on such hardware. The system runs an outdated graphics card interface standard based on AGP, or Advanced Graphics Port, called AGP 3.0 or AGP8x. AGP was essentially succeeded by the modern PCI Express (PCIe) bus standard. The user behind the experiment is retro hardware enthusiast Omores, who built the system around an ASRock ConRoe865PE motherboard based on Intel's i865PE chipset from way back in 2003, around the time when AGP was still in fashion. What made this board special back in the day was its unusual support for newer Core 2 Duo and even Core 2 Quad processors while still retaining older DDR1 memory support and an AGP8X graphics slot, making it an ideal bridge or link between two vastly different generations. Powering the machine was Intel's Core 2 Quad Q6600 alongside 3GB of DDR1 RAM and an ATI Radeon HD 4650 AGP graphics card, one of the final and most capable GPUs released for the aging AGP interface. While installing Windows 11 itself was relatively easy by bypassing Microsoft's hardware checks, getting the graphics card fully functional proved to be some challenge. Microsoft had quietly dropped native AGP support after the earliest releases of Windows 10, meaning newer versions of Windows no longer include the necessary Graphics Address Remapping Table (GART) drivers required for proper AGP acceleration. Without them, AGP graphics cards typically boot up, though with limited functionality, and can often throw a Code 43 error in Device Manager. To work around the limitation, Omores extracted Intel's legacy AGP440 SYS driver from an early Windows 10 release and paired it with a modified INF file so Windows 11 would correctly recognize the chipset. Following this and combined with AMD's final 64-bit Catalyst AGP drivers from 2012, the Radeon HD 4650 was able to operate with full AGP 8X acceleration intact. The result was said to be surprisingly usable for hardware that is over two decades old. Hardware-accelerated H.264 video playback worked correctly and benefited apps like Firefox, while legacy applications and games ran without major graphical issues. The system also successfully completed the 3DMark 2001 benchmark, although performance naturally lagged behind what the same hardware achieves under Windows 7, which is significantly lighter than Windows 11. There was, however, one unavoidable limitation as Microsoft's Windows 11 version 24H2 introduces a mandatory SSE4.2 CPU instruction requirement that cannot be bypassed through installer modifications or registry tweaks. Since no AGP-era processor supports SSE4.2, Windows 11 version 23H2 effectively becomes the final release capable of running on such systems. Regardless, it is still a very cool feat and quite fascinating to see just how stable Windows 11 turned out to be on such unfamiliar hardware. Source: Omores (Patreon) via O_MORES (Reddit)
    • That will only really help other players that are also responsible for creating the problem.
    • Well, it's good to know that they have found a workaround to a problem that they helped create, I guess...
  • Recent Achievements

    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
    • One Year In
      BA the Curmudgeon earned a badge
      One Year In
    • Conversation Starter
      rosiecharles earned a badge
      Conversation Starter
    • First Post
      KMilenkoski1202 earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      539
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      151
    4. 4
      Steven P.
      98
    5. 5
      macoman
      66
  • Tell a friend

    Love Neowin? Tell a friend!