Almost as soon as that, the company has also begun rolling out a special compatibility update (KB5022609) for Windows 11 22H2 devices. Microsoft says this update will help improve the installation and recovery of the 2022 feature update and it applies to all Windows 11 22H2 versions. On the support page announcing the update, Microsoft writes:

KB5022609: Compatibility update for installing and recovering Windows 11, version 22H2

Summary

This update makes improvements to the Windows recovery features for Windows 11, version 22H2.

You can download it manually from Microsoft's Update Catalog website. While the information on this particular update package is not provided in detail, it is known that compatibility updates are generally released from time to time to make certain user experience upgrades in terms of installing and/or recovering Windows.

In related news, Microsoft also released KB5022370 Dynamic Update recently, which was said to improve the OS setup and recovery on Windows 11 21H2 devices.

Microsoft improving Windows 11 22H2 compatibility as it begins pushing it to everyone

Unfortunately, those stuck on Windows 10 or unwilling to upgrade are unlikely to receive a remake for arguably one of the most hated parts of Windows UI. Therefore, fixing what Microsoft will not do, requires help from third-party developers. Modern Flyouts, a free Microsoft Store app, is here to save the day.

Modern Flyouts lets you replace the old volume/brightness sliders and media controls, plus enable notifications for lock keys (Num, Caps, and Scroll). The media controls and lock keys support deliver an even better experience than in Windows 11 since the latter features media controls only on the lock screen and notification center.

Windows 10 and 11 have no lock keys notifications, so Modern Flyouts can fix that if needed.

Besides giving Windows 10 a better look, the Modern Flyouts app provides various customization options. You can set light or dark themes, personalize the media controls with album art, enable or disable separate components, and move the flyouts on the screen. Windows 11 does not allow repositioning the volume/brightness flyouts, so the application gets an extra point.

It is worth noting that Modern Flyouts is still in preview (even though it is far from being a new app), so you might experience a random bug. However, before upgrading from Windows 10 to 11, the app was among my default applications list, and I do not recall experiencing any deal-breaking bugs. After all, Modern Flyouts is a free app, so you can check it out yourself.

You can download Modern Flyouts from the Microsoft Store, GitHub, and winget. Use the winget install --id=ModernFlyouts.ModernFlyouts -e command to install the app using Windows Terminal. If you want to learn about more must-have apps, check out our recent article covering 11 excellent applications for Windows 11 users. Although it focuses on Windows 11, all those apps work on Windows 10 and greatly enhance its capabilities.

This free app can modernize volume and brightness sliders in Windows 10

In an update on its webpage displaying the status of known issues in Windows 11 version 21H2, Microsoft has stated that it has kicked off the process to automatically update consumer and non-managed business devices running Windows 11 version 21H2 to version 22H2 - which became available in September 2022 with the name "Windows 11 2022 Update".

The rationale behind this automatic update is that Microsoft believes that consumers will be most secure using a more recent version of Windows. This is interesting because version 21H2 of the OS is still supported until October 10, 2023, which is about nine months away. It seems like Microsoft is being proactive rather than waiting for the end of servicing date.

The way automatic updates work is that feature updates are automatically downloaded and installed on your device. However, you are given some amount of freedom over when you want to restart your device to complete the update. If Microsoft detects an issue such as incompatibility with your device during this process, it will put a safeguard hold until the problem is resolved. This process isn't exclusive to Windows 11, Microsoft has been doing it since Windows 10.

Of course, if you'd rather install the update now instead of waiting for Microsoft to force it upon you at an inconvenient time, you can head over to Windows Update in the Settings app and check for updates. Microsoft has boasted that its analysis and customer feedback for Windows 11 version 22H2 that customers are happier with it, but you can be the judge of that too.

Your Windows 11 version 21H2 device will soon be updated to 22H2 automatically

When the bug was first documented by Microsoft, the company asked affected users to simply terminate the MSTSC process using Task Manager as a workaround. Further steps around the issue were also provided by the company which involved disabling the User Datagram Protocol or UDP using the Group Policy (GP) editor.

Fast forward two months, the issue has finally been resolved by the Redmond giant in the latest Windows 11 22H2 KB5022360 update. The release note says:

This update addresses an issue that affects mstsc.exe. It stops responding while connecting to a RemoteApp and Desktop Connection.

The update also fixes several other bugs and issues, like a searchindexer problem that would cause sign-in and sign-out problems. You can get a rundown of all the bugs and issues affecting Windows 11 in these articles.

Task Manager no longer needed to fix Windows 11 Remote Desktop bug as Microsoft resolves it

Here are the release highlights of the new KB5022360 update:

• This update addresses an issue that might occur when the Input Method Editor (IME) is active. Applications might stop responding when you use the mouse and keyboard at the same time.
• This update addresses an issue that might occur when you convert or reconvert Japanese Kanji using a multibyte character set (MBCS) app. The cursor might move to the wrong location when you type.
• This update addresses an issue that affects picture files you find using search on the taskbar. This issue stops you from opening those pictures.
• This update addresses an issue that stops you from searching for a file based on the file’s contents.
• This update addresses an issue that affects some game controllers. When the game controller is connected to the computer, the computer might not go to Sleep mode.

Below is the full changelog:

• New! This update changes the experience for preview .NET Framework updates. After you install this update, all future preview (optional) .NET Framework updates will display on the Settings > Windows Update > Advanced options > Optional updates page. On that page, you can control which optional updates you want to install.

• This update addresses an issue that affects searchindexer.exe. It randomly stops you from signing in or signing out.

• This update addresses a resource conflict issue between two or more threads (known as a deadlock). This deadlock affects COM+ applications.

• This update addresses an issue that affects conhost.exe. It stopsresponding.

• This update addresses an issue that might affect the Domain Name System (DNS) suffix search list. When you configure it, the parent domain might be missing.

• This update addresses an issue that might affect FindWindow() or FindWindowEx(). They might return the wrong window handle.

• This update addresses an issue that affects certain systems that have firmware Trusted Platform Modules. (TPM). This issue stops you from using AutoPilot to set up those systems.

