How to fix Error Code 52

Although it’s easy to set up wired printers in most cases and they have their charm, you don’t have to be around the printer if you are connected to the same network. So in this post, you will be guided on how you can install and set up a wireless printer on your Windows 10 computer. The idea here is to ensure that your Wi-Fi printer and your Windows 10 computer are connected on the same network and to do that, you need to carry out the following steps:

• You have to connect the printer to the Wi-Fi network.
• You have to add the printer or scanner to Windows 10.
• You have to install the printer software.
• You have to change the default printer.
• And troubleshoot the printer.

For more details, follow the instructions below.

Step 1: Connect your printer to the Wi-Fi network. In this step, you need to turn on your printer and look for the option to connect to a Wi-Fi network. Note that the step to connect to the Wi-Fi network depends on what kind of printer you use as well as its OEM since there will be a user interface or a Wi-Fi button that will get the job done for you. Once your printer is connected to the Wi-Fi network, you need to keep it turned on until the setup is completed. Step 2: Next, add a printer or scanner to Windows 10

• Since you’re already connected to the Wi-Fi network, you now have to go to Settings > Devices > Printers & scanners.
• From there, click on the Add a printer or scanner option.
• After that, the scanning process will begin as Windows 10 looks for the printer and once it finds it, it will display the printer in the result.
• Choose the Wi-Fi printer from the results and click on the Add device option. Once you click this option, Windows will install the drivers via Windows 10 update. Note that this process will apply to all the printers – connected, wireless, and so on.

Step 3: You have to install a printer software In this step, you need to use the driver software from the OEM even though the default printer software works since in most cases, the driver software from OEM works better compared to the default ones and offers much better functionality like ink-saving modes, and many more. Step 4: You now have to change the default printer After installing the printer software, you now have to set or change the default printer in your computer. If you have not installed any printer, the default printer in Windows is the one that saves the files. Now since you have already installed your printer, all that’s left for you to do is to change the default printer of Windows 10 to the one you installed earlier. To do that, follow these sub-steps:

• Go to Settings and navigate to Devices > Printers & scanners.
• From there, check the checkbox labeled, “Let Windows manage my default printer” if there are many printers. This will recommend you to use the most used printer. But if you don’t want to switch to the most used printer, then uncheck the checkbox.
• Once done, click on the printer you want to set as the default one and go to Manage, and then click on the Set as default button.

Step 5: If you have any issues with your newly installed printer, then you need to troubleshoot it One of the first basic troubleshooting you can perform to resolve the printer issue is running the Printer Troubleshooter. This built-in troubleshooter can detect and automatically fix the problem for you. To use it, follow these steps:

• Tap the Win + R keys to open the Run dialog box.
• Next, type “exe /id PrinterDiagnostic” in the field and click OK or hit Enter to open the Printer Troubleshooter.
• Then click the Next button and follow the next on-screen instructions to fix the issue with the printer.

A lot of users have experienced various issues either in installing a Feature or a Windows Update. One of these errors is the one with the error code 0x80d02002. If you are one of the users who is facing this problem right now, then the working solutions given in this post will surely help. The Windows Update error code 0x80d02002 indicates that Windows 10 fails to upgrade or install as there is some issue with the files that have been downloaded and Windows encounters an error in installing them. Thus, the best thing you can do in such a case is to start the installation from scratch but before you do that, here are some suggestions that might help.

Option 1 – Try to rename the SoftwareDistribution folder

The Software Distribution folder in the Windows operating system is a folder that can be found in the Windows directory and is used to store files temporarily which might be required to install the Windows Update on your PC. Thus, it is required by the Windows Update and maintained by WUAgent. Aside from that, it also contains all the Windows Update History files and once you delete them, you will most likely lose the Update history. As a result, the next time you run the Windows Update, it may result in a longer detection time.

• Open the WinX Menu.
• From there, open Command Prompt as admin.
• Then type in the following command – don’t forget to hit Enter right after typing each one of them.

net stop wuauserv net stop bits rename c:windowsSoftwareDistribution SoftwareDistribution.bak

• After entering these commands, it will stop the Windows Update Service, the Background Intelligent Transfer Service, and rename the SoftwareDistribution folder.
• Next, got to the C:\Windows\SoftwareDistribution folder and get rid of all the folders and files thereby tapping the Ctrl + A keys to select them all and then click on Delete. Note that if the files are in use, you won’t be able to delete them.
• Once all the contents in the Software Distribution folder are deleted, restart your PC and then go back to Command Prompt and input the following commands again.

net start wuauserv net start bits

Since the folder has already been flushed, it will be populated afresh the instant your restart your computer and open Windows Update.

