Microsoft has not mentioned it in the release notes, but according to Brandon LeBlanc, Senior Program Manager at the Windows Insider Program team, the change indicates that your current build is an in-development release, not a specific Windows 11 version, nor your current Insider Channel.

That change makes sense: release notes for Windows preview builds, especially Canary builds, make it very clear that changes "should not be seen as matched to any specific release of Windows." What makes much less sense is how Microsoft calls Canary builds "Dev." True, experienced users know that Windows version and preview channel are two different things, but Microsoft literally has a channel with the same name. Of course, there are already confused people out there.

Back in its original days, Microsoft had just two channels (then called "rings"): Fast Ring and Slow Ring. Now, insiders have access to four new channels with new features, often appearing in "slower" or more stable channels before showing up in Dev and Canary. Besides, you never know whether you will get a lucky ticket and receive new features, as most of them are now rolling out gradually to Windows Insiders. While there is a clear reasoning behind that approach, it just adds to the overall confusion of the program.

As a reminder, you can always check your Insider channel by heading to Settings > Windows Update > Windows Insider.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

A few weeks ago, The Verge's Tom Warren reported that Microsoft was working on some user interface changes for Microsoft Teams that would combine both its text chat and channels with a new UI design. This week, the Microsoft 365 Roadmap site added a new entry that seems to suggest something similar to what Warren reported would be added to the desktop version in October:

A new ‘your teams and channels’ view provides you with a centralized hub where you can see all your teams and navigate to their channels from one page. This interface streamlines your workflows, enabling you to quickly access and manage your teams and channels.

The roadmap website also indicates there will be a number of improvements to the Mesh virtual meeting feature for Teams users in October. One of them, for the desktop and Mac platforms, will add Teams chat in Mesh events:

Participants in Mesh events on PC and Mac can use Teams chat to communicate with all participants, across all rooms, within a Mesh event. Users can do this in the Microsoft Mesh PC app, the Mesh app in Teams, as well as in the chat message list of the Teams app.

Another Mesh feature coming to the desktop and Mac versions of Teams in October will improve interactions in multi-room Mesh meetings:

Mesh event attendees can now see raised hands and reactions from attendees in other rooms during large, multi-room Mesh events. This creates a greater sense of audience feedback as a whole across all rooms in a Mesh event and increases total audience engagement.

There are also some new audio features coming to Mesh for Teams in October.

Spatial audio in Mesh provides a realistic recreation of how sound moves in the real world, with the volume of people speaking or media playing getting lower of as you move away from the source of the sound. The introduction of audio zones enables creators to craft custom audio experiences for the intended use of a space with features such as extended audio drop off distances for conversations that happen in a large area, or restricting what audio can enter a given area, to allow smaller groups to have lively conversations without disrupting their neighbors.

In November, Mesh users in Teams for desktop, Mac, and Android platforms will add Microsoft Whiteboard support:

Mesh event participants can now use Microsoft Whiteboard in Mesh 3D environments. This functionality will enable users to collaborate spatially as avatars on a 2D whiteboard present in the virtual space, available on PC and Meta Quest devices. Mesh event attendees can use inking, annotation, and other built-in tools to brainstorm, plan, and share with others on a digital canvas in real time. Copilot integration with Whiteboard helps suggest and organize ideas directly on your canvas while in Mesh.

Getting away from Teams and Mesh entries, the Microsoft 365 Roadmap site also revealed that Copilot in Microsoft 365 will add prompt suggestions in Copilot chat in September, along with image generation as well.

Finally, the new Outlook for Windows and the web will add a feature in October that will add an "always on" function. This will let users see who is in the office based on their work hours and location.

That's it for our weekly look at the Microsoft 365 Roadmap. We will be back next Sunday to look at the new entries on the site.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Version 8.127 was fully released, but there are no big new features or substantial changes. Instead, developers focused on stability and performance improvements, bug fixes, and other minor changes. Here is the complete changelog:

Polishing Skype: Stability improvements & Bug fixes

 

• Performance and Reliability Improvements to our database system: Designed to reduce the load on your mobile device's CPU, to make your Skype experience smoother and more reliable.
• Resolved permission issue on iPad: The audio/video permissions message will now reappear correctly after turning off permissions, ensuring seamless call setup.
• Fixed button alignment in the Calls tab on Mac: The call options button now maintains a uniform position when the hover effect is active, improving usability.
• Eliminated large spaces between contacts in compact mode on Mobile: Contacts are now displayed consistently, making navigation more efficient.
• Removed call option visibility from the Copilot chat on iOS: The call option is no longer visible when swiping left in the Copilot chat, ensuring expected behavior.
• Corrected market selection for channel mute/unmute actions: When following/unfollowing a channel, the correct market is now consistently applied, preventing errors that previously occurred when muting or unmuting channels from a different market.

While it is true that Skype is no longer the go-to choice when it comes to messaging or calls, it is far from dead, and regular Skype Insider updates prove that Microsoft is not willing to ditch its ill-fated messenger. If you want to try the latest preview build, head to the official Skype Insider page here.

Image source: Depositphotos

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

In another support document, Microsoft revealed that Classic Outlook in version 2407 (build number 17840.20138) may "unexpectedly close at start up." In other words, crash upon launch. The same may happen when attempting to launch Outlook in Safe mode.

If your Classic Outlook crashes on launch, you can check for the following details in Windows Event Viewer:

You can confirm if this is the issue by looking at the Windows Event Viewer Application Log for crash Event 1000 or Event 1001, and the following event details:  

 

Fault Bucket 1620625936954482602, Type 4
Faulting application name: OUTLOOK.EXE, version: 16.0.17830.20138, time stamp: 0x66aaad8c
Faulting module name: ucrtbase.dll, version: 10.0.22621.3593, time stamp: 0x10c46e71
Exception code: 0xc0000005
Fault offset: 0x000000000005137c
Faulting process id: 0x0x5A00
Faulting application start time: 0x0x1DAE741D3515015
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\OUTLOOK.EXE

