Intel’s GPU ARC coming aimed at AMD & Nvidia

Users are reporting that randomly their screen will just go black for a second and come back. When this happens, it usually distorts any video currently on the screen; sometimes, they can resume working on the PC normally. However, when they view the event logs, they see the error message Display driver nvlddmkm stopped responding and has successfully recovered. In this article, we will address solutions to this issue and how to not have it again.

1. Remove Aura iCUE plugin (applies to only ASUS motherboards)

   Some PC users discovered that iCue adds an Aura plugin for ASUS MOBOs. That, combined with EVGA Precision X1, was causing the error it seems – this was determined when the screen would turn off and on when opening EVGA x1 software. In this case, the issue was resolved by removing the Aura iCUE plugins.

2. Change Power Management mode

   Right-click the battery icon on the notification area on the right of the Taskbar. Select Power Options. In the Power Options window, locate your current Power Plan. Select High performance, if that’s not your current power plan. Now, click on Change plan settings next to it. Now click on Change advanced power settings. Expand PCI Express section. Expand Link State Power Management. Now set power saving to Off for both On battery and Plugged in state. This would fix any issues caused by the low power of the video card. Click Apply > OK to save changes.

3. Update graphics driver

   Go into device manager Expand display adapter section Right-click on adapter Click on update driver Reboot

4. Rollback graphics driver

   Go into device manager Expand display adapter section Right-click on adapter Click on Roll back driver Reboot

5. Uninstall and reinstall graphics card driver

   Go into device manager Expand display adapter section Right-click on adapter Click on Uninstall device Reboot

6. Replace the graphics card

   If everything else failed, replace the graphic card

Blinking or Flashing Desktop After login - What does it mean?

Upon updating to Windows 10, some users might encounter a blinking or flashing desktop after logging in. This will result in a repetitive restarting of explorer or you won’t be able to make the start menu and shortcut keys work. In addition, the network icon might not appear in your taskbar as well. Other Windows 10 error messages include error code 0xc000021a.

Solution

Error Causes

Your blinking or flashing desktop after logging in might be the result of problems with the bushell.dll shell extension, which is a part of the Norton Security Suite. Another possible cause for this annoying problem is an issue with your display driver since not all systems will use the same display driver and will depend on what graphics card you use.

Further Information and Manual Repair

In fixing the bothersome blinking or flashing desktop after logging in problem, you can do a manual repair method to address the root problem. You need to be familiar with the Windows command line to successfully go through the process. However, if you are not knowledgeable or confident enough to do this on your own, it would be best to seek help from a professional. Or, you might want to consider using an automated tool to solve the issue.

You need to identify first what’s causing the blinking or flashing of your desktop after login to properly address the issue. The following methods can be done if your issue is caused by bushell.dll shell extension issue:

Method One: Forcefully Terminate Process

1. Press on Ctrl+Alt+Del then select Task manager
2. Start a Command Prompt as an administrator by choosing the File menu then Run New Task.
3. Type exe. Make sure to tick the checkbox “Create this task with administrative privileges.”

NOTE: Text input is most probably affected by the explorer restarts so you might need to repeatedly type some letters or to carefully input texts.

4. In the Command Prompt, type taskkill /f /im explorer.exe. This will stop the blinking or flashing.
5. Type cd “Program Files” afterward, type dir /s bushell.dll to locate where the dll is. (For example, purposes, use c:\program files\Norton Security Suite\Engine6422.5.2.15 as the location)
6. If the dll file is not found, you can try repeating step 5 but this time, use “Program Files (x86)” However, you can proceed with the next step if you already located where the bushell.dll is.
7. Type cd ”c:\program files\Norton Security Suite\Engine 6422.5.2.15” to change the name of the directory you found the dll in.
8. Type ren bushell.dll bushell-crash.dll
9. Restart now the system by typing shutdown /r /f /t o in the command line.

Method Two: Uninstall Programs

1. Log out then go to the sign in screen
2. Press the Shift key as you simultaneously click on the Power button on the screen.
3. Continue pressing on the Shift key as you click
4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
6. Click on the Startup Settings then select
7. Boot on Safe Mode by pressing 4 on your keyboard.
8. Log in then press Windows key + X.
9. Select the Device Manager then expand Display Adapter.
10. On your Display Adapter, right-click then select
11. Exit Device Manager
12. If in case you also have an older Antivirus utility, you should uninstall it as well.
13. Restart