Option 2 – Try to reset the Catroot2 folder

You can also try resetting the catroort2 folder as it is known to fix tons of Windows Update issues including the Windows Update error code 0x80d02002. Both the Catroot and catroot2 are Windows operating system folders that are required for the Windows update process.  So when you run the Windows Update, the catroort2 folders stores the signatures of the Windows Update package and helps it in the installation. It makes use of the “%windir%System32catroot2edb.log” file in the updating process. Afterward, the updates are stored in the SoftwareDistribution folder which is used then by the Automatic Updates in order to execute the updating process. Keep in mind that you must not rename or delete the Catroot folder. Although the Catroot2 folder is recreated automatically by Windows, the Catroot folder isn’t.

Option 3 – Try running the DISM tool to fix the broken Windows Update client

The Windows update/upgrade error 0x80d02002 might be caused by some issues in the Windows Update client so you need to run the DISM tool to repair it. Note that you have to use another computer or another Windows from a shared network to fix it.

Option 4 – Try to run the Windows Update Troubleshooter

Running the built-in Windows Update troubleshooter could also help you resolve the Windows Update error 0x80d02002. 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.

Option 5 – Try to run Microsoft’s troubleshooter online

You also have the option to run Microsoft’s online troubleshooter which could help you fix Windows Update errors.

If you got an error message saying, The INF file you selected does not support this method of installation while trying to install a driver using the “Install” option in the right-click context menu, read on as this post will guide you in fixing the problem. The INF file mentioned in the error message is a text file that’s divided into different types of formatted sections. Each one of the sections is designed for a particular purpose. For instance, one section is designed to copy files or to add entries to the registry. INF files are used to install drivers. However, if something is wrong, you might encounter this error while installing a driver on your Windows 10 computer. To resolve this problem, you can try to download the driver again from the official manufacturer website or check if the driver is compatible with your computer’s operating system architecture or you can also try installing the driver from the Device Manager. For more details, follow the given options below.

Option 1 – Try downloading the driver again from the official website of the manufacturer

Usually, you shouldn’t encounter this kind of issue no matter what installation method you used on your Windows 10 PC. However, there are times when the driver itself is corrupted for some reason which is why you are unable to complete the installation and receive an error message instead.

Option 2 – Try checking if the driver is compatible with the OS architecture

It is possible that you’re getting this error if you have a driver that is compatible with a 32-bit system and you are trying to install it on a 64-bit system and vice versa. Thus, you need to check if the driver you are trying to install is compatible with your operating system if you haven’t done it when you’ve downloaded the driver from the website of the manufacturer. To check the system architecture, in the Start Search, type “msinfo32” in the field and hit Enter to open the System Information window. From there, you should see all the information about your operating system. In addition, you can also search “system information” in the Cortana search box and look for the System Type entry and open it.

Option 3 – Try installing the driver from the Device Manager

If you have the driver files on your PC and you have to update a driver, refer to the steps given below to be guided on how to install the driver from the Device Manager.

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the driver you want to update, and then right-click on each one of them and select the Update Driver from the menu.
• After that, click on the “Browse my computer for driver software” option.
• Next, select the “Let me pick from a list of available drivers on my computer” option and then click the Next button.
• On the next screen, you should see the “Have Disk” option. Click on this option and then click on the Browse button to go to the location of the file. After that, you shouldn’t have any problem installing the INF file.

Option 4 – Try running the System File Checker Scan

The SFC or System File Checker scan could detect and automatically repair damaged system files that could be causing the “The INF file you selected does not support this method of installation” error. SFC is a built-in command utility that helps in restoring corrupted files as well as missing files. It replaces bad and corrupted system files with good system files. To run the SFC command, follow the steps given below.

• Tap Win + R to launch Run.
• Type in cmd in the field and tap Enter.
• After opening Command Prompt, type in sfc /scannow

The command will start a system scan which will take a few whiles before it finishes. Once it’s done, you could get the following results:

1. Windows Resource Protection did not find any integrity violations.
2. Windows Resource Protection found corrupt files and successfully repaired them.
3. Windows Resource Protection found corrupt files but was unable to fix some of them.

 Now restart your computer.

If you receive an error message saying, “Windows Update cannot currently check for updates because updates on this computer are controlled”, while trying to change the Windows Update preferences or manually update, then read on as this post will guide you in fixing it. You can mostly encounter this error in managed systems where an Administrator controls the permission on the operating system. The reason why you are not able to modify the Windows Update preferences or manually update your system is that a group policy prevents you from doing so and that the only user who can do these things is none other than the administrator of the system. Troubleshooting this kind of problem is the same as when you troubleshoot an error message that says, “Some settings are managed by your organization”. In such cases, you need to check both the Windows Update Group Policy and Registry settings. If you’re just a standard user, you have to contact your system administrator regarding this issue and if you are the administrator, you can make adjustments to the system settings via the Registry Editor and the Group Policy Editor. Refer to the instructions given below for detailed instructions.