Microsoft says that the root cause of the problem is corrupted server-based rules for Microsoft 365 mail accounts, which Outlook cannot properly process (ucrtbase.dll). Fortunately, there is a workaround:

To work around the issue, do the following:

 

1. Run Clean rules command line to remove the client and server rules:
   Close Outlook.
   Right-click the Windows Start button and select Run.
   In the Run box paste: Outlook.exe /cleanrules.
2. Select OK.
3. Create a new Outlook Profile, if necessary. For more information, please go to Create an Outlook profile.
4. If you still have the issue, please go to Outlook Web Access and manually remove any rules.

You can find more information about the issue in the official support document. Also, check out a forum thread using this link.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Earlier this week, Microsoft released build 27686 in the Canary Channel. It packs a decent number of new features and changes, one of which is some under-the-hood optimizations that should improve battery life on systems with build 27686. Here is what Microsoft says about it:

We’ve made optimizations to improve battery life for PCs running Build 27686+ in the Canary Channel. Let us know what you think and if you are not seeing the battery life on your PC you are expecting, let us know via Feedback Hub. When filing feedback in Feedback Hub on any battery life issues you experience, be sure to use the “Start recording” button to capture additional logs.

That is not all, though. Another power-related change is more visible. With build 27686, you can set separate power modes for different power states. For example, you can make your laptop run in the "Best Performance" mode while on power and the "Best power efficiency" when on battery:

We’re beginning to roll out improvements to Settings > System > Power & battery including the ability to set your Power Mode for both when your PC is plugged in when it’s on battery along with a few other UI improvements to the page.

 

Other changes in build 27686 include HDR, FAT32, Windows Sandbox, and other improvements. Check out the full (and now-updated with the latest additions) release notes in our separate article.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Gaming Highlights:

 

Intel Game On Driver support on Intel Arc A-series Graphics GPUs and Intel Core Ultra with built-in Intel Arc GPUs for:

 

• Black Myth: Wukong
• Hunt: Showdown 1896
• World of Warcraft: The War Within

Fixed bugs include the following:

Intel Arc A-Series Graphics Products:

 

• Delta Force: Hawk Ops Alpha Playtest (DX12) may experience application instability during gameplay.
• Shadow of the Tomb Raider (DX11) may exhibit corruption on foliage during gameplay.

 

Intel Core Ultra with built-in Intel Arc GPUs:

 

• Force of Warships (DX11) may experience texture corruption during gameplay.

 

Intel Arc Control Fixed Issues:

 

• Arc Control Studio capture recording file may become corrupted when the mouse cursor is enabled during HDR capture.
• Arc Control may experience corruption in studio camera preview while changing settings from style transfer effects.

And here is the list of known issues:

Intel Arc A-Series Graphics Products:

 

• Doom Eternal (VK) may exhibit intermittent flickering corruption in the game menu and during gameplay.
• Blender may experience application crash while rendering certain benchmark scenes.
• Topaz Video AI may experience errors when exporting videos after using some models for video enhancements.

 

Intel Core Ultra with built-in Intel Arc GPUs:

 

• Uncharted: Legacy of Thieves Collection (DX12) may experience an application crash on loading to gameplay.
• Enshrouded (VK) may experience an application crash during gameplay.
• Diablo IV (DX12) may experience an application crash with ray tracing settings enabled.
• Fortnite (DX12) game may crash while performing Alt + Tab operations
• SPECworkstation3.1 may exhibit system instability while running certain workloads.
• CATIA texts may not appear in quality toolbar with HQAO settings
• Procyon AI may experience an application crash while running benchmark with precision float32

Intel 32.0.101.5971 non-WHQL is available for systems with the following processors and graphics cards running 64-bit Windows 10 and 11:

Download the 32.0.101.5971 non-WHQL driver here. Full release notes are available here (PDF).

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Many people use tools like pomodoro timers to pace their daily tasks, by working in set intervals, followed by short breaks, then repeating the same. But, there are other aspects of a workspace that one could improve upon too.

Take your operating system for instance, its built-in window management can be a bottleneck if you are someone who likes having many windows open across multiple workspaces and displays.

Quote

The above doesn't apply to you if you are running COSMIC. 😝

But, there's a way to get past that, and if you are running Ubuntu, or any other Linux distribution that has GNOME, then you are in luck.

With this First Look, we will be taking a look at “Tiling Shell”, an open-source window tiling solution for GNOME-equipped systems.

Tiling Shell: Overview ⭐

Written using the TypeScript programming language, the lead developer behind it, Domenico Ferraro, terms it as:

Quote

    A Gnome Shell extension implementing modern windows tiling system by extending GNOME's default 2 columns to any layout you want!

Some key highlights of Tiling Shell include:

• Easy multi-monitor operation.
• Windows 11-like snap assistant.
• Can be used on GNOME 40-46.
• Supports both X11 and Wayland.

Initial Impressions 👨‍💻

I have been using Tiling Shell for the past few months on my Ubuntu 22.04.4 LTS-equipped laptop, which runs GNOME 42.9 (X11 session). I had installed it after I felt the need to have a more intuitive window tiling set up after I saw the one on Windows 11 in action. (the only thing I like about it)

My configuration of Tiling Shell is pretty close to the default settings, and I will say that the experience so far has been great.

The level of control it gives is impressive, there are options to tweak the inner/outer gaps between windows, enable snap assistant, configure the tiling system, add keybinds for window management, and more.

In terms of the layout choices, the possibilities are endless (literally), there are some handy pre-configured ones that are usable. But, the main highlight is the layout editor, which is the star of the show.

It features a slider mechanism, which can be coupled together with keyboard shortcuts (not shown in the article) to create the perfect layout according to one's preference. Post editing, clicking on the tiling assistant indicator shows an option to save it.

Layout Switcher

Layout Editor

In the layout menu shown above, the last one is a custom one that I had created using the editor for tiling two equal-sized tiled windows, similar to what we find on most window tiling setups.

Additionally, if you go into the settings for Tiling Shell, you have the option to import/export layouts so that they can be used across devices. For me, it didn't function as expected.