NOTE: You might need to download the latest Video Driver on a working computer. Save it in a thumb drive then copy and install it on your computer. If in case there is no native Windows 10 driver, you can also download the latest Windows 7 or Windows 8.1 video driver. Afterward, install it in compatibility mode.

Method Three: Use Microsoft System Configuration Utility

1. Log out then go to the sign in screen
2. Press the Shift key as you simultaneously click on the Power button on the screen.
3. Continue pressing on the Shift key as you click
4. Continue pressing on the Shift key as you wait for the Advanced Recovery Options menu to appear.
5. Once the Advance Recovery Options menu appears, click on Troubleshoot then select Advanced options.
6. Click on the Startup Settings then select
7. Boot on Safe Mode but this time, choose 5 to start in Safe Mode with networking.
8. Check if your problem is present or not in Safe Mode. If not, then you are on the right track.
9. Press on the Windows key + R then type msconfig to start up your exe file.
10. Click on the Services tab then choose Disable All. Afterward, click on
11. Once you’re prompted to reboot your computer, go ahead and reboot in Normal Mode. Check if the issue is still present.
12. If the blinking or flashing desktop after login is gone, then you can just do a process of elimination.
13. Start-up on your exe again then begin bringing up services a few at a time.
14. You can turn on all other services except for the following which causes the blinking or flashing desktop after login problem: Problem Reports and Solutions Control Panel Support •Windows Error Reporting Service.

The Windows 10 Telemetry and Data Collection features are auto-enabled and they collect all sorts of user activity and sends it to Microsoft. Microsoft says that the data collected only enhances the overall user experience and Windows functionality better but the number of data breaches happening across the globe has forced users to be extra cautious about their data privacy. So naturally, from stronger passwords and other services management, it is only logical to turn off Windows data gathering. To do so:

• Press ⊞ WINDOWS + R to open the run dialog.
• In the Run dialog type: taskschd.msc
• Press CTRL + SHIFT + ENTER key combo to open Task Scheduler in admin mode.
• On the left pane, navigate to the: Task Scheduler Library > Microsoft > Windows > Customer Experience Improvement Program
• At the location, on the middle pane, right-click on the task named Consolidator and select Disable from the context menu...
• Repeat the process with all other tasks listed in the middle pane.
• Exit Task Scheduler.

You might be familiar with the Encryption File System or EFS algorithm if you rather keep your files and folders encrypted. Encryption File System is a built-in feature in Windows 10 which allows users to secure their important files. Although there is an alternative way for you to secure your data on your Windows 10 computer, you can’t ignore the fact that the main advantage of an Encryption File System over BitLocker is that the former can help you encrypt a particular folder rather than encrypting the whole hard drive partition. If you move a file inside a folder encrypted with the Encrypting File System it will automatically get encrypted. There are some users who like this feature but unsurprisingly, there are some that don’t. So if whether you want your files encrypted when you place them in an encrypted folder or if you want to keep it as it is, read on as to how you can do it either way. You can enable or disable automatic encryption of files moved to encrypted folders in Windows 10 using the Registry Editor or the Group Policy Editor. Before you proceed, make sure to create a System Restore Point first because the modifications you’re about to make in your computer might affect its overall functioning so if anything goes wrong, you can always undo the changes. Once you have that covered, refer to the options given below to enable or disable automatic encryption in Windows 10.

Option 1 – Enable or disable automatic encryption using Registry Editor

• Press the Win key + R key at the same time to open the Run dialog box.
• Then type “Regedit” in the field and press Enter to open the Registry Editor and if a User Account Control or UAC prompt appears, just click Yes to proceed.
• After opening the Registry Editor, navigate to this key location: HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesExplorer
• Next, right-click on Explorer and select New > DWORD (32-bit) Value and then name the newly create DWORD to “NoEncryptOnMove” and press Enter to save it.
• After that, double click on the NoEncryptOnMove DWORD and set its value to the following preferences:
  • 1 – Disable Auto Encryption of files moved to encrypted folders.
  • 0 – Enable Auto Encryption of files moved to encrypted folders.