Option 1 – via the Registry Editor

If you are using the Home edition of Windows 10 and you want to change the policy for non-admin users on your local computer, then you can use the Registry Editor for that. Here’s how you can do it:

• Tap the Win + R keys to open the Run dialog box.
• Then type “Regedit” in the field and hit Enter to open the Registry Editor.
• After that, navigate to the following registry key:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindows

• From there, look for the key named “WindowsUpdate” in the Windows folder and if it does not exist, you can just right-click on the Windows folder and select New > Key.
• Now name the new key “WindowsUpdate” and create a new sub-key under the newly created key and input “AU” as its name.
• Keep AU selected and then right-click anywhere in the right pane and select New > DWORD (32-bit) Value.
• Then name the Value as “AUOptions” and right-click on AUOptions and select Modify.
• Next, change the value of the Value data to “5” and click OK to save the changes made to the settings. Note that the Value Data of 5 refers to the policy to allow the local admin to choose the setting.
• Now restart your computer once you’re done and check if non-admin users can now modify the Windows Update settings or update Windows.

Option 2 – via Group Policy Editor

• Tap the Win + R keys to open the Run dialog box and then type “gpedit.msc” and hit Enter to open the Group Policy Editor.
• Next, navigate to this folder: Computer Configuration > Administrative Templates > Windows Components > Windows Update.
• Now look for the “Configure Automatic Updates” policy on the right pane and double click on it to open its Properties.
• After that, shift the Radio button to “Enabled” and from the drop-down menu for Configure automatic updating, select option 5: Allow local admin to choose the setting.
• Then click on Apply and OK to save the changes made to the settings.
• Restart your computer and check if the problem’s fixed or not.

Error 1321 - What is it?

Error 1321 is a Windows PC error. This occurs when you try to install a Microsoft Office suite or program on your PC. The set-up program stops responding and the error message is displayed on the computer screen in the following format:

‘Error 1321. Setup cannot modify the file file_name. Verify that the file exists in your system and that you have sufficient permissions to update it.’

When this error occurs you cannot roll back the installation of the Office Suite or use the Add/Remove program option to remove the installed program.

Solution

Error Causes

Common causes of the occurrence of error 1321 are:

• Encrypt contents to secure data settings are enabled on the folder in which you are trying to install the Office suite/ program.
• PC infected by viruses
• Bad Registry Entries

Further Information and Manual Repair

The good news is that this error code is not fatal and besides it is also easy to resolve. Here are some easy do it yourself methods for you to repair this error on your system in a few minutes:

Method 1: Disable Encrypt Contents to Secure Data

To resolve this error code, make sure the encrypted contents to secure data settings are not enabled. To do so, simply right-click the folder in which you want to install the MS Office Suite or program. Now click properties and then the General tab. Now go to the Advanced option. In the Advanced Attributes dialog box, make sure that the Encrypt contents to secure data check box under Compress or Encrypt Attributes is disabled. If it is not then un-check to disable.

Method 2: Remove Viruses

Viral infection can also trigger error 1321. If this is the reason, then simply install and run a powerful antivirus on your system. An antivirus detects all types of malicious viruses such as malware, adware, spyware, and Trojans. Remove them to resolve the issue.

Method 3: Download Restoro.

If the issue is related to bad registry entries, then it is advisable to download Restoro on your PC. This is a user-friendly and powerful PC Fixer deployed with a registry cleaner. The registry cleaner scans your entire PC and wipes away all the bad entries cluttering and damaging the registry in seconds. Click here to download Restoro and resolve error code 1321 today.

KMODE_EXCEPTION_NOT_HANDLED seems to be connected primarily to a third-party driver, e1d65x64.sys associated with the Intel(R) Gigabit adapter, NIC/Wired network NDIS (Network Driver Interface Specification) 6.x driver. Error is known to produce the dreaded blue screen of death or BSOD. Most usually error is connected with gaming on Windows 10 computer and it manifests itself during gaming sessions. If you are unlucky and you are faced with this unfortunate error we will be happy to try to help you and present with tips and tricks in order for you to find a solution for it. Before you proceed with the provided solutions, be sure you have sufficient disk space on the Windows drive, run Disk Cleanup and then run CHKDSK.

1) Run the Blue Screen Online Troubleshooter