As for how the multi-monitor experience is, Tiling Shell doesn't disappoint in that matter. It's easy to tile windows between workspaces and displays using the snap assistant, I didn't feel that this behavior was an add-on, it felt quite native to me.

I usually use the Ctrl button on my keyboard to snap windows in my custom layout by dragging them around. But, the mouse-only operation via snap assistant was great, and is almost the same as the one found on Windows 11.

📥 Get Tiling Shell

Keep in mind that it is not a standalone app, but a shell extension for GNOME, you can get it from the GNOME Extensions website.

If you are not familiar with how to install a GNOME extension, then you should give our GNOME Shell Extensions and Extension Manager guides a read. You will have to install either one of those if you want to set up Tiling Shell without going the manual way.

If you were seeking the source code, or instructions on how to install it manually, then you should visit the project's GitHub repo.

Source

It’s been a long time since we’ve had a Microsoft worm event.

Last week’s patches contained a fix for the Windows TCP/IP Remote Code Execution Vulnerability identified as CVE-2024-38063. This one affects all supported Windows versions and extends back to Windows 7 and Windows 8, including older servers.

This CVE has a very high danger rating. Because of that, I am lowering the MS-DEFCON level earlier than I normally would, setting it to 3. That sounds backward, but this advisory is conditional, based upon the type of user you are and how you decide to deal with the update.

Although the danger is real, I believe the risk is somewhat less. In this alert, I’ll explain why.

Over the years, we’ve changed our systems and networks so that they are not as exposed to Web-based exploits as they were in the past. That’s the main reason I think this risk is manageable. Still, there are ways that attackers can get inside our networks, particularly by phishing. In this case, specially crafted packets must be created that can pass undetected through our edge defenses. (The nature of those packets has been withheld by the researcher because of the danger of the vulnerability.) The purpose of the patch is to add a final layer of detection so that if the dangerous packets get past the edge, they’ll still be picked up.

This vulnerability is directly connected to IPv6. Disable that, and you are protected, even without the patch. But disabling IPv6 does not apply to every situation and in some cases may not be advisable — or even possible.

Therefore, my basic recommendations are threefold: patch immediately, disable IPv6 on all PCs on your network, or configure your edge devices to block IPv6. Now for the details.

There are two options.

Install updates: I have tested updates on my home test-bed computers. No issues were found in that peer-to-peer network. Microsoft has fixed the side effect from last month’s patch installs that would trigger the BitLocker recovery key in instances where drive encryption is enabled on a Windows 10 or 11 Home SKU, or if BitLocker is enabled in Windows 10 or 11 Professional. Thus updating now should be safe.

Disable IPv6 for your network connections: You must do this for each network adapter in your system. For example, if you switch between wireless and wired, each connection must be addressed. Press the Windows key and type view network connections. The Network Connections control panel will appear. Right-click each connection and click Properties. Scroll down the list to find the entry  Internet Protocol Version 6 (TCP/IPv6) and uncheck the box (see Figure 1). You can leave this unchecked after the update is installed.

Figure 1. Disable IPv6 for wired or wireless network connections.

If you want to see whether your computer is using the IPv6 setting, go to this IPv6 site.

I do not recommend disabling IPv6 in your network connections without thorough testing, followed by examination of the consequences. For example, Microsoft Exchange doesn’t like IPv6 disabled. Direct access, in particular, requires IPv6. Servers typically want it enabled. This is more of a risk inside the network rather than outside, because your firewall and endpoint protection should assist you in protection. But it may be used with phishing lures to get inside.

You might consider disabling IPv6 using the PowerShell script CVE-2024-38063.ps1, found on GitHub. However, check and test carefully.

I’ve already seen conflicting information from Microsoft. Its official documentation indicates that the specially crafted packets could lead to remote code execution. A security-threat document available to E5 subscribers indicates that an unauthenticated threat actor could enable remote code execution (RCE) on a Windows device by repeatedly sending IPv6 messages that include specially crafted packets. This could result in a denial of service (DoS) condition. That’s a huge difference in risk, so I’ll be looking for more information to ensure we all know the true risk from this vulnerability.

The most important fact that emerges from current research is that the bug is triggered before the Windows firewall! That means Windows won’t protect you from this bug unless the August updates are applied.

Businesses have other options, such as reviewing network firewall rules, utilizing PVLANs (for DMZ/PAZ Windows IPv6 hosts), and employing existing edge devices to filter packets before they get inside your firm.

Despite my warnings above regarding the potential severity of this bug, as I write this there is no working proof of concept nor a working exploit. Please use my recommendations above as you see fit and as they best apply to your situation.

With respect to patching earlier than I would usually suggest, August updates are generally benign. That means I consider it safe to patch now. Ordinarily, I would have lowered the MS-DEFCON level to 4 by the end of the month, but setting it to 3 is my way of telling you to check carefully now — and, by all means, don’t ignore the bug.

Resources

Source

As such, users with unsupported systems have resorted to running Windows 11 using bypass tricks. Even those with really old chips like Core 2 Duos, Pentium 4s, Athlons, Athlon X2s, and Phenoms, among others, would bypass the system requirements and get Windows 11 up and running on their systems (though that will no longer work on the upcoming Windows 11 24H2 feature update).

The performance difference between Windows 10 and 11 on a similar class of hardware is much the same, indicating that such requirements were not necessary only from the performance point of view, which is why Microsoft had reasoned that security was the main reason they had done so, and pointed towards features like MBEC (on Intel) and GMET (on AMD).

In October last year, we covered a very simple bypass trick that involved just a single command when running the Windows 11 Setup. While this passthrough got popular in the tech community during this time as a result of the media coverage from Neowin as well as others, it was actually something even older.

To use this, all a user had to do was add "/product server" when running the setup, and Windows would just skip the hardware requirements check entirely.

As it turns out, Microsoft has blocked this bypass method on the latest Canary build 27686 as discovered by X user and tech enthusiast Bob Pony. When trying to use the Server trick now, the hardware requirements check is not bypassed.