• Now close the Registry Editor and restart your computer to successfully apply the changes made.

Option 2 – Enable or disable automatic encryption using the Group Policy Editor

• Press the Win + R keys to open the Run box and type “gpedit.msc” in the field and press Enter to open the Group Policy Editor.
• After that, navigate to this path: Computer ConfigurationAdministrative TemplatesSystem
• Next, look for the “Do not automatically encrypt files moved to encrypted folders” option and double click on it to set the policy. From there, you will see the following description:

“This policy setting prevents File Explorer from encrypting files that are moved to an encrypted folder. If you enable this policy setting, File Explorer will not automatically encrypt files that are moved to an encrypted folder. If you disable or do not configure this policy setting, File Explorer automatically encrypts files that are moved to an encrypted folder. This setting applies only to files moved within a volume. When files are moved to other volumes, or if you create a new file in an encrypted folder, File Explorer encrypts those files automatically.”

• Now select one of the radio buttons below depending on your preference:
  • Not Configured or Disabled: Enable Auto Encrypt of files moved to EFS Encrypted folders.
  • Enabled: Disable Auto Encrypt of files moved to EFS Encrypted folders.
• Then click on the Apply and OK buttons to save the changes made.
• Exit the Group Policy Editor and restart your computer.

Windows 11 has brought some new features and changed some of the existing ones. One of these changes includes quick switching of audio devices which will play audio. Audio switching can still be done under the taskbar, it is just a little different and one could say even hidden. Follow this quick guide and you will be switching from your headphones to speakers as an example in a matter of seconds.

1. Click on the speaker icon located in the far-right part of the taskbar.
2. After the quick settings menu appears click on the right arrow located right of the volume slider. If the arrow is not present, instead of click on the pencil icon, then on add, and finally select Volume from the list.
3. After clicking on the arrow icon, a list of all enabled audio devices on the system will replace the volume slider. Click on the desired audio device in order to make it active.
4. Click anywhere outside the quick setting menu to save changes and close it.

Note: in the Quick settings menu if you choose More Volume Settings it will bring you to System > Sound where you can access more sound input and output options.

0x000000A5 - What is this Error Code?

0x000000A5 is a stop error code also referred to as a blue screen of death error code. It is related to Advanced Configuration and Power Interface basic input/output system in Windows. It often leads to a sudden system shut down or your system may restart unexpectedly. Blue error codes like 0x000000A5 are the most severe and dangerous types of errors Windows can encounter. Ignoring 0x000000A5 error pop-ups and not repairing it timely can result in system crashes, valuable data loss and system failure.

Solution

Error Causes

The 0x000000A5 error code occurs particularly because of the ACPI BIOS error. This error message on your computer screen indicates that the Advanced Configuration and Power Interface (ACPI) BIOS of the computer is not compatible with your Windows system and is not fully compliant with the ACPI specifications. BIOS is a set of software. Through this software, the operating system communicates with the computer’s hardware devices. The ACPI is a part of BIOS and the Windows operating system. It is the standard for the way BIOS works. The presence of ACPI in the BIOS on a given Windows system determines whether the system can make full use of features such as Power Management or Plug and Play. Here’s what happens: traditionally, ACPI BIOS implementation tries to manipulate hardware resources directly through BIOS code for hardware functionality nonetheless if the ACPI-based BIOS is not compliant with the ACPI standard on your system, it may not support workable communication between the operating system and the hardware. This results in imbalance as the operations cannot be synchronized which results in system shut down, system instability, and machine failure. As a warning stop error 0x0000000A5 is displayed on the screen.

Further Information and Manual Repair

To fix the error message 0x0000005A on your PC you don’t need any professional assistance. Solving such blue screen errors in just a couple of clicks is not possible with Restoro This is a multi-functional and feature-filled registry cleaner and system optimizer that helps PC users resolve practically every type of system instability issues and registry errors including BSoD errors like 0x000000A5. It offers a comprehensive suite of utilities including registry cleaning, privacy issue detection and repair, system stability error identification, and Active X and Class issues detection. This innovative and advanced PC fixer is designed to ensure and deliver optimum system performance. It scans and detects causes for 0x000000A5 error code and repairs them in seconds. It has a neat and intuitive layout and easy navigation which makes this repair tool extremely user-friendly. Users of all levels are it novice or experienced can use it with ease and fix all types of PC-related errors like 0x000000A5 right away with no hassle. ACPI BIOS Error can be quickly resolved with this tool. This error tool offers outstanding compatibility. It is practically compatible with all Windows versions.