• This update addresses an issue that affects mstsc.exe. It stops responding while connecting to a RemoteApp and Desktop Connection.

• This update addresses an issue that causes Windows Server 2022 domain controllers (DC) to stop responding. This occurs when they process Lightweight Directory Access Protocol (LDAP) requests.

• This update addresses an issue that affects the Resilient File System (ReFS) MSba tag. The issue causes a nonpaged pool leak.

• This update addresses an issue that affects the ReFS. The issue causes high nonpaged pool usage, which depletes system memory.

• This update addresses an issue that affects devices that are subject to Microsoft Exploit Protection Export Address Filtering (EAF). Some applications stop responding or do not open. These include Microsoft Office and Adobe Reader.

• This update addresses an issue that might affect applications that use Microsoft Edge WebView2 to display content. Applications that use WebView2 include Microsoft Office and the Widgets app. The content might appear blank or greyed out.

• This update addresses an issue that affects a Group Policy for Expanded Toasts.

• This update changes how you enable the Windows diagnostic data processor configuration in preparation for EU Data Boundary support. To learn more, see Enable Windows diagnostic data processor configuration.

   

If you installed earlier updates, only the new updates contained in this package will be downloaded and installed on your device.

and here are the Known Issues with this update.

Windows 11 servicing stack update - 22621.1190

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

How to get the update

You can search for this update in Windows Update by going to Settings > Update & Security > Windows Update. In the Optional updates available area, you’ll find the link to download and install the update, or download the update manually from Microsoft Update Catalog here. To know more about this update, head over to the support article on Microsoft's official website here.

Windows 11 (KB5022360) is out with fixes for Taskbar search, and searchindexer.exe

You can add the Phone Link widget after installing the app version 1.23011.73.0 or newer (via Deskmodder) from the Microsoft Store. It is available in three sizes and allows checking notifications and various status indicators, such as battery level, network, Bluetooth, and Wi-Fi. Clicking a message on the widget launches the Phone Link app and gets you to the notification section.

It is great to see Microsoft adding more useful widgets to the operating system, not just using the area to promote MSN and various tabloids. However, one problem remains unchanged: accessing widgets requires extra action, such as a click, key shortcut, or hovering the cursor over the Widget icon. Some argue that opening Windows Widgets to check out Phone Link notifications is no different from launching the app from the taskbar. It undermines the primary idea of widgets providing quick, glanceable information without extra actions.

Users want Microsoft to allow placing widgets directly on the desktop, and it is one of many popular requests we covered in our "Top 10 features users want in Windows Widgets" article. Although Microsoft remains reluctant to turn Windows 11's widgets into gadgets from the Windows 7 era, the company at least tries to make Windows Widgets a little better with third-party support and more first-party widgets.

Windows 11 is getting more useful first-party widgets

It was back in December of last year that we learned how Microsoft wanted to introduce a new and more accessible layout to OneNote for Windows. It has taken roughly a month to complete developing the new layout, as the software giant has now started to roll out the new Vertical Tabs for the OneNote Windows client.

Instead of Horizontal Tabs being the only option, Microsoft has now introduced another way: a left-sided Vertical Tabs layout. We are not seeing it for the first time in OneNote, however. You have already seen the left-side navigation layout if you are familiar with the design of the OneNote web, Mac, and iPad clients. All Microsoft has done is bring the same feature to the OneNote Windows client.

You can access the Vertical Tabs by navigating to View > Tabs Layout > Vertical Tabs. If you don't like the new layout, you can switch to the old horizontal tabs, and all section tabs will appear at the top of the canvas. You can do this by going to View > Tabs Layout > Horizontal Tabs.

Microsoft is currently rolling out Vertical Tabs for the OneNote Windows client, but the current availability is presently limited to Insiders running Version 2302 (Build 16124.20000) or later. Microsoft has also noted that the new layout is not available on OneNote for Windows 10, which is expected as Microsoft has already confirmed that it is in support mode until 2025. The app that will replace it is the new OneNote for Windows, which arrived in the Microsoft Store last year.

Microsoft OneNote gets a new way to navigate your notebooks, sections, and pages

Microsoft is working on an overhaul of the File Explorer app in Windows 11, according to a report from Windows Central. The new Explorer will reportedly feature redesigned and more touch-friendly navigation, better photo viewing with larger previews, keyword and color tagging for organizing files, and tighter integration with Microsoft 365 and OneDrive.

An internal mock-up of the new interface shows a new "recommended" section of files alongside the existing areas for pinned and recent files, with large previews of various documents and information about where the files are located (OneDrive, SharePoint, and the local Downloads folder are all listed) and about recent changes. The new look will also come with "more modern code" under the hood.

The report says Microsoft wants to release the new Explorer before the end of the year. It could be part of this year's annual Windows update in the fall, but Microsoft has taken a "whenever they're ready" approach to releasing new Windows features in the Windows 11 era—it could be released at any time, or never.

Explorer has been refreshed a couple of times since Windows 11 was released; Microsoft updated Explorer with a tabbed design along with a small batch of other additions shortly after releasing the Windows 11 2022 Update. And the app was also updated to match the rest of Windows 11's new look in the original release of the OS, shedding the old Windows 8-era ribbon UI.

Microsoft's push to integrate and bundle together its various services is still occasionally drawing the attention of government regulators, decades after the Internet Explorer antitrust case. Politico reported earlier this week that EU regulators are close to launching an antitrust investigation of the company because of how it has bundled Microsoft Teams with the suite of productivity apps formerly known as Office. A version of Explorer that likewise prioritizes and advertises OneDrive and Microsoft 365 could also draw the regulators' ire.

Source

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.1245 and Build 22623.1245 (KB5022358) to the Beta Channel.

• Build 22623.1245 = New features rolling out.
• Build 22621.1245 = New features off by default.

The new build fixes several major bugs including an issue affecting ReFS file system, a file copy slowdown bug, and many more. The build also brings the Screen Recording feature to the Snipping Tool.

Here is the full list of changes and improvements, as well as bug fixes in the new Beta builds:

Screen recording in Snipping Tool