There are still multiple ways to get around the requirements, and you can even use Microsoft's own official Windows 11 LTSC 2024 which has far more lenient eligibility criteria.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Microsoft has released the latest Windows 11 build for members of the Windows Insider program in the Canary Channel. The new build number is 27686. It includes a preview of the new Windows Sandbox Client along with some optimizations for better battery life and more.

Here is the changelog:

What’s new with Build 27686

 

Windows Sandbox Client Preview

 

This build includes the new Windows Sandbox Client Preview that is now updated via the Microsoft Store. As part of this preview, we’re introducing runtime clipboard redirection, audio/video input control, and the ability to share folders with the host at runtime. You can access these via the new “…” icon at the upper right on the app. Additionally, this preview includes a super early version of command line support (commands may change over time). You can use ‘wsb.exe –help’ command for more information.

 

FEEDBACK: Send us feedback in Feedback Hub (WIN + F) under Security & Privacy > Windows Sandbox.

 

Changes and Improvements

 

[General]

 

• Some features that were previously rolled out to Insiders in the Canary Channel may disappear as we flight newer 27xxx series builds. These features should begin rolling out again to Insiders over time.
• We’ve made optimizations to improve battery life for PCs running Build 27686+ in the Canary Channel. Let us know what you think and if you are not seeing the battery life on your PC you are expecting, let us know via Feedback Hub. When filing feedback in Feedback Hub on any battery life issues you experience, be sure to use the “Start recording” button to capture additional logs.

 

[Settings]

 