Restoro download

To get started all you have to do is click here to install the Restoro on your computer. Once it is installed, run it to scan for 0x000000A5 error code. After scanning is complete, click the repair button to repair this issue immediately. For user safety and data security, Restoro also creates backup files. This ensures that no valuable data is lost during system repair. So, don’t delay in resolving error 0x000000A5 error code; install Restoro on your system today!

What Is 0x000000D1 Error?

Error code 0x000000D1 is a serious error that is displayed when Windows automatically shuts down to protect the system against further damage.

Usually, when this error occurs, the message displayed to the users states something like STOP 0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL.

Solution

What Causes 0x000000D1 Error?

Usually, the STOP 0x000000D1 error code is caused by issues like incompatibilities, third-party drivers, driver conflicts, outdated drivers, malicious drivers, and other related problems.

Speaking technically, the message displayed to the user actually means that the kernel-mode driver has tried to gain access to memory at an unreasonably high process IRQL.

If left unfixed, STOP 0x000000D1 error can become quite serious. Increased frequency of occurrence may not only lead to data loss but can cause system corruption as well. That’s why it is crucial to fix it and to resolve the underlying issues causing it as soon as possible.

Further Information and Manual Repair

There are different ways of quickly fixing this error, some of which are briefly listed below as follows.

• The solution advised for advanced users is to start the system and log on to it as the administrator. Then do to Start button. Click on All Programs -> Accessories-> System Tools->  System Restore. Here you will find the option, “Restore my computer to an earlier time”. Click on it and select ‘Next’. A list of restore points will appear in front of you. Select the latest restore point and then click on ‘Next’. The confirmation window will appear again. Click on the Next button again. Restart your computer. Congratulations, you have successfully restored your computer.
• Another way that’s more suitable for novice users goes as follows. Download a repair utility tool. Now install the program. You are most likely to come across a Scan button. Once that happens, choose the Fix/Repair button. Your scan will be completed. The error will be removed. You can then restart your computer again to ensure the error is no longer displayed.

Some other suggestions to keep your computer from encountering these problems in the future are outlined below.

• Update all your drivers. Obsolete or old hardware or software drivers may also trigger this STOP 0x000000D1 error.
• If you have recently installed or modified a driver or hardware and the error has occurred afterward, it is highly likely that the installation or modification has caused it. Revert back to the original settings to steer clear of this driver in the future.

In the latest Windows 11 fiasco, it is reported that the operating system is slowing down some SSD drives. Good thing is that it does not affect all of SSD on the market but the ones which it is affecting can see even a 45% of speed drop. Microsoft has not published a solution to this issue, but users point out two potential problems. The first is a security mechanism based on disk virtualization, which is supposed to slow down the performance of SSDs. The second, in turn, is related to the place of installation of Windows 11 – users indicate that if the performance test is performed on a medium with no files associated with the system, its performance results are similar to the parameters given by the manufacturer. Transfer speeds were to be slightly improved with the latest Windows 11 update 22000.348. However, users are still waiting for a solution to the problem that significantly reduces the efficiency of SSD media.

More information

The details described leading to speculation that the problem could be related to drivers that Microsoft is providing. On further tests, all Nvme drives that use the Microsoft driver have this problem, but Intel 905P, which has its own driver provided by Intel, is working at full power,”.

As you know, Microsoft’s Windows Media Creation Tool is a useful tool that helps you download and install the latest version of the Windows 10 operating system. However, there are times when it could encounter some problems during the update process. One of these programs is the following error message:

“0x8007001F-0x20006, The installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation.”

The error pointed out the “Safe OS phase”. It is the phase that’s initiated to install all the required Windows Updates. Thus, the possible cause for this error could have something to do with an interrupted download, internet connection, and many more. Although this error could be caused by a lot of factors, fixing it shouldn’t be that hard. You can try to reset the Windows Update Components or delete the Windows Update cache. You could also disable both the Firewall and your antivirus program temporarily or run the Windows Update in a Clean Boot state, as well as run the Windows Update troubleshooter. To get started troubleshooting the error, follow each one of the suggestions provided below.