Open Control Panel, change the view setting to icons. Click Troubleshooting, and click “View all” in the tasks pane. Click “Blue Screen”. This opens the Blue Screen Troubleshooter.

2) Run Driver Verifier

1. Start a Command Prompt window by selecting Run as an administrator, and type verifier to open Driver Verifier Manager.
2. Select Create standard settings (the default task), and select Next. You can also choose to Create custom settings to select from predefined settings, or to select individual options. For more information, see Driver Verifier options and rule classes and Selecting Driver Verifier Options.
3. Under Select what drivers to verify, choose one of the selection schemes described in the following table.

   Driver verifier table:

   Option	Recommended use
   Automatically select unsigned drivers	Useful for testing on computers that are running versions of Windows that do not require signed drivers.
   Automatically select drivers built for older versions of Windows	Useful for testing driver compatibility with newer versions of Windows.
   Automatically select all drivers installed on this computer	Provides maximum coverage in terms of the number of drivers that are tested on a system. This option is useful for test scenarios where a driver can interact with other devices or drivers on a system. This option can also exhaust the resources available for Special Pool and some resource tracking. Testing all drivers can also adversely affect system performance.
   Select driver names from a list	In most cases, you will want to specify which drivers to test. Selecting all drivers in a device stack allows the Enhanced I/O Verification option to track objects and check compliance because an I/O request packet (IRP) is passed between each of the drivers in the stack, which allows for a greater level of detail to be provided when an error is detected. Select a single driver if you are running a test scenario that measures system or driver performance metrics, or if you want to allocate the greatest number of resources available for detecting memory corruption or resource tracking issues (such as deadlocks or mutexes). The Special Pool and I/O Verification options are more effective when used on one driver at a time.

4. If you chose Select driver names from a list, select Next, and then select one or more specific drivers.
5. Select Finish, and then restart the computer.

3) Update network device drivers

Go to the official Intel website and try to find newer versions of drivers, if there are none perhaps you will need to revert back to the previous version.

4) Scan memory for issues

Run a memory test on your system, sometimes these errors can be traced back to a faulty RAM bank.

5) Stop over-clocking your PC

If you have overclocked your PC please reverse it back to its original state and see if that would solve the issue

6) Perform System Restore to the previous restore point

If none of the previous solutions have bared fruit, roll back to a previous restore point and that should solve the issue.

Logitech announced the Logitech G CLOUD gaming handheld, somewhat of a STEAM Deck competitor. Somewhat, because the reason is that not like Deck this device is not packing huge power in order to run locally PC games, instead it is made with one goal in mind to connect to Cloud gaming and let you play games in that way.

The device is packed with a 7-inch display featuring 1080p resolution in a 16:9 ratio with a refresh rate of 60Hz, an analog thumbstick, a D-pad, 4 action buttons, and triggers. Inside the device beats Snapdragon 720G (CPU used in most Android phones), 4GB of LPDDR4X RAM & 64GB of internal storage. As seen hardware is way less impressive than one that is packed inside the STEAM deck but as stated this handheld is not meant to run natively PC games so this hardware will suffice for its purpose.

Logitech has partnered with both Nvidia and Microsoft to add GeForce now and Xbox Cloud Gaming access to its device. If you have an account on either one of these services you can fully use them on the Logitech G Cloud gaming handheld. You can also play some Android games via the Google play store but the main goal is Cloud gaming.

The price of 350$ USD is not very impressive since STEAM Deck which is a way more capable device is running for 400$ USD, for the difference of only 50$ USD Deck has an advantage, and the price itself is a hard point for selling and if we place into this mix som retro handhelds that go as low as 100$ USD Logitech is in an awkward position. Note that Nintendo Switch is 300$ USD.

We tend to move and copy tons of files on our PCs and mostly, the process of copying or moving files, especially if the file has the size of 1GB or up, tends to take quite long. This may be caused by some issues which is why you face slow copy or move speed. So if you are experiencing this issue on your Windows 10 computer, then read on as this post will give you a couple of solutions you can try to increase the speed in copying or moving files. Follow the given instructions below.

Option 1 – Try to change the USB port

You might want to change the USB port since modern computers have a variety of USB ports. So if your USB drive supports USB 3.0 or 3.1, make sure that you plug it inside a USB 3.0 or 3.1 ports. If you’re not sure which port, just keep in mind that the USB 3 port is usually blue or you can also use your computer’s documentation or manual as a reference to locate it. It may sound nothing but changing the USB port can actually improve the copying or moving speeds drastically so this should be the first thing you can try to speed up the process of copying or moving files.

