Microsoft published a new release preview build for its Windows 11 operating system on August 14, 2026. The changes in these builds will find their way into the previews for the September 2026 update for the operating system. Most users will receive them on September 8 or later, as rollouts to stable systems begin on that date.
The big new feature, or should I say old feature, of the release brings back some of the taskbar customizations that Microsoft removed when it released Windows 11 about five years ago.
Windows 11 users who install the update on their device will regain the option to snap the taskbar to any screen edge. Up until now, Windows 11 limited this to the bottom position on the screen. Third-party workarounds and hacks offered options to bypass this restriction, but sometimes at the expense of stability.
The second taskbar related change introduces the option to make the entire taskbar slimmer to free up a few pixels for other content on the screen.
To manage these, do the following once the feature becomes available:
The update includes several other changes that are noteworthy:
Start menu: pick between a large and small Start menu under Settings > Personalization > Start > Start menu size.
Start menu Recommended: is renamed to Recent.
Hide the name and profile picture in Start under Settings > Personalization > Start > Hide your name and profile picture on Start.
Hide or show Pinned, Recent and All individually.
Windows Search offers better hints about the type of result, e.g., app, setting, files, or web results.
Option to disable Web and Microsoft Store suggestions in Windows Search under Settings > Privacy & security > Search.
Windows indexes the most used folders automatically, which you can stop under Settings > Privacy & security > Search > Automatically find additional relevant locations.
File Explorer Home should launch faster and is more responsive.
Update progress indicators are shown throughout Windows for a “more consistent and modern experience”.
Administrator Protection is introduced to “protect free-floating admin rights for administrators”.
Switching between virtual desktops is now “smoother and more responsive”.
Ah, notifications. The idea behind browser notifications is sound. It allows websites and services to notify you even if you don’t have them open at the time. However, notifications were turned into an abonimation quickly.
Seemingly every site wants you to turn on notifications for them, which is unpleasant enough. The main problem is spam and also malicious abuse of the system.
Whenever I check the browsers of my parents or other users who are not tech-savvy, I notice loads of notifications. It is easy enough to accept notifications, but not nearly as easy to turn them off again.
While you can disable all notifications, which I do on all of my systems, some may prefer to keep some notifications enabled.
Microsoft tests a new protective feature against abusive notifications in its Edge browser. The main idea behind the feature is to automatically unsubscribe Edge users if a notification was used to push scam, phishing, or malware pages.
When that happens, Edge will unsubscribe the user from receiving notifications to stop additional spam or malicious notifications from being received.
The feature is in beta currently and rolled out over time. It may take a while before it lands in stable Edge versions and even then, it may be on a slower rollout.
Microsoft says that users can check edge://settings/privacy/sitePermissions/allPermissions/notifications to see if sites have been blocked automatically by the security of the browser.
My suggestion? Turn them off entirely there right away and be done with them. You can still add some sites to the exceptions there, to allow them to send notifications while all other sites are blocked from even asking.
If you are a regular on Facebook or visit the site at times, you may have noticed the odd-ad slipping past your content blocker’s defenses. Even with the most powerful tools out there, uBlock Origin for Firefox comes to mind, it happens that you may see advertisement on Facebook.
This is not a one-time slip-off, but the result of a battle between a small team of developers and Meta’s billions. The cat and mouse game has come to an end according to a new post by the uBlock Origin team on Reddit.
According to the post, the content blocker won’t support Facebook going forward. The reason given is that Facebook is countering any bypasses the uBlock Origin team finds for blocking ads and trackers on the site.
For example, Facebook was changing ad labels and markers frequently on its site to cause content blockers to miss them entirely. While content blockers managed to find ways to block ads anew, Facebook then developed new bypasses to show ads once again on its site.
In the end, the team notes that it is too small and lacks the resources to go against a billion Dollar behemoth like Meta. While ads may be blocked for the time being, it sounds as if the next bypass won’t be countered by the team anymore.
This means that Facebook users with uBlock Origin installed will see ads on the site in the long run. It is probably fair to say that most other content blockers, regardless of whether they are native or installed as extensions, faces the same issue.
There is not much that you can do about it. Maybe other content blockers continue their fight against Meta and work most of the time, but that would mean some testing to see which do and which don’t. It is the first time, to my knowledge, that a major content blocker has lowered the flag.
While companies like Google and Microsoft have dropped support for classic MV2 extensions already or are about to end support, some developers announced plans to continue supporting some or even all classic extensions.
Of all the major browsers, it is only Firefox that continues to support MV2 extensions. Mozilla has just reiterated that this is the case stating “Firefox support for uBlock Origin is not going anywhere.” on X.
As far as Chromium-based browsers are concerned, Brave plans to continue support for some extensions only, including uBlock Origin. Opera Software also claims to continue supporting MV2 extensions.
There are a few lesser known browsers, Thorium and Supermium, which pledged to continue their support for all MV2 extensions.
The background story
Google announced plans to switch Chromium, the open source part of Google Chrome and most browsers, to a new rules system. Called Manifest V3, or MV3, it was designed to replace the classic extensions system.
Google would not be Google if it would not have tried to pull a stunt on the browsing community by removing capabilities and replacing them half-heartedly. The outcry was big enough for Google to make some concessions, but the result was still a new system that lacked some of the capabilities of the old.
One of the types of extensions hit hardest by the changes were content blockers; exactly the extensions that threatened Google’s main source of revenue.
Google continues to make changes to Google Search. After introducing AI mode and some other AI features recently, it is now reportedly testing removing the trusted Search-button for another round of AI infusions.
The report comes from Search Engine Watch noting that some users are now seeing the new AI first search page now instead. While the search field remains for now, Google has removed the search button for three AI-powered features: Create images, ask about files and brainstorm. The “I am feeling lucky” button remains for now though.
While that is not a big problem for users who know that you can simply press the Enter-key to start a search, it may confuse some Google users nevertheless. They may activate the AI mode button, which opens an interface to interact with Google’s AI Gemini.
Pressing the three other buttons starts other activities, but not the classic search. According to Search Engine Watch, two of the three AI features work without a Google account, at least for now. Those are “ask about files” and brainstorm. Only create image remains locked for Google account customers.
So, is this a problem? Probably for some users who used the button all the time to start their searches and do not know about pressing the Enter-key.
The test shows that Google continues to focus on pushing AI options to Google Search and some of its other products, such as Google Maps or Gmail. I’m not a huge fan of this. Not because I have something against AI, but because it is causing problems for the remaining independent site owners and blog writers out there.
Ever since Google’s Panda update, things have been going downhill for many. Now with Google keeping more and more visitors to its search engine on its own site, thanks to AI delivering the answer right on site, even larger publishers have faced declines in traffic.
If you use the official Weather app for Windows, you may have noticed that it is quite hungry when it comes to memory. The app uses between 500 and 600 megabytes right when you open it.
This goes down a bit when it is in the background and up again when you use it actively. Some features, like the weather radar, may shot up RAM usage to 1 gigabyte or more.
Still, even at idle, using hundreds of megabytes of RAM suggests that the app is anything but optimized.
Windows users who want a weather app but prefer one that does not use as much RAM, may want to look at third-party solutions that offer just that and often much more.
Here are a few suggestions:
Fluent Weather: uses less than 60 megabytes, is open source, has no ads or tracking, lacks some of the advanced features, such as the weather radar or adding locations to the favorites.
Skyline Weather: open source Windows store app, supports multiple locations, uses about 50 megabytes.
TrayWeather: open source app, displays weather information in the system tray, less than 30 megabytes of RAM usage.
WeatherWidget: another standalone open source app that displays weather information for up to five locations. Less than 30 megabytes of RAM usage.
While all lack some of the advanced features of the native Windows app, all use a fraction of the RAM of the official app.
The company revealed that the top 95 percent of the top Edge extensions are already migrated to MV3 and that there are only 58 MV2-based extensions with “meaningful usage” in the Edge Add-on Store.
As a consequence, Microsoft aims to transition all non-Enterprise installations of Edge to supporting MV3 only by the end of 2026. Enterprise customers will get an extension to early 2027.
Edge users may start to see notices on the “Manage Extensions” page of the browser (edge://extensions) and on detail pages that support is ending. MV2 extensions will be turned off by default over the next few months and customers may get MV3 extensions recommended, if an alternative is available.
The changes will roll out to experimental versions of the browser first before they hit the stable population.
With Microsoft dropping support, the situation looks rather grim when it comes to Chromium-based browsers. Firefox remains a strong supporter for MV2 extensions and should be first pick in most cases.
However, here is an overview of Chromium-based browsers and their MV2 support:
Browser
MV2 Support Status
Approach
Catch
Brave
Curated
Custom Chromium engine patches
Only supports four specific extensions (uBlock Origin, AdGuard, NoScript, uMatrix)
Opera
Legacy only
Maintaining backend workarounds
Only works for previously installed extensions; the Opera store is now MV3-only
Thorium
Full
Hard-forking and restoring MV2 code
Enthusiast project; updates rely on a small team
Supermium
Full
Hard-forking and restoring MV2 code
Niche browser primarily designed for older Windows systems
Notes:
Brave force-enabled MV2 support by modifying their underlying Chromium engine, but they are not supporting the entire MV2 ecosystem.
Opera committed to keeping existing MV2 extensions functioning for as long as it remains “technically reasonable”. However, they have stopped accepting new MV2 extensions and transitioned their official extension store entirely to MV3.
Thorium: A performance-focused Chromium fork where the lead developer has explicitly committed to maintaining the MV2 loading code indefinitely.
Supermium: A privacy-focused browser (originally designed to bring modern web rendering to legacy Windows systems) that guarantees permanent MV2 support.
When you are hunting for big files on your Windows PC, you may come upon several large system files. One of them may be hiberfil.sys, which Windows uses for its hibernation feature and some other features.
The file has a size that is roughly 40 percent of the system RAM. If you have a PC with 16 gigabytes of RAM, it should have a size of about 6,4 gigabytes. This climbs to more than 12 gigabytes on a 32 GB system.
The file hiberfil.sys is found in the root location of the c: drive on Windows PCs by default.
The main hiberfil.sys functions
1. Hibernation
Windows creates a snapshot of the RAM, including open apps, documents and browser tabs, and writes the data directly to the hibernation file hiberfil.sys.
Once it is saved, Windows shuts down completely and doesn’t need electricity anymore. When the PC is turned on again, Windows reads the file and loads the snapshot back in memory, so that the previous session is restored.
2. Fast Startup (Fast Boot)
Introduced in Windows 8 and active by default in Windows 10 and 11, Fast Startup speeds up the time it takes for a PC to turn on.
When shut down is selected, Windows logs out the user and closes any app that is open. It saves the core Windows system and loaded drivers into the hiberfil.sys file.
The next time Windows is powered on, the operating system loads the file from the drive into RAM, which improves the time it takes to start the system, especially on devices with older or slow hard drives.
3. Hybrid Sleep
This feature is primarily used on desktop computers. When a desktop goes to “Sleep,” it enters a low-power state that keeps the RAM active for instant wake-ups. However, as a safety measure, Windows simultaneously writes a copy of the RAM to hiberfil.sys.
If the PC loses power, Windows can restore the state so that uncompleted work is not lost.
Why you may consider shrinking the file
While hiberfil.sys provides useful power and startup functions, there are several practical reasons users—especially desktop power users and gamers—choose to shrink it or delete it entirely.
1. Reclaiming Significant Storage Space
This is the main reason for most users. You can reclaim gigabytes of storage space by shrinking or eliminating the hiberfil.sys on your system. While that is not a problem on systems with plenty of disk space, every gigabyte counts on systems with 128 GB or, god beware, 64 GB of hard drive space.
High-RAM Systems: On a PC with 32 GB, 64 GB, or 128 GB of RAM, hiberfil.sys can use two-digit gigabytes of space on the main OS drive (C:), even if Hibernation is never used.
Small SSDs: For users running Windows on smaller boot drives (such as 128 GB or 256 GB SSDs), reclaiming that space can make a massive difference in keeping the system running smoothly.
2. Reducing Unnecessary Write Wear on SSDs
Solid-State Drives (SSDs) have a finite lifespan determined by Terabytes Written (TBW). Every time a system hibernates or undergoes Fast Startup shutdowns, Windows dumps gigabytes of data onto the drive.
Disabling or reducing hiberfil.sys eliminates continuous large-file write cycles.
While modern NVMe drives are quite durable, minimizing redundant writes helps maximize drive longevity.
3. Fast SSDs Render “Fast Startup” Obsolete
Windows Fast Startup was designed during the era of slow, mechanical HDDs to speed up boot times.
On modern NVMe SSDs, a cold boot from a completely turned-off state takes just a few seconds.
Because the speed improvement from Fast Startup is practically imperceptible on modern drives, many users prefer to turn it off completely and get their disk space back.
4. Fixing System Bugs & Driver Issues
Fast Startup doesn’t actually shut down Windows—it saves a kernel session state. Over time, this can lead to system instability:
Stale Drivers & Memory Leaks: Unstable device drivers or memory leaks can persist across reboots because the system kernel never truly gets refreshed.
Troubleshooting: System administrators often disable hibernation to force Windows to execute clean full reboots every time.
How to shrink or disable hiberfil.sys on Windows 11
Press the Windows-key.
Type cmd.
Select “run as administrator” to open an elevated terminal window.
Click “yes” when asked for permission.
To completely disable hiberfil.sys on the system, type:
powercfg -h off
To shrink hiberfil.sys instead, type:
powercfg /h /type reduced
To undo the change at any time, type:
powercfg /h /type full
Shrinking vs. disabling: the differences
When deciding how to manage hiberfil.sys, the choice ultimately comes down to one question: Do you still want to use Windows’ “Fast Startup” feature?
Here is exactly how the two options compare:
Feature / Impact
Shrinking (type reduced)
Disabling (off)
File Status
Kept, but shrinks to ~20% of your total RAM
Completely deleted (0 bytes)
Fast Startup
Remains active
Disabled (PC performs a true “cold boot”)
Hibernation (App state)
Disabled
Disabled
Hybrid Sleep
Disabled
Disabled
Space Reclaimed
Moderate (frees ~50-80% of the file’s original size)
Maximum (frees 100% of the file’s footprint)
Which should you choose?
Choose “Shrinking” if:
You have a slower drive: If you are running Windows on a mechanical hard drive (HDD) or an older SATA SSD, Fast Startup noticeably improves your boot times.
You want a compromise: You want to reclaim a few gigabytes of space but don’t want to sacrifice the quick boot speeds you are used to.
Choose “Disabling” if:
You have a modern NVMe SSD: On fast modern drives, a traditional “cold boot” only takes a few seconds longer than Fast Startup. The massive storage savings are usually worth the 3-second longer boot time.
You want a “Clean Slate” shutdown: Because Fast Startup saves the system kernel to the drive, bugs, memory leaks, and driver issues can persist across reboots. Disabling the file forces Windows to load fresh every time you turn on the PC.
You Dual-Boot: If you run Linux alongside Windows, Fast Startup leaves the Windows drive in a locked state. Disabling the file ensures you can safely access your Windows files from your Linux partition.
If you run a recent version of Windows 11 on your PC you may have noticed — or not — that Microsoft installed a new application automatically on the device. Called OneDrive Photos, it brings OneDrive’s gallery view to the operating system. To make things worse, reports suggest that Microsoft is pushing the app to non-managed and managed devices.
As always, Microsoft has not confirmed any of that at the time. However, there are multiple reports on sites like Reddit that confirm the installation of the app on devices. Some Windows administrators have created scripts that remove the app from devices, which shows up as Beta for some.
To make matters even worse, it seems that the app installs itself again after it has been removed. Windows Latest suggests that it is linked to the synchronization of OneDrive, but this has not been confirmed yet.
You can check in Settings > Apps whether the extra OneDrive app is installed, or use other means, such as winget to find out. You could also check the following two locations for the actual app that Microsoft pushed to the system:
So what can you do about it? If you do not use OneDrive, you could remove the app entirely and be done with it. If you do, you might be able to replace it with a dummy file in the directory and write protect it. I did not test this, as I’m still running Windows 10 on my main PC.
Just when you thought that Microsoft might have finally understood what users want, it is falling back to old habits. Seems the company never really learns.
It took Microsoft five years to correct a course that it set when it released the Windows 11 operating system. Back then, Microsoft more or less crippled the taskbar functionality by limiting it to the bottom. Users who were used to displaying the taskbar at the sides or top were left with little options, other than relying on working but sometimes unstable third-party solutions.
This year, Microsoft revealed plans to do better. To focus on quality and to a degree what users of the operating system really want. Turns out, it is not really more AI, but a stable system that gives them the freedom to do whatever they please.
After launching taskbar improvements in the experimental Insider channel earlier this year, Microsoft has now moved the improvements to the beta channel.
The changes allow Windows 11 users to move the taskbar to any edge of the screen, just like it was the case on Windows 10 and earlier versions of Windows. Furthermore, Microsoft is introducing an option to free up more space by changing the taskbar’s size to compact mode.
Microsoft writes:
You can now change the position of taskbar on your screen. In Settings > Personalization > Taskbar > Taskbar Behaviors, you can select the side of the screen you want your taskbar on: bottom, top, left, or right. In these other positions, tooltips, flyouts, and animations will still come from the taskbar, and most customization settings like never combine taskbar icons will work with all locations.
We’re introducing a smaller taskbar for users who want to maximize screen space, especially on smaller devices. While the default taskbar remains unchanged, this setting provides a more compact experience with smaller icons and a reduced taskbar height, giving you more room for your apps. Core elements like Start, Search, and the system tray scale appropriately to stay aligned and consistent.
While the move to Beta is the next step in a wider rollout to all users, Microsoft notes that some features are not finished yet.
Support for touch gestures, Search box, and Ask Copilot in alternate locations is in progress. Auto-hidden taskbar and touch optimized taskbar are not currently supported. Smaller taskbar is currently supported only for top and bottom positions.
It seems likely that these issues will get fixed before the final release. Once you have it, you find the new options under Settings > Personalization > Taskbar > Taskbar Behaviors.