In response to feedback, we have added a detach virtual hard disk (VHD/`VHDx) button to Settings making it much simpler to detach your VHD/VHDx as needed. This option is available under Settings > System > Storage > Disks & Volumes, in the properties for your VHD/VHDx.

 

[ADDED 8/16] We’re beginning to roll out improvements to Settings > System > Power & battery including the ability to set your Power Mode for both when your PC is plugged in when it’s on battery along with a few other UI improvements to the page.

 

[ADDED 8/16] On PCs with HDR displays, we have added the option to allow HDR video streaming even when HDR is off under Settings > System > Display > HDR.

 

[Networking]

 

To help us evaluate future improvements in network performance, your device may periodically run network tests in the background to collect diagnostic data. These tests will use a small amount of data (up to 10MB/day) and will only run on Ethernet and Wi-Fi connections that are not marked as metered. This will only occur on PCs in the Canary Channel running Build 27686 and higher.

 

[Storage]

 

When formatting disks from the command line using the format command, we’ve increased the FAT32 size limit from 32GB to 2TB.

 

Fixes

 

[Dev Drive]

 

Fixed an issue where Dev Drive VHDs weren’t automatically re-mounting when the underlying volume was dismounted and brought back online.

 

[Lock screen]

 

Did some work to help address an issue where the battery icon displayed on the lock screen might be out of sync with the actual battery level of your PC.

 

[Windows Security]

 

Fixed an issue in the Windows Security app where if you browsed the networks under Firewall & Network protection, it showed a broken glyph (a rectangle) next to the network name rather than a network icon.

 

[Settings]

 

• Fixed an issue under Settings > System > Storage > Disks and Volumes, where there was no space between the Create and Attach VHD buttons.
• Fixed an issue where the power mode option in Settings > System > Power & Battery was showing in cases where it couldn’t be changed, leading to a blank dropdown.
• Fixed an issue where if you searched in Settings for Kiosk and clicked the result for setting up kiosk mode, it wouldn’t navigate to the correct page for doing that.

 

[Other]

 

Fixed an issue in Registry Editor where when editing a DWORD or QWORD if you pasted in a HEX value into the text box and saved it, the value saved might not be the one you had entered (for example, pasting 0x1 would become 0x411).

 

Known issues

 

[General]

 

[IMPORTANT NOTE FOR COPILOT+ PCs] If you are joining the Canary Channel on a new Copilot+ PC from the Dev Channel, Release Preview Channel or retail, you will lose Windows Hello pin and biometrics to sign into your PC with error 0xd0000225 and error message “Something went wrong, and your PIN isn’t available”. You should be able to re-create your PIN by clicking “Set up my PIN”.

 

[ADDED 8/16] We’re investigating an issue where when trying to open dfrgui.exe (Defrag and Optimize drives) fails with a pop up saying SXSHARED_UCRT.dll was not found.

 

[Input]

 

We are working on the fix for an issue causing the emoji panel to close when trying to switch to the kaomoji and symbols sections, or after selecting an emoji.

You can check out the full blog post here.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

With Windows 11 build 27686, which was released this week in the Canary Channel, Windows Sandbox received several quality-of-life improvements that should make it easier and more convenient to use. For example, you can now have a shared folder that is accessible from the host system and the sandbox. This will come in handy in case you want to move a large file or a bunch of executables to your sandbox.

Also, Windows Sandbox now supports clipboard redirection, which means you can copy to and from the sandbox. Finally, the feature now supports audio and video input, as well as command line support. However, as Microsoft says, it is "a super early version," so expect more changes in future updates.

Besides implementing new features, Microsoft decoupled Windows Sandbox from Windows updates. Now, Windows Sandbox can update using the Microsoft Store, which should make it possible to receive updates faster.

There is no need to install the latest preview build if you want to try Windows Sandbox. To turn it on in your existing installation, press Win + R, type optionalfeatures and toggle on "Windows Sandbox" in the "Windows Features" window. However, the latest feature updates are only available in build 27686, which also brought some changes to FAT32 drives, automatic HDR switching, virtual disks, and other parts of the operating system. Full release notes for Windows 11 build 27686 are available in our dedicated article.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Besides waging war against rivals, search giant Google is also currently trying to kill off ad blocking on YouTube with server-side-injected ads inside videos that may be impossible to jam off.

In the ad blocking extension space, another ongoing change is the move from Manifest V2 to V3. For those unfamiliar, the Manifest API essentially deals with how extensions and add-ons work on browsers, and V3 aims to improve the privacy, security and performance of such extensions.

Recently, uBlock Origin developer recommended users switch to uBlock Lite as Chrome Web Store currently flags the former with a message that says the extension may not be supported for longer following the commencement of the Manifest V2 phase-out at the start of June.

The message (warning) is also present on the "About Manifest V2" page on Google's official site. It notifies extension developers that V2 extensions are no longer accepted on Chrome Web Store with the message "Warning: The Chrome Web Store no longer accepts Manifest V2 extensions. Follow the Manifest V3 Migration guide to convert your extension to Manifest V3."

Microsoft Edge, which is Chromium-based as well, is going a similar route, although no such notification about the Edge Add-ons Store seems to have been planted on its site. However, updates to existing MV2 add-ons are still allowed on Edge, which is not possible on Chrome.

For those who want to keep using Manifest V2 extensions like uBlock Origin in the foreseeable future, one way to do so is to migrate to Mozilla's Firefox, which has no plans to drop MV2 support any time soon. The Gecko-based browser recently said that it wants to extend the support for Windows 7, 8, and 8.1 further.

If you want to stick to Chromium, an official Registry hack exists that allows extending the support for MV2 add-ons with the help of the "ExtensionManifestV2Availability" policy that is designed for enterprises. Enabling the policy allows an extended year of support for MV2 add-ons till June 2025. The policy works on Windows, as well as macOS, and Linux. Chrome version 110 or newer is needed, while for Edge, it is version 123 or later.

Reddit user TeamDJ brought attention to the policy that can be added inside the Windows Registry using the Registry Editor app (Regedit) as a DWORD. They wrote:

1. Open up the “Registry Editor” Program
2. Navigate to: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
3. With the Chrome folder on the left highlighted, select Edit/New/DWORD (32-Bit Value)
   or, if you prefer, on the right side of the screen in a BLANK SPOT, you can RIGHT CLICK New/DWORD (32-Bit Value).
4. Name it ExtensionManifestV2Availability and hit enter.
5. Right click what you just created (ExtensionManifestV2Availability) and click Modify. Set the Hexadecimal value to 2, and click OK.
6. You’re done, but check your work by opening Chrome, and pasting chrome://policy in the URL Address bar and hit enter. You should see the ExtensionManifestV2Availability policy, and the value should be set to 2. If you don’t see it, click “Reload Policies” and/or review your work.

If you are savvy enough, you can also go about the above steps on your own using this official Chrome guide. As always, though, make sure to be careful when tweaking the Windows Registry.

As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Details about the patched vulnerability are currently unknown as the Microsoft Security Response Center website returns error 404 when trying to load the listing for CVE-2024-43472.

Here is the official changelog that Microsoft published in its documentation:

Microsoft has released the latest Microsoft Edge Stable Channel (Version 127.0.2651.105) which incorporates the latest Security Updates of the Chromium project. For more information, see the Security Update Guide.

 

This update contains the following Microsoft Edge-specific update:

 

• CVE-2024-43472

 

Improved reliability

 

• Fixed a browser crash (STATUS_BREAKPOINT) that occurred when trying to upload documents on some websites.

In case you missed it, about a week ago, Microsoft Edge received another security update. It patched six Chromium vulnerabilities and two Edge-related vulnerabilities. Details about that update are available here. In the Dev Channel, where Microsoft Edge receives weekly updates for testing, version 129.0.2766.0 arrived with VPN fixes and various stability improvements on desktop and mobile devices.

To get to the latest Microsoft Edge version, head to Menu > Help and Feedback > About Microsoft Edge or the edge://settings/help page. Wait for the browser to download available updates, and then click Restart. Alternatively, just continue using Microsoft Edge as usual, and it will update itself automatically in the background.

In other news, Statcounter recently reported that Microsoft's desktop browser continued increasing its market share in July 2024. It is currently at its all-time high of 13.74%, which grants the browser solid second place among its competitors, such as Safari and Firefox.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Aside from that, the company has also announced that it is finally making a major change to the FAT32 partition size as it is increasing the format limit to 2 TB from the current one of 32 GB. It writes:

When formatting disks from the command line using the format command, we’ve increased the FAT32 size limit from 32GB to 2TB.

While this limit could have been bypassed via other means, Windows has had this limit imposed for a very long time.

Do bear in mind though that testing a feature in the Canary Channel does not guarantee it will definitely be generally available, but there is a good chance that it will eventually show up if all goes as planned.

As you can see in the example image below, X user and Windows enthusiast Xeno shows how they were able to successfully format a 114.6 GB drive, which was not possible prior to this build. Hopefully, Microsoft will one day bring such a change to the GUI-based Format dialog box too, thus making it easier for the non-techie public.

This is not the only File System-related improvement Microsoft has made in this build. As spotted by another X user and Windows enthusiast PhantomOcean3, the new build raises the ReFS (Resilient File System) version support to 3.15, although the user notes that Windows still supports previous version 3.14.

If you have not been following the integration and slow expansion of ReFS support on Windows, Microsoft, back in March 2023 at Build, launched its ReFS-based Dev Drives that were touted to be up to 30% faster. These Dev Drives are essentially VHDs (virtual hard disks) and they too have received improvements in the latest build. You can read about them in the dedicated coverage of the build 27686 we have linked above.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Users noticed that build 27686, which was released in the Canary Channel this week, contains a new HDR-related option in the Settings app. It allows playing HDR content when HDR is toggled off, saving you from the chore of manually toggling HDR on whenever you want to play a game or watch an HDR video:

For some reason, Microsoft has not mentioned this change in the official release notes for build 27686. However, if you are already on the latest Canary build, and your computer supports HDR, go to Settings > System > Display > HDR and expand the HDR section to check out the new "Allow HDR video streaming even when HDR is off" feature.

The upcoming Windows 11 version 24H2, which is expected in the coming months, will bring HDR wallpaper support in JXR format.

Other changes in Windows 11 build 27686 include improvements for Windows Sandbox Client, which is now a Microsoft Store app, energy efficiency improvements that should result in better battery life, the ability to detach a virtual hard disk in Settings, increased FAT32 size limit from 32GB to 2TB, and more. You can check out the full release notes here.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Although the main focus of the presentation was on developers, every user who wants to save some time and clicks on repetitive tasks will appreciate the new utility.

In a nutshell, PowerToys Workspaces (called App Layouts in the Windows Dev Chat demo) allows you to create groups of applications, arrange them on the screen in a certain order, add some arguments or additional commands and then create a shortcut for launching them altogether.

For example, with just one click, you can launch Visual Studio on the left side of the screen, Terminal in the upper-right corner, and Microsoft Edge in the bottom-right corner of the screen. You will be able to create multiple workspaces and keep them on the desktop for quick access. Here is a demo of how this feature works:

PowerToys Workspaces will let you capture existing layouts with running apps, apps on different monitors, and even minimized applications. Moreover, you will be able to add CLI arguments, launch apps as Admin, specify window sizes, state, and more.

There is no information on when exactly PowerToys Workspaces will be available, but considering that the app receives updates quite often, the wait should not be too long. As usual, PowerToys 0.84 should also bring improvements for already existing modules and utilities.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Microsoft's initial idea was to target non-managed domain-joined Windows 10 Pro and Pro Workstation computers with full-screen Windows 11 ads that would say something like "Upgrade for free to the latest Windows 11" with two "Yes" buttons and a small "Keep Windows 10" link somewhere in a corner.

Following the announcement, Microsoft received quite a lot of criticism and negative feedback from users, so it quietly made changes to its plans. Some time ago, the company updated the original announcement to confirm that it stopped showing those ads to eligible Windows 10 devices. Here is what Microsoft said in the updated post on the official Tech Community website:

To honor your feedback, this change will no longer occur with the April 2024 monthly security update. We will share a new timeline in the coming months.

Although the update was made a few months ago, there is still no "new timeline" for Windows 11 upgrade on non-managed domain-joined devices. Microsoft might take some time, considering that Windows 10 has over one year of active support ahead of it, plus the Extended Security Update program will give users three extra years of security (third-party services promise even more).

It is worth noting that "regular users" are exempt from Microsoft's revised plans, so if you have a Windows 11-compatible computer that is running Windows 10, don't be surprised to see a massive Windows 11 ad next time you restart your computer. There is just no escape from it.

Via XDA

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Here is the changelog:

What’s new with Build 27686

 

Windows Sandbox Client Preview

 

This build includes the new Windows Sandbox Client Preview that is now updated via the Microsoft Store. As part of this preview, we’re introducing runtime clipboard redirection, audio/video input control, and the ability to share folders with the host at runtime. You can access these via the new “…” icon at the upper right on the app. Additionally, this preview includes a super early version of command line support (commands may change over time). You can use ‘wsb.exe –help’ command for more information.

 

FEEDBACK: Send us feedback in Feedback Hub (WIN + F) under Security & Privacy > Windows Sandbox.

 

Changes and Improvements

 

[General]

 

• Some features that were previously rolled out to Insiders in the Canary Channel may disappear as we flight newer 27xxx series builds. These features should begin rolling out again to Insiders over time.
• We’ve made optimizations to improve battery life for PCs running Build 27686+ in the Canary Channel. Let us know what you think and if you are not seeing the battery life on your PC you are expecting, let us know via Feedback Hub. When filing feedback in Feedback Hub on any battery life issues you experience, be sure to use the “Start recording” button to capture additional logs.

 

[Settings]

 

In response to feedback, we have added a detach virtual hard disk (VHD/`VHDx) button to Settings making it much simpler to detach your VHD/VHDx as needed. This option is available under Settings > System > Storage > Disks & Volumes, in the properties for your VHD/VHDx.

 