Option 1 – Try to reset the Windows Update components

Resetting the Windows Update components could help you resolve the Windows Update error 0x8007001f – 0x20006. How? Refer to the following steps:

• Open Command Prompt with admin privileges.
• After that, type each one of the following commands and hit Enter after you key in one after the other.
  • net stop wuauserv
  • net stop cryptsvc
  • net stop bits
  • net stop msiserver

Note: The commands you entered will stop the Windows Update components such as Windows Update service, Cryptographic services, BITS, and MSI Installer.

• After disabling WU components, you need to rename both the SoftwareDistribution and Catroot2 folders. To do that, type each one of the following commands below, and don’t forget to hit Enter after you type one command after the other.
  • ren C:WindowsSoftwareDistribution SoftwareDistribution.old
  • ren C:WindowsSystem32catroot2 Catroot2.old
• Now, restart the services you’ve stopped by entering another series of commands. Don’t forget to hit Enter after you key in one command after the other.
  • net start wuauserv
  • net start cryptsvc
  • net start bits
  • net start msiserver
• Exit Command Prompt and then restart your computer.

Option 2 – Try to delete the Windows Update Cache

You might also want to delete the Windows Update cache since there are times when existing corrupt or incomplete Windows Update files can cause some problems in downloading and installing Windows Updates. To achieve this, simply delete the “$Windows.~BT” & “$Windows.~WS” folders in your computer. Once you’re done, try to run Windows Update again and see if the error is now fixed.

Option 3 – Try to temporarily disable anti-virus and Windows Defender Firewall

As mentioned, the error could be due to the antivirus program or the Windows Defender Firewall installed on your computer. Thus, disabling them or any security software installed in your computer is always a good idea you can try when you’re not able to access the shared drive on your computer. There are times when you encounter problems like error 0x8007001f – 0x20006 due to interference of antivirus or security programs. Thus, you have to disable both your antivirus program and Windows Defender Firewall for the meantime and check if it fixes the error or not

Option 4 – Run the Windows Update in a Clean Boot State

It is possible that some third-party application is the one that’s causing the problem so it’s best if you put your computer in a Clean Boot state. During this state, you can start the system with a minimum number of drivers and startup programs that will surely help you in isolating the root cause of the issue.

• Log onto your PC as an administrator.
• Type in MSConfig in the Start Search to open the System Configuration utility.
• From there, go to the General tab and click “Selective startup”.
• Clear the “Load Startup items” check box and make sure that the “Load System Services” and “Use Original boot configuration” options are checked.
• Next, click the Services tab and select the “Hide All Microsoft Services” check box.
• Click Disable all.
• Click on Apply/OK and restart your PC. (This will put your PC into a Clean Boot State. And configure Windows to use the usual startup, just simply undo the changes.)
• After that, try to run Windows Update again.

Note: If you are able to install the app without any trouble at all then it means that the error is caused by some third-party application on your computer. You need to look for the culprit and uninstall it once you found it.

Option 5 – Run the Windows Update Troubleshooter

You might also want to run the Windows Update Troubleshooter as it could also help in fixing error 0x8007001f – 0x20006. To run it, go to Settings and then select Troubleshoot from the options. From there, click on Windows Update and then click the “Run the troubleshooter” button. After that, follow the next on-screen instructions and you should be good to go.

Microsoft just released Windows 11 Insider build 22000.71. Let’s dive in and see what it brings with you.

Changes and features

New entertainment widget. The entertainment widget allows you to see new and featured movie titles available in the Microsoft Store. Selecting a movie will direct you to the Microsoft Store to see more information about that title. Just open widgets and click or tap on the “Add widgets” button and choose the entertainment widget. For now, the entertainment widget is available for Insiders in the following countries: US, UK, CA, DE, FR, AU, JP. The new context menus and other right-click menus have been updated to use acrylic material. We are testing the usability of a SplitButton for making new folders and files in the File Explorer command bar. The Taskbar previews (when you mouse-over open apps on the Taskbar) have been updated to reflect the new visual design of Windows 11.

Fixes

Taskbar:

• We fixed an issue where if you drag app icons on the Taskbar to rearrange them, it was making the apps launch or minimize when you released the icon.
• Using a long press with a touch on an app icon in the Taskbar to open the jump list should now work.
• After right-clicking the Start icon in the Taskbar, clicking somewhere else should now dismiss the menu more reliably.
• Shift + Right-click on an app icon in the Taskbar will now bring up the window menu like it used to and not the jump list.
• We’ve addressed an issue that was making your mouse move slowly when hovering over the Taskbar previews.
• We’ve included the fix for an issue when using multiple Desktops where an app icon in the taskbar might give the appearance of multiple windows being open when that wasn’t the case on that Desktop.
• When using the Amharic IME you should no longer see an unexpected X next to the IME icon in the taskbar.
• The issue where if you click on the input indicator on the Taskbar and it would unexpectedly highlight Quick Settings has been fixed.
• When you hover over Task View, the preview flyout for your Desktops will no longer pop back up after using Esc to dismiss them.
• We made a fix to address an issue where explorer.exe might crash after hovering over the Task View icon in the Taskbar.
• We fixed an issue where the selected date in the calendar flyout was out of sync with the date in the Taskbar.
• We made an update to address a scenario resulting in some Insiders not seeing the lunar calendar text in the calendar flyout when enabled in Settings.
• This flight addressed an issue that could unexpectedly make the Taskbar background transparent.
• Right-clicking the focus assist icon in the taskbar should now show a context menu.
• The issue from the previous flight where icons in the taskbar corner were getting crushed against the top of the Taskbar has been addressed.
• The tooltip for the location in use icon in the Taskbar should no longer appear blank sometimes.

Settings:

• We fixed an issue making Settings crash on launch periodically.
• Using the volume mixer sliders in Sound Settings should be more responsive now, as well as the page responsiveness as a whole.
• We fixed an issue resulting in Disk and Volumes Settings’ change size option being clipped.
• There was a non-functional verify link under Backup Settings – this has been fixed.
• The Power and Battery Settings page should no longer be reporting that the battery saver is engaged if it’s not.
• The Power and Battery Settings page should also now not crash when launched from Quick Settings.
• We fixed a grammatical error in the Sign-in Settings text.
• The “I forgot my PIN” link was unexpectedly missing in Sign-in Settings when a PIN was set up and has now been returned.
• The issue where the Move option under Apps & Features in Settings wasn’t working reliably should be addressed in this build.
• We’ve mitigated a problem where some of the colors in Settings weren’t updating after switching between dark and light mode, leaving the unreadable text.
• We’ve done some work to help improve the performance of Settings when switching between light and dark mode.
• We addressed an issue where some of the elements of the Themes page in Settings would end up crowded together when the window size was small.
• We resolved an issue where the Pen menu toggle under Taskbar Settings was not in sync with the actual state of the feature.
• Changes made to “Dismiss notification after this amount of time” in Accessibility Settings should now persist.
• Some of the icons you could enable in Taskbar Settings were erroneously labeled Windows Explorer even though that’s not what they were – this should now be fixed.
• The Connect text in Quick Settings has been updated to say Cast.

File Explorer:

• Clicking the command bar button twice should now close any dropdown that appeared.
• The new command bar should now appear when “Open folders in a separate process” is enabled under File Explorer Options > View.
• This build addresses an issue where right-clicking a file and selecting Open With > Choose another app might launch the file in the default app rather than opening the Open With dialog.
• Fixed an issue the desktop and File Explorer context menu would stop launching.

Search:

• We fixed an issue where the option to verify your account in Search wasn’t working.
• Hovering over the Search icon on a secondary monitor will now show the flyout on the correct monitor.
• Search should now work if you open Start and start typing after having gone to the apps list and back.

Widgets:

• When using the Outlook client with a Microsoft account, Calendar, and To-Do updates should sync faster down to the widgets.
• We addressed an issue where if you added multiple widgets quickly from the widget's settings, it could result in some of the widgets not being visible on the board.
• We fixed a bug where widgets could all become stuck in a loading state (blank squares in the window).
• The traffic widget should now follow the Windows mode (light or dark).
• The title of the sports widget should no longer mismatch with the content of the widget.

Other:

• This build addresses an issue where ALT + Tab was getting stuck open sometimes after you released the keys and had to be manually dismissed.
• We made a fix for an issue where Narrator's focus wasn’t ending up on the emoji panel after using the keyboard shortcut to open it.
• Magnifier’s lens view has been updated so the lens now has rounded corners.
• We found an issue that was noticeably impacting Start launch reliability for some Insiders, and have addressed it with this flight.
• We’ve updated the “Most Used” text in the Start menu’s app list so it should no longer be getting clipped.
• Using the semantic zoom in Start’s app list should no longer result in the list being pushed down and to the right off the edge of the window.
• We fixed an issue where if you pressed ⊞ WIN + Z you would need to press Tab before you could use the arrow key to navigate through the snap layouts.
• We addressed an issue where an acrylic area could get left on the screen after repeatedly snapping and unsnapping a window with touch.
• We’ve done some work to mitigate an unexpected flash when moving a snapped window with touch.
• We made a change to help window borders have a little more contrast when “Show accent color on title bars and windows borders” was turned off.

Known issues in Windows 11 repaired

Start:

• In some cases, you might be unable to enter text when using Search from Start or the Taskbar. If you experience the issue, press ⊞ WIN + R on the keyboard to launch the Run dialog box, then close it.
• Based on feedback, we are working on adding access keys to ⊞ WIN + X so that you can do things like “⊞ WIN + X M” to launch Device Manager. Insiders may see this functionality in this build, however, we are currently investigating an issue in which sometimes the option is unexpectedly unavailable.

Taskbar:

• There is an issue in this build where Explorer.exe will crash when the date and time button on the Taskbar is clicked to access new notifications with Focus Assist turned off. The workaround for this is to enable Focus assist to priority or alarms mode. Note that when focus assist is turned on, notification popups won’t appear, but they will be in the notification center when opened.
• The Taskbar will sometimes flicker when switching input methods.
• Taskbar previews may draw partially offscreen.

Settings:

• When launching the Settings app, a brief green flash may appear.
• When using Quick Settings to modify Accessibility settings, the settings UI may not save the selected state.
• The button to rename your PC doesn’t work in this build. If needed, this can be done using sysdm.cpl.
• Settings will crash when clicking “Facial recognition (Windows Hello)” under Sign-in Settings if Windows Hello is already set up.
• Reset this PC and Go back buttons in Settings > System > Recovery does not function. Reset and rollback can be accessed from the Windows Recovery Environment by selecting System > Recovery > Advanced startup, and pressing Restart now. Once in Windows Recovery, choose Troubleshoot.
• Choose Reset this PC to perform a reset.
• Choose Advanced options > Uninstall Updates > Uninstall latest feature update to perform a rollback.

File Explorer:

• exe crashes in a loop for Insiders using the Turkish display language when the battery charge is at 100%.
• When right-clicking the desktop or File Explorer, the resulting context menu and submenus may appear partially off-screen.
• Clicking a desktop icon or context menu entry may result in the wrong item being selected.

Search:

• After clicking the Search icon on the Taskbar, the Search panel may not open. If this occurs, restart the “Windows Explorer” process, and open the search panel again.
• When you hover your mouse over the Search icon on the Taskbar, recent searches may not be displayed. To work around the issue, restart your PC.
• The search panel might appear black and not display any content below the search box.

Widgets:

• Widgets board may appear empty. To work around the issue, you can sign out and then sign back in again.
• Launching links from the widgets board may not invoke apps to the foreground.
• Widgets may be displayed in the wrong size on external monitors. If you encounter this, you can launch the widgets via touch or WIN + W shortcut on your actual PC display first and then launch on your secondary monitors.

Store:

• The install button might not be functional yet in some limited scenarios.
• Rating and reviews are not available for some apps.

Windows Security:

• Device Security is unexpectedly saying “Standard hardware security not supported” for Insiders with supported hardware.
• “Automatic sample submission” is unexpectedly turned off when you restart your PC.

Localization:

• There is an issue where some Insiders may be missing some translations from their user experience for a small subset of languages running the latest Insider Preview builds. To confirm if you have been impacted, please visit this Answers forum post and follow the steps for remediation.

That's is so far, the latest update information on Windows 11 insider build. Stay tuned for more information when it comes as it comes.