We are beginning to roll out screen recording in Snipping Tool to Windows Insiders in the Beta Channel (version 11.2212.24.0). And as part of the most recent Snipping Tool update, we have also added the ability to pause while recording and you should notice improved performance and reliability.

Fixes in Build 22623.1245

[Taskbar & System Tray]

• Fixed a high hitting ShellExperienceHost crash related to interacting with Quick Settings.

[Task Manager]

• Fixed a few issues causing Task Manager crashes.
• You now shouldn’t have to make Task Manager be as wide before the navigation pane appears.
• If text scaling has been increased, the search box shouldn’t overlap with the title bar text anymore.
• Made some tweaks to address cases where text in dialogs was getting cut off when text scaling was increased.
• Fixes an issue where certain parts of the title bar couldn’t be used to drag the window.

Fixes for BOTH Build 22621.1245 & Build 22623.1245

• New! This update changed the experience for preview .NET Framework updates. After you installed this update, all future preview (optional) .NET Framework updates would be displayed on the Settings > Windows Update > Advanced options > Optional updates On that page, you could control which optional updates you wanted to install.
• We fixed an issue that affected the ReFS. The issue caused high nonpaged pool usage, which depleted system memory.
• We fixed an issue that affected copying from a network to a local drive. Copying was slower than expected for some users.
• We fixed an issue that caused Windows Server 2022 domain controllers (DC) to stop responding. This occurred when they processed Lightweight Directory Access Protocol (LDAP) requests.
• We fixed an issue that affected a Group Policy for Expanded Toasts.
• We fixed an issue that might have occurred when the Input Method Editor (IME) was active. Applications might have stopped responding when you used the mouse and keyboard at the same time.
• We fixed an issue that affected conhost.exe. It stopped responding.
• We fixed a resource conflict issue between two or more threads (known as a deadlock). This deadlock affected COM+ applications.
• We fixed an issue that affected devices that are subject to Microsoft Exploit Protection Export Address Filtering (EAF). Some applications stopped responding or did not open. These included Microsoft Office and Adobe Reader.
• We fixed an issue that stopped you from searching for a file based on the file’s contents.
• We fixed an issue that affected searchindexer.exe. It randomly stopped you from signing in or signing out.
• We fixed an issue that might have occurred when you converted or reconverted Japanese Kanji using a multibyte character set (MBCS) app. The cursor might have moved to the wrong location when you typed.
• We changed how you enabled the Windows diagnostic data processor configuration in preparation for EU Data Boundary To learn more, see Enable Windows diagnostic data processor configuration.
• We fixed an issue that affected mstsc.exe. It stopped responding while connecting to a RemoteApp and Desktop Connection.
• We fixed an issue that might have affected FindWindow() or FindWindowEx(). They might have returned the wrong window handle.
• We fixed an issue that affected picture files you found using search on the taskbar. This issue stopped you from opening those pictures.
• We fixed an issue that might have affected applications that used Microsoft Edge WebView2 to display content. Applications that used WebView2 included Microsoft Office and the Widgets app. The content might have appeared blank or greyed out.

You can find the official blog post here.

Latest Windows 11 Beta build (KB5022358) fixes ReFS bug, file copy bugs, and more

According to a new report, Microsoft is working on reimagining its browser and delivering a more modern variant with a better user interface and more productivity features to help Edge stand out on the market dominated by Chrome.

Edge Phoenix is an internal concept the company has been developing since the summer of 2022. It has several quirky features, some of which are already available in preview versions of Microsoft Edge. For example, the recently spotted Split View, rounded corners, and Mica treatment.

Other concepts and ideas from Edge Phoenix are yet to emerge. Windows Central reports that Microsoft is working on a Tab Activity Center feature to provide customers with insides into browser usage. Consider Tab Activity Center as a local variant of the Screen Time feature found on iOS (Digital Wellbeing on Android).

Microsoft also considers turning Edge into a system-wide password manager (the browser already has one of the best-in-class password managers), plus allowing users to get Edge up and running during the initial Windows setup.

Edge's slow year-over-year progress on the desktop market is a clear sign that Microsoft needs to step up its game and offer customers a more compelling product (not imposing the browser with all sorts of user-hostile practices might also be a solid option). Edge Phoenix may be that breath of fresh air to help Microsoft rejuvenate its browser.

Microsoft is working on reimagining the Edge browser with project 'Phoenix'

Basically, some Windows Insiders on this build may experience problems while trying to access certain websites or other resources through a VPN connection. Since VPN connections are primarily leveraged in corporate and enterprise environments and you shouldn't really be using Insider builds for work (unless you're an IT admin testing a new build for work purposes), the problem is not expected to affect most users.

Regardless, Microsoft has documented the issue and detailed a workaround. You can see the steps below with the images courtesy of Microsoft:

1. Click the Start button or the Windows key on your keyboard
2. Search for Edit group policy and launch it to open the Local Group Policy Editor

   

    

3. In the navigation pane on the left, expand to Computer Configuration > Administrative Templates > Network > DNS Client

   

    

4. In the right pane, double-click Configure NetBIOS settings
5. In the pop-up window, select Enabled at the top and in the corresponding Configure NetBIOS options drop-down, select Allow NetBIOS name resolution

   

    

6. Click OK
7. Double-click Turn off multicast name resolution
8. In the corresponding window, select the Disabled radio button

   

    

9. Click OK
10. Close the Local Group Policy Editor and restart your PC

Ideally, you should only be applying this workaround if you find yourself impacted by the VPN issue mentioned earlier. It is also important to understand that Microsoft may resolve the problem in a more permanent fashion in future builds, and then you'll have to roll back all of these changes.

Microsoft issues workaround for VPN problem in Windows 11 Dev Channel build 25284

The issue is caused by a setting in Terminal that is off by default. In short: Terminal needs to have been updated to version 1.16 and the setting needs to have been enabled in the past for the issue to occur.

Windows Terminal may be updated via the Microsoft Store or manually, depending on the installation source.

According to our colleagues over at Deskmodder, the issue is caused by Windows Terminal's "run as administrator" setting for the active profile. Profiles include Microsoft PowerShell, the Command Prompt, Linux terminal and others.

