Windows 10 build 22257 was just released, and it’s full of new features. If you decide to upgrade, you’ll be able to set the default browser to the Spartan browser, which promises to be faster than Edge, but slower than Chrome. The new Windows 10 build 22257 also adds support for the Windows Mixed Reality headsets, which will work with the headsets to let you enter Virtual Reality worlds.
Microsoft’s newest Windows 10 upgrade has not been the best received by users. Many have complained that the new OS is highly unstable, causing them to have to reinstall Windows, or that it causes them to lose important files and settings. Many also say that Microsoft’s ‘Get Windows 10’ app is nothing but a scam, attempting to get users to upgrade their OS using false promises and false claims.
He spent much of his time acquiring new talents and learning more about the computer industry, since he was passionate about technology, Windows, and anything that had a power button. Coming from a strong foundation in computer science,… Read more
- Insiders in the Dev channel are beginning to get increasingly unstable preview builds.
- Build 22449 introduces a significant new feature: a modification in SMB compression behavior.
- This is the first time Microsoft has simultaneously issued two major Windows updates.
- Commercial previews of Windows 11 and Windows 10 version 21H2 are now available for corporate customers.
If you’re a Windows Insider who does the majority of your testing in the Dev Channel, you’re going to receive less reliable, more experimental versions of Windows 11, as Microsoft has previously warned.
Because it is the first build from the active development branch (RS PRERELEASE), build 22449, which was just published today, represents a significant jump in version numbers.
If you’re wondering why Microsoft has moved on to more unstable preview releases, it’s because it wants to use the Dev channel to test the first Windows 11 major upgrade, 22H2.
The next OS is set to begin trickling out to eligible devices on October 5th, as you may recall.
This is one of the builds for which Microsoft issued a warning.
So, let’s have a look at what’s new in build 22449, beginning with the most significant change, which is a change in SMB compression behavior.
If you’re not acquainted with the phrase, SMB compression enables a user or program to request that files be compressed while they travel over the network.
If compression is needed, Windows 11 will try to compress the contents starting with this version, resolving an issue where smaller files were previously not compressed.
The following are some of the additional changes and enhancements in this new software version:
- Instead of an animated circle of dots, the boot screen now displays a progressive ring animation for loading the OS. Over time, Microsoft plans to replace this dynamic circle of dots in other parts of the OS.
- Right-clicking on the Bluetooth entry in Quick Settings and selecting Settings will now open the main Bluetooth & Devices page in Settings.
- After an unattended update, the Windows starting sound will no longer play (aka a scheduled Windows update when you are not at your PC).
- Added a link to the touch keyboard personalization settings from Typing > Touch Keyboard to help improve discoverability.
- The backdrop of notifications has been changed to acrylic.
- The animation in the notice that introduces you to Windows Hello if it hasn’t been set up has been updated.
- The dialog that appears when you close Windows Sandbox has been updated to include rounded graphics.
- Notification Center’s appearance has been tweaked to help the app names stand out more from the alerts.
Build 22449 contains a number of fixes.
Let’s have a look at some of the key bug fixes that Microsoft managed to include in this latest patch:[Taskbar]
- Hovering over the Taskbar corner or bottom of secondary displays should now correctly activate the Taskbar if your Taskbar is configured to auto-hide.
- Fixed an issue that caused the calendar flyout to load just the week titles and not the calendar.
- The lunar calendar was out of sync with the actual date in the calendar flyout, which was fixed.
- Additional clocks added to the calendar flyout will now update to match your time format if you’ve changed it.
- When you hover over one of the Desktops in the Task View flyout, your active Desktop should no longer change.
- For screen readers, the Focus Assist button in Notification Center now has an accessible name.
- The typeface in the Taskbar previews was not accurate because of an underlying problem.
- I did some work to improve the reliability of explorer.exe while utilizing the Taskbar on many displays.
- Fixed an issue that caused the Mail app to sometimes fail to accept keyboard input into the address and subject lines of new emails.
- Also addressed an input-related issue that caused some windows, including as Search, Start, and the emoji panel, to stop responding to mouse input.
- When you press Command Prompt to enter text on a tablet or 2-in-1 device in tablet posture, the touch keyboard should now be activated without having to tap the touch keyboard button.
- When the N’Ko keyboard is added to the input list, the name should now appear properly in the input flyout.
- When accessing the emoji panel or voice typing, Microsoft worked to fix an animation problem with the shadow.
- To assist solve a problem where the Pinyin IME might take a long time to start, several performance enhancements were made.
- Fixed an issue where the Pinyin IME would crash and get stuck in a broken state, preventing users from typing anything.
- When UAC was deactivated or Windows Sandbox was used, the Japanese IME didn’t lock Kana input mode and returned it to Romaji input mode after entering a single character.
- When using Japanese IME to enter several prolong noises in a sequence, the first and subsequent ones were added with distinct character codes.
- While attempting to open the input switcher (Win + Space) in certain situations, such as when using Windows Sandbox, you wouldn’t see anything.
- If you searched for “sad” on the emoji panel, you would get an angry looking emoji instead.
- Fixed certain display issues with specific characters when writing vertically, for as when using Meiryo UI to write Japanese vertically.
- I worked on resolving an issue where the left mouse click button on precision touchpads might get stuck and cease functioning.
- When using the Japanese IME, entering ALT key codes on the number pad should now function.
- When a client RDP window was active, Alt-Gr was sometimes ignored, which was fixed.
- A modification was made to help solve an issue that may cause characters to be lost while entering in some win32 text fields using the Korean IME.
- When a File Explorer window was also displayed on the screen, Microsoft worked to solve an underlying problem where moving some program windows was extremely sluggish.
- In Arabic and Hebrew, the command bar should now be correctly mirrored, and the command bar flyouts should now be appropriately positioned in those display languages.
- An problem with the dependability of explorer.exe has been resolved.
- In the Move Folder dialog, a text rendering problem with the apostrophe was fixed.
- Instead of simply navigating to the main page of Network Settings, clicking the “Network discovery is switched off” notice in File Explorer will now take you to a more appropriate place.
- Fixed an underlying problem that was causing explorer.exe to crash for certain users when right-clicking in File Explorer and using the paste button.
- A problem was fixed that caused the battery level shown in Settings for connected Bluetooth devices to get stuck and seem out of date.
- When using the Desert contrast theme, the contrast problems in Sound settings should now be resolved.
- A problem with choosing 5.1 audio type in Sound Settings wasn’t staying was fixed.
- The lengths of the sliders in the Sound Settings volume mixer should no longer be surprising.
- If the indexer is not operating, the Searching Windows link on the Search Permissions page in Settings now works and should no longer crash Settings.
- Improvements were made to assist solve an underlying problem that may cause display positions and settings to be lost unexpectedly.
- Fixed an issue where the profile image in the top corner of Settings might scale incorrectly on occasion.
- The time format in Power & Battery Settings should now follow your preferences.
- Addressed an issue where clicking the high brightness warning in Powery & Battery Settings wouldn’t lower the brightness.
- For devices without batteries, the Video Playback tab in Settings should no longer display battery choices.
- In Language Settings, the typo of Santali has been corrected.
- When utilizing the Tamil display language, the misspelling Malaysia (TA-MY) was fixed under Language Settings.
- I worked to resolve an issue where going to the Lock Screen might sometimes crash Settings.
- Only accounts that support Windows Hello sign-in will see the “only allow Windows Hello sign-in for Microsoft accounts on this device” setting in Sign-in Settings.
- If you want to copy the update names from Windows Update History, you may now choose the text of the update names again.
- Fixed a problem that caused some people’s computers to crash when they clicked on certain of the links on the Advanced Options page of the Windows Update Settings.
- Instead of displaying 0 in Windows Update History, it should now indicate the number of updates in each category.
- If you click the BitLocker link in Settings on a device that doesn’t support it, it won’t crash.
- Fixes to a couple locations in Settings where Narrator wasn’t reading things, as well as an update to make Narrator declare success after connecting a device.
- Personalization Options When a contrast theme is chosen, settings that aren’t supported will be disabled.
- When you open Taskbar Settings in Windows Sandbox, it will no longer crash.
- Quick Settings was hanging and not launching due to a hang related to the input flyout.
- I worked on resolving an issue where the edit button in Quick Settings would sometimes disappear.
- Fixed a deadlock that caused cellular data on/off settings on the Quick Settings and Cellular Settings pages to differ.
- When using Magnifier, Quick Settings should no longer be clipped.
- The Duplicate option under the Project flyout in Quick Settings was not working in certain instances, thus that was fixed.
- On the lock screen, the icons used in Windows Spotlight text should now show correctly and not seem like boxes.
- While updates are being installed, the Windows starting sound should no longer be heard.
- The pushed status of the buttons in the UAC dialog has been tweaked to be more consistent with other buttons.
- When utilizing light mode, the picture in the Windows Hello notification is now visible.
- Following an update, the phrase “getting everything ready for you” should now be written in the proper typeface (Segoe UI Variable).
- After initially setting up a device, I worked on reducing possible banding effects on the “getting everything ready” screen.
- The Number Lock status did not remain after a Fast Start reboot, which was fixed.
- If lock screen slideshow was enabled in combination with “Automatically select accent color from my background” in Personalization options, the Lock screen may look blank with the default lock screen picture.
- After resuming from hibernation or turning off Bluetooth, Insiders with connected Bluetooth LE devices saw an increase in Bluetooth reliability problems and bugchecks.
- Fixed a problem that may prevent you from using Bluetooth with certain connected devices.
- Unexpected beeping, lower-than-expected maximum volume, occasional Windows Audio service hangs, and volume apparently becoming stuck were all fixed for specific connected devices.
- Fixed a problem that caused certain scanners to stop working.
- When adding a monitor, shutting and opening a laptop lid, changing resolution or orientation (including autorotation), or changing a game setting or full-screen mode at a different resolution, an issue that may cause unexpected brightness changes was fixed.
- When a new display driver is installed, disabled devices, such as graphics adapters, should no longer be re-enabled abruptly.
- After turning off a contrast theme, the Min/Max buttons in the title bar of certain applications should no longer appear distorted.
- The explorer.exe crash that may occur while using ALT + Tab has been fixed.
- In ALT + Tab and Task View, the keyboard focus should now be more visible.
In the most recent Store upgrades, the following problems were addressed:
- The problem with the install button not working in certain situations has been resolved.
- Also addressed an issue where certain applications’ ratings and reviews were not accessible.
- Changes to Teams Settings are now possible in Arabic and Hebrew.
- Fixed an issue where there was no ring tone when making an outgoing call although the user interface indicated that the connection was being connected.
- A modification was made to assist improve Task Manager launch speed in situations when it was unusually sluggish.
- In multi-monitor situations, a bug was fixed that caused some programs to use the incorrect color profile.
- The recording and snapshot capabilities in the Xbox Game Bar were abruptly removed as a consequence of an underlying crash.
- Windows Security was not starting on a limited number of devices due to an underlying app deployment problem, which was fixed.
- Windows 11 should now appear in the Windows Boot Loader text.
- In the Store applications troubleshooter, the logo was fixed.
- WSL2 work was done to enhance the performance and reliability of the localhost relay.
After general availability on October 5th, some of the improvements found in Insider Preview versions from the active development branch may find their way into maintenance updates for the published version of Windows 11.
Build 22449 has problems that you should be aware of.
What sort of software release would we be discussing if it didn’t come with its own set of problems?
The Redmond-based tech firm has published a comprehensive list of some of the issues that remain in this latest version, so users will know precisely what to anticipate.
So far, here’s what we know:[General]
- This build will not be sent to Windows Insiders who have Windows Defender Application Guard (WDAG) activated. With WDAG enabled, there is a problem in this version that causes PCs to bugcheck constantly. Microsoft anticipates that this issue will be resolved in the next flight.
- Microsoft is working on a remedy for an issue that is triggering WHEA UNCORRECTABLE ERROR bug checks on certain Surface Pro X devices.
- When using Search from Start or the Taskbar, you may be unable to input text in certain situations. If the problem persists, open the Run dialog box by pressing WIN + R on the keyboard, then shut it.
- When right-clicking on the Start button (WIN + X), System and Windows Terminal are absent.
- When switching input methods, the Taskbar will sometimes flicker.
- The Search panel may not open after clicking the Search button on the Taskbar. Restart the “Windows Explorer” process and reopen the search panel if this happens.
- The search panel may look dark, with no information underneath the search field.
- When you right-click files in OneDrive locations in File Explorer and linger over items that open sub-menus, such as “Open with,” the context menu may abruptly dismiss.
- It’s possible that the widgets board is empty. You can get around the problem by signing out and then back in again.
- External displays may show widgets in the incorrect size. If this happens, open the widgets on your primary monitor first, then on your other displays, using touch or the WIN + W shortcut.
- Microsoft is looking into an issue where certain Insiders may not be able to start Windows Sandbox after upgrading to this version.
- Microsoft is still working on making the Store’s search results more relevant.
- Some Insiders may be missing translations from their user experience for a limited subset of languages using the newest Insider Preview builds due to an issue. To see whether you’ve been affected, go to this Answers forum post and follow the instructions for fixing it.
At the same time, Microsoft publishes two significant Windows updates.
In a commercial preview, Microsoft also launched Windows 11 and Windows 10 version 21H2 to corporate customers.
This is clearly one of the last stages before Microsoft formally finalizes its desktop Windows releases, and it is perhaps the first time it has ever issued two significant Windows updates at the same time.
These builds are available via all normal channels for Windows Insider Program for Business members, including Windows Update, Windows Server Update Services (WSUS), Azure Marketplace, and the Windows Insider Program ISO download website. We are also providing free support for business companies using these builds, in addition to commercial pre-release availability. This means you may test these releases—along with your chosen deployment methods—while still being supported before they go public.
As a result, business PCs registered in the Windows Insider Program Release Preview channel will be given Windows 11, provided they satisfy the release’s stringent new baseline criteria.
Commercial PCs in the Release Preview channel that do not satisfy those criteria, on the other hand, will be given Windows 10 version 21H2.
As previously stated, businesses may opt to stay on Windows 10 and not upgrade to Windows 11.
They may also stay with their existing Windows 10 version since these updates are also optional. If that’s the case, they’ll continue to get quality update preview builds for that version instead.
How can I get build 22449 to work?
Keep in mind that this build is only accessible to Insiders in the Dev channel, so make sure you’re in the correct location before you begin.
After you’ve double-checked this crucial information, go to the procedures below:
- Go to the Windows Update tab in the Settings menu.
- The update should appear as a pending download, so click the Downloadbutton.
- The fix will begin downloading on its own.
- To complete the installation, click “Restart now.”
Have you tried out the latest Windows 11 Insider build yet? In the comments box below, tell us about your experience.
Was this page of assistance to you?
Thank you very much!
There are insufficient details It’s difficult to comprehend Other Speak with a Professional
Start a discussion.
This article broadly covered the following related topics:
- don’t upgrade to windows 11 build 22449 it’s unstable to work
- don’t upgrade to windows 11 build 22449 it’s unstable to stand
- don’t upgrade to windows 11 build 22449 it’s unstable free
- don’t upgrade to windows 11 build 22449 it’s unstable like
- don’t upgrade to windows 11 build 22449 it’s unstable to be