[Networking]

 

To help us evaluate future improvements in network performance, your device may periodically run network tests in the background to collect diagnostic data. These tests will use a small amount of data (up to 10MB/day) and will only run on Ethernet and Wi-Fi connections that are not marked as metered. This will only occur on PCs in the Canary Channel running Build 27686 and higher.

 

[Storage]

 

When formatting disks from the command line using the format command, we’ve increased the FAT32 size limit from 32GB to 2TB.

 

Fixes

 

[Dev Drive]

 

Fixed an issue where Dev Drive VHDs weren’t automatically re-mounting when the underlying volume was dismounted and brought back online.

 

[Lock screen]

 

Did some work to help address an issue where the battery icon displayed on the lock screen might be out of sync with the actual battery level of your PC.

 

[Windows Security]

 

Fixed an issue in the Windows Security app where if you browsed the networks under Firewall & Network protection, it showed a broken glyph (a rectangle) next to the network name rather than a network icon.

 

[Settings]

 

• Fixed an issue under Settings > System > Storage > Disks and Volumes, where there was no space between the Create and Attach VHD buttons.
• Fixed an issue where the power mode option in Settings > System > Power & Battery was showing in cases where it couldn’t be changed, leading to a blank dropdown.
• Fixed an issue where if you searched in Settings for Kiosk and clicked the result for setting up kiosk mode, it wouldn’t navigate to the correct page for doing that.

 

[Other]

 

Fixed an issue in Registry Editor where when editing a DWORD or QWORD if you pasted in a HEX value into the text box and saved it, the value saved might not be the one you had entered (for example, pasting 0x1 would become 0x411).

 

Known issues

 

[General]

 

[IMPORTANT NOTE FOR COPILOT+ PCs] If you are joining the Canary Channel on a new Copilot+ PC from the Dev Channel, Release Preview Channel or retail, you will lose Windows Hello pin and biometrics to sign into your PC with error 0xd0000225 and error message “Something went wrong, and your PIN isn’t available”. You should be able to re-create your PIN by clicking “Set up my PIN”.

 

[Input]

 

We are working on the fix for an issue causing the emoji panel to close when trying to switch to the kaomoji and symbols sections, or after selecting an emoji.

You can check out the full blog post here.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