Option 2 – Update the USB Controller Drivers

• First, click the Start button and type “device manager”.
• Then click on the “Device Manager” from the search results to open it.
• From there, look for the “Universal Serial Bus controllers” option and then right-click on each one of the USB drivers and select the Update Driver from the menu.
• Restart your PC and then click the “Search automatically for updated driver software” option.

You also have the option to update the motherboard and the USB driver from the manufacturer’s official website.

Option 3 – Check for any hard disk errors

• On your desktop, right-click on the “This PC” or computer icon and then select Manage to open the Disk Management. Here you get to check your drive’s health.
• Next, click on Disk Management on the left side panel.
• From there, check the state of your drives. If it shows that all your partitions are healthy then it means all is good and that the problem may have something to do with some physical issues with your hard drive.

You might also want to run the CHKDSK utility to help you fix any issues with your hard disk. If your hard drive has issues with integrity, the update will really fail as the system will think that it’s not healthy and that’s where the CHKDSK utility comes in. The CHKDSK utility repairs hard drive errors that might be causing the problem.

• Open Command Prompt with admin privileges.
• After opening Command Prompt, execute the following command and hit Enter:

chkdsk /f /r

• Wait for the process to be completed and then restart your computer.

Option 4 – Try to disable Windows Auto Tuning

Disabling Windows Auto-Tuning can also help in increasing the copying or moving of files in your computer. It is said that this feature improves the performance of programs that receive TCP data over a network by adjusting the receive buffer size dynamically throughput and latency of the link. Thus, if you are trying to copy some data over the network, then the Auto Tuning feature is playing a role here. And in some cases, disabling this feature completely resulted in a lot faster copy speeds over the network.

Option 5 – Try changing the USB Removal Policy

• First, plug your USB drive or external device into your PC and then open This PC.
• Next, right-click on your device and select Properties.
• After that, go to the hardware tab and select the storage media that you want to enhance and then click on the Properties button.
• From there, you can select the Better performance option if you wish for your device to have a better performance. Once you select this option, it will enable write caching in your Windows 10 computer but you need to use the “Safely Remove Hardware” option from the notification area to safely disconnect the device otherwise it may result in data corruption.

Option 6 – Format your drive

• To get started formatting your drive, tap the Win + E keys and then go to the access page of the drive.
• Next, right-click on the drive and select Format.
• After that, uncheck the “Quick Format” option and then format your drive properly.
• Now once the formatting process is finished, unplug the drive and plug it back in afterward.
• Check if the error is already fixed. If the drive is not initialized, tap the Win + R keys and hit Enter.
• After opening the Run dialog box, type “diskmgmt.msc” and hit Enter to open Disk Management.
• From there, right-click on the drive volume and select initialize disk.
• Next, select the correct partition type and proceed.

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.

Researchers have discovered 16 vulnerabilities in Bluetooth connections that could be exploited and make from minor to some serious damage to your device. The flaw can be used on chips manufactured by Intel, Qualcomm, and Texas Instruments while connecting to external devices like speakers, headphones, keyboards, mice, etc.

Who is affected?

Mentioned chips are used by many in a vast range of devices including big players with their products like Microsoft Surface laptops, Dell desktops, Samsung Phones, Google Pixel, and OnePlus handsets. The Bluetooth bug affects a wide range of devices, including smartphones, laptops as well as smart home gadgets. In total, more than one billion devices that rely on Bluetooth are believed to be impacted.

What is the damage?

The amount of damage possible with this flaw depends on the type of device with the chipset. Some devices can only be crashed after a specially crafted packet is sent to the flawed chip. If that's the case with your gadget, it can be easily resolved with a simple restart. With other devices, hackers can take advantage of the Bluetooth Classic flaw to remotely run malicious code. That could allow malware to be installed remotely. Researchers say vendors were informed about these issues months ago before the findings were published. The good news is this should have given plenty of time for the relevant patches to be pushed out that remedy the flaws. However, you'll need to make sure that you're running the latest version of the operating system to be protected by the patch crafted by the manufacturers.

Android Bluetooth threat

The researchers emphasize the lack of basic tests in Bluetooth certification to validate the security of Bluetooth Low Energy (BLE) devices. The BrakTooth family of vulnerabilities revisits and reasserts this issue in the case of the older, but yet heavily used Bluetooth classic (BR/EDR) protocol implementations. We would also advise users to disable Bluetooth on devices that do not need it. This way you can prevent attackers from sending you malformed LMP packets. Since BrakTooth is based on the Bluetooth Classic protocol, an adversary would have to be in the radio range of the target to execute the attacks. So, in a safe environment Bluetooth can be enabled.