The issue affects any profile that is set to run as administrator. There are two workarounds for the issue.

Getting Windows Terminal to start up again

If one of the available profiles is not configured to start with elevated privileges, then it can be used to open Terminal and modify the preference in any profile that is affected by the issue.

PowerShell is the default profile and it may not run anymore because the "run this profile as administrator" setting was activated. Command Prompt, on the other hand, may start fine. To launch it, simply type cmd.exe in Start and select the Command Prompt result.

Terminal should start fine in this case. Now repeat the following steps for any Windows Terminal profile that is not starting on Windows:

1. Select the drop-down arrow icon in the tab bar and then Settings from the menu
2. Select one of the available profiles under "Profiles".
3. Toggle the setting "Run this profile as Administrator" to off.
4. Activate the save button to save the change.

Windows Terminal should startup up normally after the change has been made.

Windows Terminal can't be started anymore

The situation is more problematic if Windows Terminal can't be started anymore, because there is no profile with the administrator preference set to off.

Here is the workaround for that situation:

1. Load %LOCALAPPDATA%\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState in the File Explorer address bar.
2. Create a backup copy of the file settings.json.
3. Open the file settings.json with an editor, e.g., Notepad, and search for "elevate": true,.
4. Change true to false in all cases and save the file.

Windows Terminal should start up fine afterwards.

Windows 11 lists the version of Windows Terminal under Settings > Apps > Installed Apps.

Now You: do you use Windows Terminal?

How to fix a Windows Terminal startup issue

Every few years, Microsoft is making it more difficult to create a local account during setup of the Windows operating system.

The company announced in February 2022 that new setups and first runs of Pro versions of Windows 11 would require a Microsoft account. Previously, one Home editions of Windows 11 required that customers signed-in to or created a Microsoft account on first run of the system.

It did not take long for workarounds to become available, but many users may be unaware of these bypass options. It is important to realize that both account type offers certain benefits.

Advantages and disadvantages of a Microsoft account

Some users may prefer to use a Microsoft account, as they offer some advantages. Here is the top list of Windows features that require a Microsoft account or benefit from it:

• Windows Settings sync across all Windows devices, provided that syncing is enabled. This is a powerful feature, as it keeps all Windows machines in sync and extends to Microsoft's Edge web browser as well.
• Microsoft Store requires a Microsoft account to download and install games, apps and media.
• OneDrive cloud storage becomes available only if a Microsoft Account is used.
• Other Microsoft products, such as Microsoft To-Do, require an account for usage.
• Remote password recovery support.
• Additional security options, such as 2-factor authentication or passwordless sign-ins.

You may check out Shaun's article on the Windows features that require a Microsoft account.

Others may prefer local accounts as they reveal less to Microsoft account and are not attackable if the device is not turned on. Computer techs may also need to setup accounts for customers, who may not be available or able to provide a Microsoft account.

Here are the main benefits of using a local account:

• Improved privacy, as less data is given to Microsoft or submitted automatically while the operating system is used.
• Microsoft accounts may be hacked remotely, while local accounts only when the Windows device is turned on and connected to the Internet.

How to avoid using Microsoft accounts in Windows 11

There are several methods to bypass the Microsoft account requirement during setup on Windows devices.

I described one option in How to use local accounts on Windows 11 version 22H2 devices. While written for that specific version, the described method works in other versions of Windows 11 as well.

To describe it in a sentence, it is creating a Microsoft account during setup and creating a local account after setup ended. It is not elegant and requires that an email address is used initially for the account creation.

The following two methods do not require a Microsoft account at all.

Bypass 1: OOBE\BYPASSNRO

This bypass is the easiest option right now, as it requires just a few steps during setup to skip the Microsoft account creation.

Here is how it works:

1. Disable the Internet connection before starting setup, e.g., by disconnecting the LAN cable or disabling Wi-Fi.
2. Windows will display a "Let's connect you to a network" or similar screen. The upcoming Windows 11 version 22H2 does not allow you to skip this anymore to create a local account.
3. On the screen, use Shift-F10 to open a command prompt window.
4. Type OOBE\BYPASSNRO and hit the Enter-key.
5. Windows will reboot and return to the "Let's connect you to a network" screen. Only this time, you may select "I don't have Internet" to skip this.
6. Then you select "Continue with limited setup" to then create a local account during setup.

Bypass 2: Use a banned email address

Microsoft has banned email addresses that were used too often in the account creation process. You may use this to your advantage, as it allows you to skip the Microsoft account creation or sign-in phase during setup.