According to Microsoft, the problem occurs in Office version 2407, build number 17830.20138 and higher. To confirm that your system is affected, launch Event Viewer and look out for Event 1000 or Event 1001:

You can confirm if this is the issue when by looking at the Windows Event Viewer Application Log for Event 1000 or Event 1001, and the following event details: 

 

Faulting application name: OUTLOOK.EXE, version: 16.0.17830.20138, time stamp: 0x66aaad8c
Faulting module name: mscss7it.dll, version: 16.0.12527.20122, time stamp: 0x5e439ea1 Exception code: 0xc0000005
Fault offset: 0x000000000003e518
Faulting process id: 0x0x51B0
Faulting application start time: 0x0x1DAE97DD89190C3

 

The faulting module name will vary depending on what language packs you have installed. For example, mscss7it.dll for Italian, or mscss7de.dll, for German, with others listed here, Language identifiers and OptionState ID values in Office 2016.

Microsoft says that the root of the problem may be an out-of-date language pack:

This issue may occur if the language pack version is not updated to the current version. If you check the version of the C:\Program Files\Microsoft Office\root\Office16\ mscss7xx.dll it should be a build closely matching the Office version but might not match exactly.

Fortunately, you can mitigate the problem relatively easily. To fix the issue while Microsoft and the Office team are investigating it, perform an online repair of your Office apps or re-install your language packs. If you do not know how to do that, check out the official "Repair an Office application" and "Language Accessory Pack for Microsoft 365" documentation.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Note: these changes will also impact other Chromium-based browsers, including Microsoft Edge, Opera, or Vivaldi. Brave is special, as the developers announced that they will continue to support uBlock Origin and several other extensions (but not all).

The ad-blocker will stop working in Chrome and most Chromium-based browsers once Google launches the change. Any other extension that has not been updated, or cannot be updated because of the changes, will also be disabled by Google.

There is a way to keep on using the classic extensions for longer. While Google turns off support for home users immediately, it is giving Enterprise customers an option to extend support by one year. Good news is that you can also utilize this to extend support.

How to extend uBlock Origin support in Chrome by one year

The policy in question is called ExtensionManifestV2Availability. It defines support for classic extensions in Chrome.

The policy has the following values:

• 0 - Default behavior, determined by Google Chrome and Google.
• 1 - Manifest V2 is deactivated. This means that uBlock Origin won't work anymore.
• 2 - Manifest V2 is enabled. This extends support by a year.
• 3 - Manifest V2 is enabled for forced extensions only. This limits the extensions to addons specified by an administrator.

Windows users can set it in the following way:

1. Activate the Start button.
2. Type regedit.exe.
3. Load the Registry Editor.
4. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome.
   1. Note: some of the keys may not exist. In this case, right-click on the previous key, e.g. SOFTWARE and select New > Key. Name it accordingly to create the path.
5. Right-click on Chrome and select New > Dword (32-bit) Value.
6. Name it ExtensionManifestV2Availability.
7. Double-click on the new Dword and set its value to 2.
8. Restart the PC.

This enables the Enterprise policy on the system. Chrome will not disable the old system for extensions this year, because of it.

Tip: you can load Chrome://policy to verify that the extension is set correctly.

Linux and Mac users may want to check this Chrome support document for instructions on setting policies on their devices.

Which extensions are affected?

It takes a few seconds to find out. Google has started to display incompatible extensions on Chrome's extensions page.

You load chrome://extensions/ and check "These extensions may soon no longer be supported" at the top.

Tip: if you do not see this yet, load chrome://flags/#extension-manifest-v2-deprecation-warning and set the value to Enabled. Restart Chrome, and you will see the warning at the top of the page.

What happens to extensions once the change lands in Chrome?

Google Chrome will disable extensions like uBlock Origin once the change lands. The extensions are not uninstalled, at least not immediately. The screenshot above shows the disabled uBlock Origin extension. The toggle to enable it is inactive, which means that you cannot enable it anymore in the browser. The only options provided are to view the details and to remove it.

Most users of uBlock Origin may notice quickly that the extension is disabled. Websites and services will start to show advertisement again.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Of course, being a preview build, 26120.1350 contains a fair share of bugs and known issues. In addition to those mentioned in the original announcement from August 9, Microsoft has now revised the release notes to warn users that build 26120.1350 contains a bug with the emoji panel dismissing itself automatically.

If you notice that the emoji panel disappears after certain scenarios, like opening the kaomoji or symbol tab or selecting an emoji, you are not alone—Microsoft is aware of the issue, and it is working on finding its root. Here is what the company added to the release notes for build 26120.1350 (that June 13 is probably a typo and should be August 13):

"[ADDED 6/13] We are working on the fix for an issue causing the emoji panel to close when trying to switch to the kaomoji and symbols sections, or after selecting an emoji."

Unfortunately, Microsoft rarely announces additional changes and revisions for already-released build changelogs, so tweaks like that with information about new known bugs or other things could go unnoticed. Fortunately, the new emoji panel bug is not a big deal, so there is no need to panic if you are already on build 26120.1350.

The latest Dev build has other bugs you should beware of (which are why you should never run preview builds on mission-critical devices), such as Task Manager crashing when switching between pages or error 0x800f081 when adding languages or optional features. You can check out the full release notes for build 26120.1350 in our dedicated article.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

In a post on the Microsoft 365 Insider blog, Microsoft stated:

Accessibility Assistant in Word makes it simple for you to create accessible content by flagging any accessibility issues in your document and offering remediation suggestions. Going through each issue one by one can be time-consuming, so we’ve introduced Quick Fix, a new feature that allows you to resolve multiple issues with one click.

If a user wants to check if a Word document has accessibility problems, they can open the document and then click on the Review option at the top, followed by the Check Accessibility selection. Insiders will then see that all of the issues in the Accessibility Assistant groups have been put into one Quick Fix card on the right side of the Word document.

You can then select that Quick Fix card and the Accessibility Assistant will offer some color suggestions. You can then click on the Select All checkbox, followed by clicking on Apply. This will fix the problem in the entire Word document.

