Even though Windows 10 is now officially launched, the Insider Program is going to continue. People that have joined the preview program now have a new build of Windows 10 available to them. Build 10525 is the first build released since 10240 was shipped out in July, and the first build since the July 29th launch of Windows 10.

One of the things that has already struck me with Windows 10 is just how quickly it is being iterated even after launch. Small things are constantly being fixed, and because many of them are now being done through the Windows Store, large updates through Windows Update which require a computer restart are not always needed. However Windows Update has been busy too, with three cumulative updates rolled out in the last couple of weeks. It goes to show two things. Windows as a Service is happening, and Windows 10 when it shipped was not complete. While I think that’s kind of the new normal now, with the software never being complete and always being updated, hopefully they will pull back the pace of Windows Updates in the near future since not everyone wants to deal with a system restart every couple of days.

So let’s get on to the changes. First of all there is now the ability to customize the colors for Start, Action Center, Taskbar, and Title bars. People like to customize and this is a great addition. Hopefully these kinds of changes can be saved as themes like in the old days of Windows, and that would allow people to share their experiences. In a world of social, this seems like it can’t not happen.

The only other major change listed is improvements to the Memory Manager. In fact, it is not even new to this build, although they could have tweaked it with 10525. Memory Manager now includes the ability to compress pages if there is memory pressure. This is done as a first step rather than instantly write them to disk when there is pressure on memory, and this change improves responsiveness since it is quicker to decompress when necessary than access the disk to retrieve the pages necessary. By reducing the amount of memory used per process, Windows 10 can keep more active programs in main memory which is going to be a big help on devices without a lot of system memory. The minimum memory for Windows 10 is 1 GB on 32-bit and 2 GB on 64-bit, and we’ve seen some low cost devices shipping with the minimum, so this should be a nice improvement for them in the seat of the pants feel. What it does mean is that the System process is going to seem like it’s using more memory than past releases, since it is keeping these compressed pages in check.

In an odd twist, there are some known issues with the new build. I had wondered how much of this would happen post launch, since the last couple of builds released before launch were all about bug fixes, but it appears that Microsoft is OK with sending out less than 100% functional code to the Fast Ring. Mobile Hotspots don’t work in this build, video playback has an issue which requires an update to the Film & TV app, and optional language packs will not be available on this initial launch, but should be available later in the week.

What’s actually the most telling about how Windows 10 is being developed is that the Mobile Hotspot bug is exactly the same one as the most recent Windows 10 Mobile build released to phones last week. They really are the same code base now. It actually is not going to be a bug that affects a lot of people on Windows 10 since most devices don’t have cellular connectivity anyway, unlike the Mobile build, but if you do use this you better skip the Fast Ring on this one.

If you want to give this build a try, head over to https://insider.windows.com/ and sign up, and then go to settings and set your device to Fast Ring in Windows 10.

And, as an update, I am still finishing up the final touches on our Windows 10 Review so stay tuned for that.

Source: Windows Blog


Comments Locked


View All Comments

  • willis936 - Wednesday, August 19, 2015 - link

    They do actuary. Sequential performance is still higher than random on SSDs. You're right that the impact is much smaller because there is no seeking.
  • Einy0 - Wednesday, August 19, 2015 - link

    I used to set the swap to 4096min to 4096max on Windows XP making it static. It made a difference.There is no reason to set a static swap file on Windows Vista or newer. Until SSDs came along and I had to worry about capacity, I wasn't messing with SWAP file sizes anymore. Now I like to minimize the swap file as much as possible. I will set the swap on Windows 7/8/10 with an SSD, generally at 256min to equal the system RAM but no more than twice the system RAM on the max. I was setting it to 256 to 256 but my users where getting the old out of memory errors sometimes. MS released a windows update service that had a bad memory leak in it around February, it was more than likely the cause. Just to be safe I started using dynamic sizes again so it wouldn't be an issue.
  • Alexvrb - Wednesday, August 19, 2015 - link

    Most 'tricks' involving swapfiles were aimed at mechanical HDDs anyway. If you have an SSD you don't have to worry about being closer to the outside of the platter for higher speeds, nor do you have to worry about fragmentation caused by dynamic swap files.

    So the best trick these days? Buy a halfway decent SSD, use HDDs only for mass-storage (video files, backups, et al) and don't touch the swap file settings. ;-)
  • JonnyDough - Wednesday, August 19, 2015 - link

    Memory management and colors...ROFL. You'll have to do better than Microsoft! I REFUSE to use Windows 10 and so should you, on the basis that my data belongs to ME.
  • damianrobertjones - Wednesday, August 19, 2015 - link

    That's perfectly fine but the OS DOES NOT belong to you. I use Windows 10 as I know that MS already has my data.
  • Michael Bay - Wednesday, August 19, 2015 - link

    Then you might as well drop windows altogether in the favor of loonix madhouse.
    I`m not sure how gullible one must be to beieve taha MS didn`t have your data before 10.
  • hughlle - Wednesday, August 19, 2015 - link

    It's like the whole apple argument. Because no one has explicitly stated as much at this point, they are as such 100% not collecting any "private" data about you. seems that this time around MS thought that they might as well just tell us what they're doing instead of just doing it with a wink and a smile.
  • hughlle - Wednesday, August 19, 2015 - link

    When did you get so big headed as to think you are so right that you speak for others? I couldn't give one hoot about MS having all of my data, and it' not like every other company doesn't already have it.

    Happily sent from windows 10.
  • devione - Wednesday, August 19, 2015 - link

    I hope you don't use any Google or Apple or any internet and Cloud-based service then.

    Enjoy communicating with your string and 2 cans.
  • Alexvrb - Wednesday, August 19, 2015 - link

    So you must therefore also REFUSE to use Android or iOS.

Log in

Don't have an account? Sign up now