Here is how this method works (thanks Neowin😞

1. Select Sign-In when asked to create or sign-in to a Microsoft account during setup.
2. Use the email address no@thankyou.com.
3. Type any password on the next screen.
4. Windows will display "Oops, something went wrong" on the next screen.
5. Clicking Next opens a screen that allows you to create a local account.
6. You can assign a password to the account, or leave it empty.

Bypass 3: Use the free tool Rufus when setting up Windows

Rufus is a free program that anyone may download. It allows users to create Windows installation media. Recent versions of the application include options to remove certain requirements, including the requirement to create a Microsoft account during setup.

You may check out our full guide on using Rufus to bypass the Microsoft account requirement during Windows setup. The only requirement though is to disconnect the Internet connection prior to starting the setup of the operating system.

Closing Words

There is a chance that Microsoft is removing the bypass options in future versions of Windows. New bypasses may be found, which we will add to this guide.

For now, users have several options to skip using a Microsoft account during setup.

Now You: local or Microsoft account, what is your preference?

How to bypass the Microsoft Account requirement during Windows setup

This free watermark removal tool is surprisingly effective against stock images

Resetting your PC isn't a fool-proof method to get your PC up and running, it has a chance to fail. If it does, you will have to reinstall Windows from scratch, and in the process lose all your apps and files.

While it is not clear how the new feature could work, a couple of known leakers (PhantomofEarth and Xeno) have suggested that it will allow users to perform an in place repair, or repair installs. What that likely means is that users will be able to fix their PC without resetting it completely. Since it relies on Windows Update whether it will probably require a working internet connection. Of course, it all depends on how the feature works, if its purpose is to fix the problems without an ISO, I believe that the only solution left is to re-download the system files as required in order to repair Windows.

This could pose a hurdle if a user actually has problems connecting to the internet, but the new troubleshooter options in the Get Help app should help sort out the issues. Only time can tell us how the feature would actually work. On the bright side, downloading a few files instead of a whole ISO could be a much faster, and efficient way to solve the issues.

As for now, let's get back to how the option can be accessed. The latest build in the Dev Channel introduces the new setting, but it is not directly available. You will need to use the ViveTool utility to enable a Velocity ID related to it.

How to enable the Fix Windows problems with Windows Update option

1. Download ViveTool, extract it to a folder.

2. Open a terminal window with administrator rights, and set its path to the folder that contains ViVeTool.exe

3. Paste the following command in it, and hit Enter

4. .vivetool /enable /id:42550315.

5. Restart the computer

6. Open the Windows 11 Settings app, and navigate to System > Recovery. Or, you can go to Settings > Windows Update > Recovery. It opens the same page.

Note: Command prompt users should delete the . before the code.

You should see a new option here that says "Fix problems using Windows Update". There is a button next to it, "Reinstall now". It will likely be greyed out for you, i.e., it is not clickable, if your computer is working fine. But it's good to have the option, isn't it? You never know, it could prove to be useful if something goes awry. As Deskmodder points out, not everyone may know how to download a Windows ISO, let alone use it to create a bootable USB drive. So the option to fix problems using Windows Update could be a lifesaver not just for tech-savvy users, but also for average users.

It will take a while for Microsoft to test this feature, it has not even been announced officially yet. So, we could be looking at a few months or so before the option is introduced in the stable channel of Windows 11, if it ever happens. Not all experimental features make it to the final release, but I think users may generally agree that an option to fix Windows errors without an ISO would be a welcome one.

Source

Microsoft has offered a workaround of sorts for Windows 10 and 11 users who've noticed their Start menu is suddenly unresponsive and that some applications won't open or work correctly.

Unlike previous headaches with the Start menu and similar features, the latest problems are not caused by bad operating system patches but possibly by broken updates for third-party applications that rely on Microsoft Office, according to the IT giant.

More specifically, some third-party apps, following an update or not, appear to trigger one or more bugs when interfacing with Redmond's software, disrupting people's desktop productivity.

Microsoft is pointing the finger of blame in the general direction of app makers; at least one third-party developer is blaming a programming flaw in the mega-corp's code.

"Affected Windows devices might have damaged registry keys or data which might affect apps using Microsoft Office APIs to integrate with Windows, Microsoft Office, or Microsoft Outlook or Outlook Calendar," Microsoft offered on its Windows Health Dashboard.

At the heart of the issue, users not only find the Start menu unresponsive, but Windows Search and Universal Windows Platform (UWP) apps don't work properly either. This affects Windows 11 versions 22H2 and 21H2 and Windows 10 versions 22H2, 21H2, and 20H2.

As a workaround, kinda, Microsoft recommends users uninstall misbehaving apps that integrate with Windows, Office, Outlook, or Outlook calendar, and also check for updates to affected software or guidance from developers of those apps.

In particular, the tech goliath pointed to ClickShare, an app that is used to wirelessly share the screen of a laptop or mobile device via a meeting or office room's audiovisual system. Users will run into problems "when a third party process such as ClickShare uses Office APIs on a computer where Office is deployed by using Office ClickToRun," Redmond wrote in a support file.

According to Barco, ClickShare's maker, when the app begins to read the Outlook Calendar, the Start menu may ignore mouse clicks, the Windows key may not work, and the desktop Search feature may ignore mouse clicks on the Search button as well as the Windows+S key.

In addition, Outlook or OneDrive can no longer connect or sync.

"More investigation has shown that the ClickShare App triggers a bug in the Microsoft Office API (MAPI)" that removes application packages' permissions from a particular Registry entry, Barco wrote on its own support page.

The biz said users should ensure the ClickShare app is updated to version 4.27.2 or higher, and that Calendar integration in the app is disabled.

Barco also directed users to Microsoft's pages addressing the issue.

Microsoft said it was investigating the weirdness and is expected to deliver some kind of solution.

The technology titan has run into a few snags with its operating system in recent weeks. Its Defender for Endpoint this month went awry, removing icons and application shortcuts from the Windows 10 and 11 desktop, Taskbar, and Start menu.

Days later, Microsoft reported that users running the latest versions of Windows 11 were losing some Office apps after running System Restore. There also were problems with such tools as Notepad, Paint, Cortana, and Terminal.

The mega-corp offered some workarounds for those issues. ®

Source

Microsoft launched the Widgets app in Windows 11 as a central hub featuring news, tips, weather information, and several Microsoft-specific promotions and highlights.

Third-party widgets were not supported back then, but Microsoft promised that support would be added eventually.

Fast forward to January 2023, and the first third-party widget is now available in Developer builds.

Microsoft has a strong partnership with Meta, parent company of Facebook, and the launch of widget support in Messenger confirms that the partnership is still going strong.

Windows 11 users need to install the Messenger app on their device and make sure that it is up to date. Afterwards, it is necessary to add it as a widget by selecting the plus-icon in the Widgets interface and selecting the Messenger widget to pin it to the Widgets board.

Windows 11's Widgets board displays the last few messages that users have received in Messenger from that moment on whenever it is opened.

The data is limited to just a few words, the name of the contact and the time. A click opens the full message in the Messenger application on the device.

Microsoft announced that more widgets will become available in the foreseeable future as "more developers create and release widgets for their apps".

Not all applications make good targets for placement on the widgets board, and it remains to be seen if third-party support will increase the attractiveness of Widgets, or if it remains a niche feature, despite it being promoted heavily by Microsoft.

Expect more chat, cloud-based, and entertainment apps to come with widgets support in the coming years.

Microsoft never revealed numbers regarding widgets. It is unclear if the feature is popular or if most Windows 11 users ignore it by removing the icon from the taskbar.

To remove the Widgets interface, right-click on a blank space on the Windows 11 taskbar, select Taskbar Settings and flip the switch next to Widgets to off. Disabling Widgets may save system resources, actually.

You may also check out Ashwin's guide on uninstall widgets in Windows 11.

Now You: do you use Widgets? If not, would you if Microsoft would make changes to the feature?

Meta's Messenger is the first third-party Windows 11 Widget

The full changelog is given below:

What’s new

New Widget

With the release of Windows App SDK 1.2 developers are now able to create widgets for their apps. Users can access these experiences on their Windows 11 widgets board in current Dev Channel Insider Preview builds.

Ready to try out a new widget? The Messenger app now has a preview version of its widget available. To give it a try, go to the Microsoft Store and update to the latest version of Messenger. Then open the widgets board and navigate to the widgets picker by clicking the “+” button at the top-right of the board to pin your widget.

The Messenger widget on the widgets board.

As you give this widget a try, please let us know what you think through the Widgets feedback link in the widgets picker. You should expect to see additional new widgets as more developers create and release widgets for their apps.

Fixes

[Taskbar & System Tray]

• Fixed an issue where right clicking on certain icons in the hidden icons flyout would make the flyout dismiss rather than bringing up the context menu for that icon.

[Search on the Taskbar]

The fixes only apply for Windows Insiders who received one of the different treatments for how search looks on the taskbar that began rolling out to Insiders with Build 25252:

• Fixed an explorer.exe crash which was impacting some Insiders, related to the search box in the taskbar.

[Input]

• When search suggestions are triggered while using the Pinyin IME, keyboard focus will now stay on the current candidate. To move focus to the search suggestions, press Tab.

[Windowing]

• Fixed an issue for PCs with touch, where when using certain apps in full screen mode it wasn’t possible to swipe down from the top of the screen to make the title bar appear.

[Other]

• Fixed an issue which was causing certain apps to hang or crash when saving files as PDF in the last few builds.
• Fixed an issue where using the cast option in an app may unexpectedly not show any devices in recent builds.

NOTE: Some fixes noted here in Insider Preview builds from the Dev Channel may make their way into the servicing updates for the released version of Windows 11.

Known issues

[General]

• [NEW] Some Insiders may have issues accessing websites and other resources via VPN connections. See this forum post for details and how to workaround the issue.
• IMPORTANT: Some Arm64 devices may fail to resume from sleep/hibernate when running Build 25281, experiencing a hang at the OS boot logo. To bypass this bug, please use the Windows Recovery Environment (WinRE) to roll your device back to the previous build. Instructions can be found here: ms/WinRERollback.
• Using Windows Hello to sign in with facial recognition may not work on Arm64 PCs. A workaround for this is to use the Hello PIN path.
• Some users are experiencing longer than expected update times installing recent builds. We are actively investigating this issue.
• We’re investigating reports that some Insiders are experiencing freezes when using the browser and certain other apps after the previous Dev Channel flight.

[Widgets]

• [NEW] Third-party widgets may occasionally disappear from the widgets board. They can be re-added by clicking refresh or by re-pinning them from the widgets picker.
• [NEW] Third-party widgets may occasionally get unpinned when the Microsoft account is used to sign-in multiple Windows 11 devices.
• [NEW] The undo button on the widget pinned/unpinned toast notification sometimes doesn’t work.

[Taskbar & System Tray]

• The taskbar is sometimes cropped in half when using the tablet-optimized taskbar. You may also see this issue on secondary monitors.

[Search on the Taskbar]

The following known issues only apply for Windows Insiders who received one of the different treatments for how search looks on the taskbar that began rolling out to Insiders with Build 25252:

• There is an issue where you will be unable to change taskbar search box to show as icon only via taskbar settings in some cases. To work around this issue, first change to a different option and then after, you should be able to choose to show as icon only.

[Task Manager]

• Some dialogs may not render in the correct theme when applied from Task Manager Settings page.
• The data content area of the Processes page may flash once when theme changes are applied in the Task Manager Settings page.

[Windows Spotlight]

The following known issues only apply for Windows Insiders who received one of the different treatments of Windows Spotlight that began rolling out to Insiders with Build 25281:

• [NEW] Clicking on a secondary monitor does not dismiss the full screen experience.
• [NEW] Spotlight wallpaper doesn’t show the correct resolution on multiple / mixed resolution monitors.
• [NEW] In some cases, people are not getting a consistent refresh on a daily basis.

You can find the official blog post here.

Latest Windows 11 build 25284 brings more Widgets, fixes right-click issues, and more

The sidebar has received an upgrade to show more information at a glance. Games on it will now display data such as recently receiving an update, days since last played, achievements completion status, and pending invites depending on what is relevant.

A new module has also appeared on the Game Pass home page to notify players of available 'EA Game Trials'. "You will sometimes see this module on Home, and you can always find the list through the dedicated EA Play hub in the app," adds Microsoft. Speaking of the home page, the Xbox app's "Coming to Game Pass" section has been spruced up to bring more attention to it.

The bug fixes that are included in the latest update improve text readability on game pages, solves the Game Pass tab sometimes being blank, and more. Here's everything:

• Adjusted the size and weight of some fonts on game pages for better readability.
• Fixed an issue where install sizes were not present after recently installing a game.
• Fixed a bug where some devices would fail to load content on the Game Pass tab.
• Fixed a bug where your ‘Cloud Gaming Jump Back In’ list would infinitely load when on an ARM device.
• Fixed certain scenarios that would leave you stranded, and need to restart the app.
• Fixed several Vietnamese and Philippines localization issues.

There is a single known issue this time, and it is isolated to the Desert high contrast theme on Windows. Using the theme is seemingly making the Guide button and the Show Stream menu disappear while using remote play.

Xbox app on Windows gains a sidebar upgrade with latest update

As per usual, there's no changelog to speak of, so it's unclear what's new in the bits that relate to Server, for a changelog of the build 25284 client, go here.

Branding has not yet been updated and remains as Windows Server 2022 in the preview. In addition, Microsoft is encouraging Insiders to give feedback in the Windows Server category and then the appropriate subcategory. The company asks to indicate the build number you are providing feedback on along with the title as shown in the example below:

• [Server #####] Title of my feedback

What's New

There are no new features shared about this build.

Known Issues

There are no known issues reported in this release.

Available Downloads:

• Windows Server Long-Term Servicing Channel Preview in ISO format in 18 languages, and in VHDX format in English only.
  Windows Server Datacenter Azure Edition Preview in ISO and VHDX format, English only.*
  Microsoft Server Languages and Optional Features Preview

Note: Downloads to certain countries may not be available. See Microsoft suspends new sales in Russia - Microsoft On the Issues

Keys are valid for preview builds only:

• Server Standard: MFY9F-XBN2F-TYFMP-CCV49-RMYVH
• Datacenter: 2KNJJ-33Y9H-2GXGX-KMQWH-G6H67
• Azure Edition does not accept a key

To download, registered Insiders can head over to the Windows Server Insider Preview download page here. You can also check out the Getting Started with Server page here on the Windows Insider for Business portal to register for the Windows Insider Program in case you aren't already registered.

Microsoft also notes that this Preview will expire on September 15, 2023.

You can download the build here, and find the official announcement here.

Latest Windows Server LTSC vNext build 25284 out in 18 languages with ISOs

Google has made two changes to provide easy share access to content on Meet. Firstly, the company will let users present and share content with meeting attendees, like individuals on the Calendar guest list right from Google Meet. Secondly, whenever a user shares a link in the chat box, they get to adjust access from the “file access dialogue” and add the file to the calendar.

When an individual is presenting at a meeting, they can share desired files from the suggestion feature in Meet Chat or by clicking on the floating action menu on their screens. When a file is presented, attendees receive a notification and a link to the file in the Meeting chat.

Google wrote in a blog post explaining that the feature helps keep the audience engaged. It added:

“By allowing sharing directly from Meet, you can seamlessly share presented content without having to switch into another window to grant access, which can be disruptive. This makes it easier for meeting attendees to follow along with your presentation, find and reference your material later on, and continue working on action items from the meeting.”

There are no Admin controls for this feature, and it'll be available by default to end users. The feature will roll out to Rapid Release Domains gradually beginning today, whereas, for Scheduled Release Domains, it will be available starting February 14. Google Workspace and legacy G Suite Business and Basic users and personal Google Account owners will be able to access the capability.

Google to let users share and control others' access to files on Meet with new changes

Aside from that, this release includes a few game-related fixes, but plenty of Known Issues. Find the full changelog below:

GAMING HIGHLIGHTS:

• Intel® Game On Driver support on Intel® Arc™ A-series Graphics for:
  • Forspoken

NOTES:

• The Intel® Arc™ 101.3490 BETA driver is bundled with the latest version of Intel® Arc™ Control to streamline installation experience, resulting in a larger driver package file size.

FIXED ISSUES:

Intel® Arc™ Graphics Products:

• A Plague Tale: Requiem* (DX12) may experience application freeze and crash during gameplay.
• Need for Speed: Unbound* (DX12) may exhibit box corruptions during gameplay.

Intel® Core™ Processor Products:

• Need for Speed Unbound* (DX12) May exhibit screen-space colour corruption during gameplay.
• Total War: Warhammer III* (DX11) May exhibit an intermittent application crash when launching the game.
• Battlefield: 2042* (DX12) May experience colour corruption on certain maps.

KNOWN ISSUES:

Intel® Arc™ Graphics Products:

• Warhammer 40,000: Darktide* (DX12) may experience application crash during character selection.
• Halo Infinite* (DX12) may exhibit colour corruptions during gameplay.
• Sea of Thieves* (DX11) may experience colour corruption on water edges.
• Conqueror’s Blade* (DX11) may experience corruption in benchmark mode.
• Call of Duty: Vanguard* (DX12) may experience missing or corrupted shadows during the Submarine mission.
• System may hang while waking up from sleep. May need to power cycle the system for recovery.
• GPU hardware acceleration may not be available for media playback and encode with some versions of Adobe Premiere Pro.
• Blender may exhibit corruption while using Nishita Sky texture node.

Intel® Iris™ Xe MAX Graphics Products:

• Driver installation may not complete successfully on certain notebook systems with both Intel® Iris™ Xe + Iris™ Xe MAX devices. A system reboot and re-installation of the graphics driver may be required for successful installation.

Intel® Core™ Processor Products:

• Uncharted: Legacy of Thieves Collection* (DX12) may exhibit texture corruption during gameplay.
• Warhammer 40,000: Darktide* (DX12) may exhibit texture corruption during gameplay.
• Dysterra* (DX12) may exhibit texture corruption during gameplay.
• Total War: Warhammer III* (DX11) may experience an application crash when loading battle scenarios.
• Call of Duty Warzone 2.0* (DX12) may exhibit corruptions on certain buildings and floors during gameplay.
• Conqueror's Blade* (DX12) may experience application crash during game launch.
• A Plague Tale: Requiem* (DX12) may experience application freeze and crash during gameplay.

INTEL® ARC™ CONTROL KNOWN ISSUES:

• Windows UAC Admin is required to install and launch Arc Control.
• Some applications may exhibit a transparent or blank window when CMAA is set to “Force ON” globally.
• A 1440p resolution selection in Arc Control Studio Capture may be unavailable when the display native resolution is 4K.
• Arc Control Studio Camera overlay position may not retain desired position and size after a system restart.
• The Arc Control Studio Camera tab may take longer than expected responsiveness upon the first navigation.
• Arc Control may report incorrect memory bandwidth value.

Intel® Arc™ Control Performance Tuning (BETA):

• Intel® Arc™ Control Performance Tuning is currently in Beta. As such, performance and features mmay behave unexpectedly. Intel® will continue to refine the Performance Tuning software in future releases.

You can download the driver by heading over to Intel's official website at this link. The driver is compatible with Intel Arc discrete graphics cards alongside Intel 11th, 12th, and 13th Gen processor graphics.

Intel Graphics v31.0.101.4090 beta driver arrives with support for Forspoken

Windows Terminal Preview 1.17 includes support for dropdown customization to add folders, separators, and profiles by editing the settings.json file. Additionally, another feature some might like is the ability to restart a process by pressing Enter after it has terminated. Moreover, launch position parameters in the Startup section of the Settings UI can be configured too.

On the aesthetics side, there is support for Mica as a background material in Windows 11 by setting the useMica property to "true" in the settings.json file. Similarly, the colour schemes page has been updated again to be more intuitive. You'll even be able to see a preview of a colour scheme before you select it.

Other items from the changelog are quoted below:

• Other colour Scheme Improvements
  • You can now configure a colour scheme (per profile) to apply in System Light theme and System Dark theme
  • You can now configure a colour scheme (per profile) to apply in Application theme
• Virtual Terminal (VT) and Output
  • HUGE shoutout to @j4james for his amazing contributions in the VT space. James worked tirelessly to improve support for VT features, including rewriting how text output is processed in Windows Terminal. Here is a brief summary of the VT contributions that James made for this release:
  • Added support for DEC macro operations
  • Added support for DECARM (Auto Repeat Mode)
  • Added support for IRM (Insert Replace Mode)
  • Added support for private options in DSR queries
  • Added support for selective erase operations (DECSED)
  • Added support for the DECRQM escape sequence
  • Added support for the rectangular area operations (DEC*RA)
  • Merged the legacy and extended attributes
  • Rewrote how we handled text embedded in a stream of VT, which closed 8 bugs!
  • Added support for line rendition attributes (DECDHL) over ConPTY
  • Added support for soft fonts over (DECDLD) ConPTY as well
  • Wide characters will no longer cause weird cursor leavings
  • VT reports once again work when DECARM is disabled
  • Thanks again for all your help, James!
• Usability Updates
  • wt now supports the --pos and --size commandline arguments to control the position and size of the new window (thanks @ianjoneill!)
  • When you duplicate a tab, the new tab will open next to the current tab (thanks @vamsiikrishnaak!)
  • You can now use exe and dll resources for icon paths
• Accessibility Improvements
  • We’ve removed a leading cause of crashes closing panes and tabs while screen reading was active
  • Our internal management window will no longer appear as an empty pane to screen readers
• Miscellaneous Improvements
  • Windows Terminal now supports remaining FinalTerm mark types (command input start, command executed, and command finished)
  • You can now set the scroll bar to be always displayed in $profile.scrollbarState
  • The contents of the Terminal package are now code-signed, so those of you who deploy it unzipped will no longer get in trouble with your IT folks
• Bug Fixes
  • The Export and Find context menu items work on unfocused tabs (thanks @ianjoneill!)
  • We’ve retooled how we launch Terminal elevated when you use an elevate: true profile (or Ctrl+Shift-click a profile in the dropdown menu.) (thanks @jboelter!)
  • The about dialog (and other dialogs) will finally block the entire window even if you resize it
  • We now attempt to account for transparent tab backgrounds when calculating the text foreground colour
  • You can now drag/drop more than 16 items directly out of 7-Zip (and some other applications) (thanks @jiejasonliu!)
  • Malformed settings objects will no longer cause an “Application error 0x%” settings warning
  • “Use Acrylic in Tab Row” no longer requires a relaunch
  • Split pane borders no longer display in the wrong theme colour
  • In separate titlebar mode, Terminal will now default to a dark title bar when you are using a dark theme
  • The “Add Appearance” button will now be read out properly by screen readers

Although what we have above is the changelog for Windows Terminal Preview 1.17, you can also view the changelog for Windows Terminal 1.16 - now generally available - in our previous article here.

You can download Windows Terminal and Terminal Preview from the Microsoft Store here and here, respectively, or through the GitHub repository here.

Windows Terminal Preview 1.17 now out with Mica support and process restart

Downdetector.com quickly detected and tracked outages as users started reporting the issues this morning. Based on the reports, UK Outlook users counted in at just under 5,000. It’s probably more at this time. The reports were mainly from Manchester, Birmingham, London, Norwich, Cardiff, Oxford, Brighton and other areas nearby.

As for Microsoft Teams, it affected users living in India and Japan. For the former, the number of complaints reached 3,900, while Japanese users called in at about 900. From what we can tell, it looks like it also affected the UAE and Australia. If you can still access your Teams servers, that means you’re ok.

The odd thing about these reports is that I’ve been seeing mentions of people returning to meeting in person now that Teams is down. That doesn’t really make sense, as you still have Skype, Google Meets, and other alternative platforms to use. There are also many other messaging apps available, such as WhatsApp and Telegram.

Strange reports aside, Microsoft has indicated that it’s working on resolving the problem. It mentioned it affecting other Microsoft 365 services, too. If you’re on Twitter, you’ll probably find your feed filling up with Tweets with people complaining about this issue, specifically with the #MicrosoftTeams tag.

Have any of you had any issues with Microsoft servers being down? Let us know in the comments.

Source: https://news.sky.com/story/teams-and-outlook-goes-down-for-thousands-of-microsoft-users-12794856

Source

“For the second time, Edge has come back to my desktop,” posted one Reddit user. “When will Microsoft understand that nobody likes Edge?”

“They already understand that nobody likes or wants it,” replied another user. “That’s why they’re doing this.”

Other users shared that the problem occurs every time Edge is updated, causing it to add a new shortcut to the desktop. Additionally, the reports claim that deleting the shortcut just leads to the recreation of a new one, so many instead choose to just hide it. Most affected individuals who voiced their concerns were Windows 10 and Windows 11 users. 

“I keep deleting the shortcut, but it keeps getting reinstalled,” confirmed one Reddit user. “Edge is my default browser but having to delete it from the desktop always is quite annoying.”

Currently, there is no clear explanation for the “issue,” but one Independent Advisor in the Microsoft community forum said it “must be something that was pushed through Edge or Updates.” Greg Carmack, the advisor, also suggested a workaround.

“Most are fixing it by disabling the Edge startup listing in Task Manager > Startup tab, which apparently keeps putting the shortcut back after every restart,” Carmack said. “If not there, check in Task Scheduler if Edge scheduled a task to run at every startup.”

Microsoft said that it is now working on a solution to solve the problem.

Deleted Edge on desktop is persistently coming back; Users believe issue is just a pushy tactic