Microsoft adds:

Try reviewing image alt text using this feature. You can review auto-generated alt text for all the images in the document at once by using the Review alt text Quick Fix card. Once you are satisfied with the alt text for the images, check the boxes for each image (or check Select All) and click Approve selected.

The Quick Fix accessibility feature is available for Microsoft 365 Insiders who have Windows Beta Version 16.0.17726.10000 or later installed. There is no word on when the feature will be added for all Word for Windows users or when it might be available for other Word platforms.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

Microsoft is making BitLocker device encryption a default feature in its next major update to Windows 11. If you clean install the 24H2 version that’s rolling out in the coming months, device encryption will be enabled by default when you first sign in or set up a device with a Microsoft account or work / school account.

 

Device encryption is designed to improve the security of Windows machines by automatically enabling BitLocker encryption on the Windows install drive and backing up the recovery key to a Microsoft account or Entra ID.

 

In Windows 11 version 24H2, Microsoft is reducing the hardware requirements for automatic device encryption, opening it up to many more devices — including ones running the Home version of Windows 11. Device encryption no longer requires Hardware Security Test Interface (HSTI) or Modern Standby, and encryption will also be enabled even if untrusted direct memory access (DMA) buses / interfaces are detected.

 

The new device encryption setting in Windows 11, version 24H2.

Image: Microsoft

 

The latest Windows 11 version 24H2 update comes preinstalled on Microsoft’s range of Copilot Plus PCs and is expected to be available on existing machines in late September. That means if you clean install Windows 11 later this year or buy a new PC with 24H2 installed, BitLocker device encryption will be enabled by default. If you just upgrade to 24H2, Microsoft won’t enable device encryption automatically.

 

The feature could impact SSD performance on some devices. Tom’s Hardware tested this software version of BitLocker last year and found it could slow drives by up to 45 percent. We’ve asked Microsoft repeatedly since early May to comment on BitLocker device encryption being enabled by default, but the company has only confirmed its plans through support documents where there is no mention of any potential performance impacts.

 

You’ll need a Microsoft account to enable device encryption.

Screenshot by Tom Warren / The Verge

 

You can avoid automatic device encryption if you’re using a local account on a clean Windows 11 version 24H2 install. When you first set up a new machine and log in with a local account, you’ll be prompted to sign in with a Microsoft account to finish encrypting the device. BitLocker can still be manually enabled using the BitLocker Control Panel on local accounts, though. You can also disable device encryption through a toggle in the privacy and security section of Windows 11’s settings interface.

 

Microsoft set out to improve security in Windows 11 in a meaningful way by requiring modern processors, Secure Boot, and TPM (Trusted Platform Module) chips. These requirements, while controversial, allowed Microsoft to also enable its virtualized Memory Integrity feature by default two years ago to better protect Windows 11 systems from malicious code.

 

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts

On Windows 11, if you have the new Sticky Notes app, but it's missing your notes, you can still perform some troubleshooting steps to recover them, and in this guide, I will explain the steps to complete this process.

Microsoft is gradually rolling out a new version of Sticky Notes integrated into the OneNote app. The new experience is similar to the legacy version, but it now includes an option to take screenshots, dock the app to the side of the screen, and requires the installation of OneNote.

Although the app is meant to modernize the experience with new visual elements and capabilities, the rollout isn't going as smoothly as the company was hoping. A small group of users has been reporting a few problems, including lag while scrolling because of the lack of smooth scrolling support and syncing issues, with some users noting that their notes are no longer available.

If you can't find your notes after the new version of the app installs on your computer, you may still be able to recover them from the app's database, reinstalling the app, uninstalling the updated version of OneNote, forcing resync, or use the legacy version of Sticky Notes.

In this how-to guide, I will explain a few troubleshooting suggestions you can try to recover your notes as the new version of the app has been installed on your computer. 

How to troubleshoot Sticky Notes on Windows 11

If you're having problems with Sticky Notes, try the following troubleshooting steps.

Force Sticky Notes sync

If you're noticing that your notes are gone in the new app, it's important to note that the legacy version of the app is still available. As a result, the first step is to open the legacy Sticky Notes app (the one without the "Preview" label) from the Start menu.

Here is the changelog:

Added Features:

 

• Introduced a new Rewards Campaign on Android.

 

Improved Reliability:

 

• Resolved an issue where browser would crash when switching from an InPrivate tab to a normal tab after installing Nord VPN on Android.

 

Changed Behavior:

 

• When relaunching browser, Tab Groups do not have correct collapsed state restored.
• Resolved an issue in Browser Essentials where background text was visible within the ‘Thank you!’ message popup.
• Resolved an issue when splitting the screen immediately after opening browser for the first time caused a size mismatch between the left and right screens.
• Resolved an issue where an error menu would appear when right-clicking on a tab icon in the Tab Groups Hub.
• Resolved an issue where manually added apps to the sidebar were not showing as selected on the ‘Choose Your Sidebar Apps’ page in Gamer Mode.

 

Android:

 

• Resolved an issue where the ‘Enjoying Microsoft Edge so far’ feature page did not appear in the feedback section on Android.
• Resolved an issue where a grey summarize icon appeared in the overflow menu when signing into AAD on Android.

 

iOS:

 

• Resolved an issue on the Password Monitor page where the red triangle icon was overlapping the leaked password text on iOS.
• Resolved an issue where the translation bar would become narrow and elongated when the ‘Show original’ button was clicked on iOS.
• Resolved an issue where NTP weather data would not load when the network was unavailable on iOS.
• Resolved an issue where the keyboard remained fixed on the NTP page and couldn’t be dismissed on iOS.

Microsoft Edge 129 will be available in the Stable Channel on the week of September 19, 2024. If you want to test the browser before it arrives for everyone, go to the official Edge Insider website and download the Dev installer.

Source

Hope you enjoyed this news post.

Thank you for appreciating my time and effort posting news every single day for many years.

2023: Over 5,800 news posts | 2024 (till end of July): 3,313 news posts